Hot answers tagged

17

Yes, it is possible. In Windows, this is what I see when there is a new version available: When you click the Upgrade Automatically button, Jenkins downloads and install the new war file itself. Please, check Jenkins wiki for further details. There are some problems if you installed Jenkins from a Debian package. If you run Jenkins with java -jar ...


5

I found out via this StackOverflow question which pointed me to JENKINS-27624 which indicates that Java 8 is now required. Update: I upgraded Java on all my nodes this morning and they are up and working.


3

For tools which don't offer access to a source code management repository that you can automatically query for updates you could start with a manual trigger, then take a closer look for how is that trigger activated by humans and maybe automate the task: there could be upgrade email notifications sent to a subscriber list. An automatic email processing ...


3

From your list of tools: Jenkins and Github have apt/yum repositories you can use to install and upgrade. For Atlassian products, best up to date information about repositories I can found is This ShipIt experiment and it seems unlikely to change from this forum post The workaround may be parsing the mailing list to update the deploy. Now if you really ...


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

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 ...


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 ${HELM_HOST} -...


1

I recommend Chocolatey. There are more and more companies that are adopting this. For example, if one would like to install Gradle and navigates to the installation page: Chocolatey is “the package manager for Windows”. $ choco install gradle


1

You can overwrite the existing jenkins.war file with the new one and then restart Jenkins. This file is usually located in /usr/share/jenkins. If this is not the case for your system, in Manage Jenkins -> System Information, it will display the path to the .war file under executable-war.


Only top voted, non community-wiki answers of a minimum length are eligible