Hi list My group run a large Jenkins instance that many other teams in our organisation depend on. We want to automate the Jenkins upgrade process which will include a measure of verification that the upgrade hasn’t broken anything.
I’m thinking of only using LTS releases, backing up the main config.xml and the configs for each job, and running test jobs that use the plugins we’re supporting. My question is, what else are you doing to verify a Jenkins upgrade has been successful? What checks do you perform before letting an upgrade go into production? Thanks Rob Johnston ________________________________ This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp". Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au. The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
