[moving to users list, please use that list non Jenkins dev related questions]
Definitely do what Daniel advises (back up), plus set up a pre-production server, with the same current config, and try upgrading that one first to know where you're going. 2016-09-28 16:38 GMT+02:00 Daniel Beck <m...@beckweb.net>: > https://jenkins.io/2.0/#compat > > It's not a semver major version increase. > > That said, it is always advisable to have good backups when upgrading in > case something does unexpectedly go wrong. > > > On 28.09.2016, at 16:08, RAMMY237 <rammy...@gmail.com> wrote: > > > > Hey guys, > > > > While distracted by build procedure script enhancements and side > projects I got kinda out of date. > > I'm currently running Jenkins v 1.653 > > > > Soon Jenkins suddenly jumped to v 2.x and past 6 months there are 24 > versions already. > > > > To be plain, how can I make sure I am safe to upgrade, for example, to > v2.7 ? > > > > Also, if I want, for example, to upgrade to latest v2.23, may I always > be sure I am OK to do such upgrade (v1.653 -> v2.23) without some interim > upgrades? > > (e.g. somewhere mentioned that must go through v2.13 before upgrading to > v2.20 or higher for data compatibility or whatever reason) > > > > p.s. I'm also running about 15 plugins which are not out-of-the box, how > can I also make sure they are compatible with any 2.x Jenkins version? > > (plugins' pages usually say Jenkins v1.xxx or higher in requirements, > but I'm sure most of those requirements were placed before 2.x existence) > > approx. list of my plugins is: Build Failure Analyzer, > build-name-setter, description setter plugin, Email Extension Plugin, > Extra Columns Plugin, Green Balls, Locale plugin, Multijob plugin, P4 > Plugin, Role-based Authorization Strategy, Validating String Parameter > Plugin > > > > Thanks! > > Pavel > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to jenkinsci-dev+unsubscr...@googlegroups.com. > > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/be8e18bb-efd7-4986-bc6a-a1e26d83150c% > 40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/3EB3C0C9-062C-4EA3-8C38-16E946AAFA72%40beckweb.net. > 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/CANWgJS4BXcduFj1c%2B_nx%2B47eyJrjCRc2OLi_EJgWjfUGHMuhpA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
