Ugrading a quite old Jenkins server version (1.564) to the latest (1.636)

[jks3]

Hi,

While not a newbie to Jenkins, I am certainly a newbie to Jenkins admin and I've been handed the task of upgrading our Jenkins server from its current version of 1.564 to the latest, which, as of today, is 1.636.

Now, when someone else here attempted this some time ago, they had issues (the details of which I don't currently have) but, suffice it to say that they felt the need to roll back to our current version. I believe they tried to jump to a version multiple versions up (possibly to 1.600) but not the latest at the time. So, I am looking for advise as to the best approach to this.

I don't want to have to upgrade a version at a time (84 upgrades) so, besides perhaps using the 'major enhancement' marker in the Changelog, what would be the recommended intermediate versions to which I should upgrade?

Any other words of advice?

Regards,

JK.

[Victor Martinez]

As you already mentioned the changelog is your key place, probably a LTS version might give you much stability.

Some advice's:

- UI upgrade from 1.574, so you might be affected if you use any custom theme.

- You can backups the JENKINS_HOME and run a docker instance locally and test it before upgrading your production environment. That's how I normally do 'major' uogrades.

- If you use puppet/chef/Ansible you can easily track your jenkins infrastructure, that's how I avoid manual actions and track my set of Jenkins instances, and also I use docker to test it locally as I've already mentioned....

- Although sometimes I'm forced to rollback some plugins (via puppet) rather than the jenkins itself. It is worth if you track your plugins and their versions/dependencies and uninstall those ones you are not using at all.

I hope it helps

Cheers

[Victor Martinez]

I didnt mention that 1.62x onwards require java 7+ in your slaves!!

[James Nord]

1) backup your JENKINS_HOME  (accidents happen)
2) don't go to 1.636 unless you have to - use an LTS if you want stability which it appears you do as you have not upgraded in a long time!
3) make sure any JNLP slaves have their slave.jar updated

[Stephen Connolly]

FYI You are rather probably going to want to upgrade when the security releases come out later this week. (And you have applied the short-term fix to the 0-day already haven't you?)

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/563D27A9.5000502%40teilo.net.
For more options, visit https://groups.google.com/d/optout.

--
Sent from my phone

[Baptiste Mathus]

+ you should test the upgrade on another machine.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw0FYF3nJxdPnZ0raQ2UFr0ELeZVs_-7whV_DruosFScg%40mail.gmail.com.