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 c
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 pl
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 pipel
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
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.
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
+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
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.
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 jd
