Thank you this has been most helpful and I will be sure to come back with any questions if I encounter any issues!
Sent from my iPhone > On Jan 23, 2016, at 8:35 AM, Baptiste Mathus <[email protected]> wrote: > > Hi, > > Basically, yes, there are obviously many risks doing a fast-forward of almost > 5 years, maybe even more with a project as active as Jenkins :). > > BUT, depending on your environment (how many jobs, nodes, exotic configs, > unmaintained/custom plugins...), this may not be a so big issue in the end. > The upgrade should still be pretty automatic if you're a bit lucky. > No specific patch or something should be required off the top of my head. > > What you want to do is to replicate your whole current install the new target > server, and just try upgrading. You'll see how it goes. Crawl the archive > here about how to move a server onto another machine about that (basically, > rsync should almost always be sufficient from my experience). > > When you have done that, and have found specific issues, don't hesitate to > come back here to ask for help/advice. > > HTH > > -- Cheers > > 2016-01-21 17:40 GMT+01:00 Nia Hunter <[email protected]>: >> Good morning, I have two basic questions. I am not sure if this is the >> correct group for these questions, if not please let me know where to pose >> these questions. >> >> We are using Jenkins as a stand-alone application on our UNIX server. >> >> 1. Other than Java 7 and above, are there any System Requirements or >> Environmental constraints associated with upgrading from a much older >> version of Jenkins to the latest? For example, we are using Version 1.423 >> and would like to go to at least Version 1.638, but preferably the latest. >> Is there a patch required when doing an upgrade from such an old version? >> >> 2. Are there any general risks associated with upgrading from an older >> version to a newer version? >> >> Thanks! >> -- >> 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/8afcd1af-840f-4d05-b72e-afcc8a57600f%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/55-9UlaD44A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6_D7COajvP0XadaY7dn71_nTLyExuFkS72aRxL%2B%3DqY8Q%40mail.gmail.com. > 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/E2DE1AE0-27CF-4288-A86F-9A31B4935CD3%40gmail.com. For more options, visit https://groups.google.com/d/optout.
