We’re rewarding the question askers & reputations are being recalculated! Read more.

New answers tagged

1

Not to take away from @vaporwave_sailor or @Alex, answers, but to add to.. The basic answer is you MUST upgrade the war first, then the plugins. All plugins depend on a minimum Jenkins version and the Update Centre will give you different information back. If you don't upgrade often, use the LTS version. READ the Upgrade Guide. READ the Changelog. Re-READ ...


1

I've gained some experience from f-n up Jenkins a lot of times, here is order I kept sticking to and it saved me a lot of time: Upgrade Jenkins itself (if needed) Upgrade Auth plugins (i.e. Github org auth) Upgrade plugins related to most important pipelines/projects (ssh-agents, ansible, k8s, docker, whatever you guys are using) Upgrade currently used but ...


2

I can only speak from personal experience rather than best practices, but in our company we'll make a duplicate jenkins instance, then upgrade that. We do main upgrade first, then plugins second, then run testing to make sure our core jobs still work. If all is good, we'll then upgrade the real jenkins during off-hours. We have 90+ jobs so testing them all ...


1

See my answer here: Ran into this today when trying to use Garden.io for a cluster running in Jelastic. Found the solution in this Github comment: First acquire a local binary for Tiller (server-version of Helm), either by compiling or by downloading it from the release page. Then run: $ export HELM_HOST=":44134" $ tiller -listen ${...


0

What you suggest might be the simplest way to collect the data, but you will have to do quite a bit of work to extract the availability over certain periods. I think it's fair to say that if you want availability, you need a monitoring system. This means having an extra service in your catalogue to continuously probe the availability of your microservices ...


Top 50 recent answers are included