+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 2017-02-26 12:23 GMT+01:00 Michael Pailloncy <michael.paillo...@gmail.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 > :-) > > 2017-02-25 19:35 GMT+01:00 Raj <rp0...@gmail.com>: > >> 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+unsubscr...@googlegroups.com. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/jenkinsci-users/4b262872-a494-4d29-9e3d-f390b5f14218% >> 40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/4b262872-a494-4d29-9e3d-f390b5f14218%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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/CAPO77c0rVpj8Grtc9rcDxXy_korLoiBXBMbEwtJCdf8hgX6Tnw% > 40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c0rVpj8Grtc9rcDxXy_korLoiBXBMbEwtJCdf8hgX6Tnw%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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6wC_Q4hOHdFeGDaLyRCJhL%2BMDO8SNWGFp3SdyrhQ1hoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
