Hey Ketan, Thank you for taking time and answering my question. Following your answer , I would 2 more questions to ask.
1- About the java requirement, does goCD 15.8 support the java8 sdk so I could update every agent machien to use java 8 instead thus when uprading goCD, everything will work as intended and I won't have to update it during the upgrade reducing my maintenance window ? 2- You said the best way to prevent any execution, is to disable all agents. If I want to test an upgrade , I'll use our current server backup and as I restore that backup on a test machine to perform a test upgrade , how do I prevent that server when starting from starting any pipeline and not affecting the current one running ? Thank you very much again for taking time in answering those questions. a+ Fred Le vendredi 16 février 2018 13:44:57 UTC-5, Fred a écrit : > > Hi guys ! > > Recently I was mandated to plan a version update of GoCD from 1.5.2 to > latest and because of political reason, this upgrade can't afford to fail. > I started digging into the documentation and wrote an upgrade and rollback > plan which ended with a couple of questions and I'm wondering if you guys > could help me on this. > > Here is the questions I come up : > > 1) Documentation says that goCD will always updates his agent to its > corresponding version , could there be a problem in case of a rollback to > an older version (17.+ to 1.5.2) ? > 2) Do disabled agents finish their current executing task properly ? > 3) Is there a maintenance mode in GoCD that prevents anything to start > automatically. A one Pause button to rule them all ? Can we pause all > pipeline prior to starting a goCD server ? > 4) Following a goCD server upgrade , when are agents upgraded ? Does goCD > upgrades disabled agents? > 5) Does the server stop command wait for jobs to be finished (graceful > stop) or I need to make sure nothing runs before stopping the server ? > 6) What is the impact of doing the backup procedure whille there is job > executing on the goCD server ? > > Here is the upgrade plan : > > 1) Pause all pipelines and wait until all active jobs on the agent grid > has completed (all agents are in the state "idle"). *Question (3)* > > 2) Backup the GoCD server. *Question (6)* > > https://docs.gocd.org/current/advanced_usage/one_click_backup.html > > 3) Stop GoCD Server. *Question (3,5)* > > 4) Backup all agents of the GoCD server. *Question (1)* > > 5) Upgrade the GoCD server. > > 6) Start GoCD server. > > 7) Test most representative pipeline to see if the upgrade works. > > 8) Enable all pipelines. *Question (3)* > > 9) If there is any problem do a *rollback*. (See *rollback* section) > > 10) Write a report , things that need to be fixed , etc etc anything > relevant. > > > Here is teh rollback plan : > > 1) Stop GoCD Server. *Question (5)* > > 2) Restore backup on GoCD server. > > https://docs.gocd.org/current/advanced_usage/one_click_backup.html > > 3) Restore backup on all agents of the GoCD server. *Question (1)* > > 4) Start GoCD server. *Question (3)* > > 5) Test most representative pipelines to see if the upgrade works. > > 6) Enable all pipelines. *Question (3)* > > 7) If there is any problem we are doom. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
