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 help from : http://stackoverflow.com/questions/38157686/migrating-to-jenkins-2-1-ajp-support-is-removed-in-winstone-3-0-due-to-jetty-9 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 On Wednesday, March 1, 2017 at 4:01:04 AM UTC-5, Baptiste Mathus wrote: > > 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). > > 2017-02-27 20:32 GMT+01:00 Peter McNab <[email protected] <javascript:>> > : > >> 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 >> >> On 2/27/2017 11:16 AM, Baptiste Mathus wrote: >> >> 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 <[email protected] <javascript:> >> >: >> >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/3f246128-6cea-4013-a175-c27bcce0e588%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/3f246128-6cea-4013-a175-c27bcce0e588%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/0b283e4a-7b5f-a981-3dac-212d45358eec%40perforce.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/0b283e4a-7b5f-a981-3dac-212d45358eec%40perforce.com?utm_medium=email&utm_source=footer>. >>> >>> >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5UFiUi-WGM7SkLx%3D1R49YadXmKUgV9g%3De7-UH8rognrQ%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5UFiUi-WGM7SkLx%3D1R49YadXmKUgV9g%3De7-UH8rognrQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/9258cc89-19ee-0393-d4d3-366f433fbcac%40perforce.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/9258cc89-19ee-0393-d4d3-366f433fbcac%40perforce.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/21fd910b-38ee-49e1-96d8-703ec90f4f2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
