Hi, Once again we will need to do a long overdue Jenkins upgrade.
During CW 33 (August 17-20) we will gradually upgrade all of our CI instances to the latest Jenkins LTS version to provide new features and important security updates. * Why do you spread the upgrade over a week? We have more than 250 active CI instances that need to be upgraded. To spread the load and wait for running builds to finish, we distribute the upgrade over several days. We are planning to improve this and cut down the required time in the future. * How long will my project's CI instance be unavailable? In most cases, this will require only a restart of each CI instance and should not take more than an hour (this is a *very* conservative estimate to be on the safe side). If no builds are running, we simply run the upgrade. If builds are running, we either wait for them to complete or contact the projects directly to find a suitable time for a restart. See also: https://wiki.eclipse.org/IT_SLA#Jenkins.2FJIPP_upgrades NOTE: If you have any important releases planned for this week (CW 33), please contact us, so we can figure out an alternative time frame. Please let us know, if you have any other questions or concerns. Regards, Fred -- Frederic Gurr Release Engineer | Eclipse Foundation Europe GmbH Berliner Allee 47, D-64295 Darmstadt Handelsregister: Darmstadt HRB 92821 Managing Directors: Gaël Blondelle, Mike Milinkovich _______________________________________________ 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
