Hi Michael, Yes, please share if you could. We have quite a different setup from you (as upgrade are done by deploying new docker images rather than updating the instances with jenkins builtin feature and modifying $JENKINS_HOME from within the instance), but we could still learn some tricks to make the process smoother.
Thanks. Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > Le 9 mai 2020 à 16:12, Michael Keppler <michael.kepp...@gmx.de> a écrit : > > On 06.05.2020 18:53, Frederic Gurr wrote: >> To >> spread the load and wait for running builds to finish, we distribute the >> upgrade over several days. > > At work I have created a pipeline which automatically restarts Jenkins > whenever it is necessary and no jobs are running _without_ using the > "cannot take any further jobs" mode. I upgrade Jenkins plugins every > other day, but _never_ restart manually, since that pipeline takes care > of everything. > > Would you be interested in that, and if so, is there any bugzilla to > continue such discussion? > > > Ciao, Michael > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
