RELEASED: September 8, 2022
Upgrade notes
| If you use the 2.303.x fixed release after October 5, 2023, the certificate used to sign the offline update center that is included in the release will not be valid. The offline update center allows the installation of the plugins that are packaged with our release. CloudBees strongly recommends that you upgrade to the next fixed release before October 5, 2023. |
- When you upgrade to Java 11, you must update your Java garbage collection arguments (BEE-16018)
-
Garbage collection has been updated in Java 11. Many of the previously recommended arguments are no longer supported. When you upgrade your JDK to Java 11, you must also update your garbage collection configuration. Using unsupported Java arguments will result in startup failure.
For more information, refer to Adding Java arguments to the Jenkins service configuration file.
- End of life announcement (BEE-23004)
-
After assessing the viability of our supported plugins, CloudBees will no longer support the following plugins:
-
CloudBees Docker Build and Publish
-
Jira
-
JIRA Integration For Blue Ocean
-
Mercurial
-
MSBuild
-
Promoted Builds
-
These plugins have been removed from the CloudBees Assurance Program (CAP). This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation, as well as maintaining existing products that are actively used by customers.
If you installed any of these plugins using a Configuration as Code bundle via the plugins.yaml file, you must include them in the plugin catalog to continue using them.
Refer to Installing non-CAP plugins with plugin catalogs.
For more information regarding this end-of-life announcement, please contact your Customer Success Manager.
- Migration to Jakarta Mail (BEE-22565)
-
The CloudBees Nodes Plus plugin and the Operations Center Server plugin were updated to use jakarta.mail instead of javax.mail. This migration may break existing scripts that relied upon javax.mail. You may need to recreate any broken scripts.
- SSH host key verification enabled by default in Git Client Plugin (JENKINS-69149)
-
As a follow up of a security fix from Jenkins Security Advisory 2022-07-27, the Git Client plugin now has SSH host key verification enabled by default using the Known Hosts file strategy. Any
git/checkoutstep that use the SSH protocol now performs strict host key verification based on the~/ssh/known_hostsfile in its environment. Impacted builds fail to check out the code and show the following error:stderr: No <key_format> host key is known for <hostname> and you have requested strict checking.The solution is to specify one of the recommended host key verifiction strategies documented in Git Client Plugin - SSH Host Key verification.
- Jenkins upgrade notes