HI All, Jenkins was today upgraded from 2.32.2 LTS to 2.46.2 LTS.
We were not planning on this upgrade just yet , but a blog post [1] detailing security vulnerabilities, some major, one critical , sort of made it obvious we needed to bump our schedule forward to immediately upgrade. In addition, the upgrade was not announced ahead of time due to the security issues. We did notify by twitter 2 hours before and 1 hour before and then again once the upgrade was complete. The upgrade itself went fine. We started off by doing some pre-upgrade plugin updates. Then the upgrade. The post upgrade plugin updates. So, everything is now bang up to date. Projects should make themselves aware of some major changes that have happened since 2.32.2 LTS :up to the current 2.46.2 LTS release. If any project is affected by any of these changes, they should seek out the documentation which details the specific changes made, and what the alternate configurations might be. See the Jenkins Upgrade Guide at [2] for details. Also note that in the last month or two, we have added in probably a dozen new plugins that have been requested, including Blue Ocean, so feel free to have look around. As always, any issues, please do create an INFRA Jira ticket and/or email the builds@apache.org <mailto:builds@apache.org> mailing list. I encourage all projects to use the builds list as a self service list for sharing in configurations,hints and tips, etc. Thanks Gav… (ASF Infra) [1] - https://jenkins.io/blog/2017/04/26/security-advisory/ <https://jenkins.io/blog/2017/04/26/security-advisory/> [2] - https://jenkins.io/doc/upgrade-guide/2.46/ <https://jenkins.io/doc/upgrade-guide/2.46/>
