Upgrade Jenkins from 1.580 to 2.32.2

83 views
Skip to first unread message

Raj

unread,
Feb 25, 2017, 1:35:25 PM2/25/17
to Jenkins Users
Hello,
We have been stuck to a very old version of Jenkins for a while now. 1.580. we are on Centos 6.

I am wondering if any one has upgraded from 1.580 to 2.32.2 via yum and including all plugins ? 

If someone could share their experience it will be really appreciated. 

apart from need for jdk 1.8, is there any other hard dependency for the upgrade?
Regards,
Raj

Michael Pailloncy

unread,
Feb 26, 2017, 6:24:07 AM2/26/17
to jenkins...@googlegroups.com
Few months ago, I've successfully upgraded from 1.6x to 2.x without any issue. But it depends on your configuration and installed plugins. 
Have a look at https://jenkins.io/doc/upgrade-guide/ and https://jenkins.io/changelog/ to get changelog details and upgrade specific instructions.

But since 1.580 is pretty old, I would recommend to upgrade to the latest 1.xx first, and then upgrade to 2.32.2 to avoid too many changes at the same time. And of course, a backup is always recommended before any upgrade :-)

--
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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4b262872-a494-4d29-9e3d-f390b5f14218%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Baptiste Mathus

unread,
Feb 26, 2017, 8:13:39 AM2/26/17
to jenkins...@googlegroups.com
+1 with Michaël. Upgrade should be possible without any hard issue, but indeed dependent on how many plugins you installed, and possibly custom ones.

Strongly recommended to test that upgrade in your staging env (i.e. duplicate your set up, and try to upgrade). Also, we've written quite a few time about that: I would recommend to not upgrade in place for simplicity, roughly:

1. Get a new machine (assuming you're using a common virtualized/cloud one)
2. duplicate existing env (rsync or so is your friend)
3. test upgrade
4. if break, fix it, wipe everything and go back to 2
5. if nothing breaks, celebrate. Then plan for the upgrade: go back to 2, but in the end, simply switch your DNS/reverse proxy or whatever to point to your new server.
6. Celebrate

HTH

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

Raj

unread,
Feb 27, 2017, 12:59:18 PM2/27/17
to Jenkins Users
Thank you for the feedback. 

Sure. we can do that and more simply with a vm snapshot for rollback. 

but in case of staging upgrade how do you propose \ suggest to manage the slave \ agents ? i ask since if i bring up the staging with a rsynced config then the agents will try to connect too and might cause a issue. or should we just make all slaves offline when i take a snaphot so when they do comeback they will be not connected to the master and that way we can test just the master and once it is fine then just connect all agents to the new server ?

Peter McNab

unread,
Feb 27, 2017, 1:29:59 PM2/27/17
to jenkins...@googlegroups.com

I don't remember exactly when the change was made, but keep in mind that Java7 is required for slave nodes with recent versions of Jenkins.  If you have slave nodes without that available they will be dead in the water.

Pete

--
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/3f246128-6cea-4013-a175-c27bcce0e588%40googlegroups.com.

Baptiste Mathus

unread,
Feb 27, 2017, 2:17:32 PM2/27/17
to jenkins...@googlegroups.com
Well, no. The Java 8 change hasn't been made yet, though it is coming according to the announced plan (first weekly should be on April, and first LTS requiring it should be around early June). And Java 7 has been around for a long time.

And we already discussed the fact that though some platforms may not have a JDK packaged with std distro, it's dead simple to download it directly from , uncompress and be done with it on the big majority of platforms (Centos 6 is not an issue at all for instance, I can relate).

2017-02-27 19:29 GMT+01:00 Peter McNab <pmc...@perforce.com>:

I don't remember exactly when the change was made, but keep in mind that Java7 is required for slave nodes with recent versions of Jenkins.  If you have slave nodes without that available they will be dead in the water.

Pete


On 2/27/2017 9:59 AM, Raj wrote:
Thank you for the feedback. 

Sure. we can do that and more simply with a vm snapshot for rollback. 

but in case of staging upgrade how do you propose \ suggest to manage the slave \ agents ? i ask since if i bring up the staging with a rsynced config then the agents will try to connect too and might cause a issue. or should we just make all slaves offline when i take a snaphot so when they do comeback they will be not connected to the master and that way we can test just the master and once it is fine then just connect all agents to the new server ?



On Saturday, February 25, 2017 at 1:35:25 PM UTC-5, Raj wrote:
Hello,
We have been stuck to a very old version of Jenkins for a while now. 1.580. we are on Centos 6.

I am wondering if any one has upgraded from 1.580 to 2.32.2 via yum and including all plugins ? 

If someone could share their experience it will be really appreciated. 

apart from need for jdk 1.8, is there any other hard dependency for the upgrade?
Regards,
Raj

--
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-users+unsubscribe@googlegroups.com.

--
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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0b283e4a-7b5f-a981-3dac-212d45358eec%40perforce.com.

Peter McNab

unread,
Feb 27, 2017, 2:32:20 PM2/27/17
to jenkins...@googlegroups.com

No to what?

Jenkins 1.608 made slaves require Java7, so it might impact Raj's upgrade attempts.

I know the Java8 change hasn't been made, but it's coming soon as well.

Java7 has been around a long time, but so have the platforms I support, and we we moved up to a version that supported pipelines a number of the older platform slaves stopped working and some users had to scramble to adjust their jobs.

Pete

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/CANWgJS5UFiUi-WGM7SkLx%3D1R49YadXmKUgV9g%3De7-UH8rognrQ%40mail.gmail.com.

Baptiste Mathus

unread,
Mar 1, 2017, 4:01:04 AM3/1/17
to jenkins...@googlegroups.com
Right, sorry, I misunderstood, I assumed Raj was using Java 7 VM for running Jenkins already, but he didn't tell this part.

@Raj: if you're still using a JDK6, then yes, you better indeed upgrade everything to JDK8 while in the go. If already using JDK7, then you should be fine, but you want to plan to upgrade to JDK8 everywhere probably also while at it to avoid headaches with the upcoming baseline upgrade (next month for first weekly, early June for first LTS requiring Java 8).

--
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-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9258cc89-19ee-0393-d4d3-366f433fbcac%40perforce.com.

Raj

unread,
Apr 11, 2017, 10:35:30 AM4/11/17
to Jenkins Users, m...@batmat.net
Thank you very much for all the help and pointers (yes some slave issues did surface needing latest Java quickly resolved the issues.)
Here is the report of my upgrade:
1: it was seamless no issues faced. 
2: Upgraded all the plugins. 
3: Minor issues faced related to Jococo plugin and some lost credentials which had to be reselected from drop down for Jenkins build success or failure notification to Stash\ Bitbucket 
4: some slack api access keys configuration were lost. 
5: had to change this for  /etc/sysconfig/jenkins 
JENKINS_AJP_PORT="-1"

But over all nothing that could be called a show stopper. 

I am \ will be for ever indebted to authors \ maintainers \ supporters of this software. Without you guys i am not sure where we would have been. 

regards,
Raj
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
--
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.
--
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.

--
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.
Reply all
Reply to author
Forward
0 new messages