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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f246128-6cea-4013-a175-c27bcce0e588%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
