Security fixes
- Upgrade from gson 2.8.6 to gson 2.8.9 (BEE-22224)
-
Upgraded gson 2.8.6 to gson 2.8.9.
- Upgrade Ivy 2.5.0 to Ivy 2.5.1 (BEE-28081)
-
Upgraded Ivy 2.5.0 to Ivy 2.5.1.
- Security vulnerabilities were fixed and backported from Jenkins (BEE-29043)
-
Refer to CloudBees Security Advisory January 24, 2023 for more information.
Known issues
- Sandboxed Groovy scripts, including Pipelines, that use the
@Field
annotation to declare fields with a type other thanObject
and do not provide an initial value for the field fail to compile. -
The Sandboxed Groovy scripts, including Pipelines, that use the
@Field
annotation to declare fields with a type other thanObject
and do not provide an initial value for the field fail to compile. You should define an initial value for any fields that are declared using the@Field
annotation, or change their declared type toObject
.
For example, the following fields cause the script to fail to compile:
-
@Field String myField1
-
@Field Integer myField2
To resolve this, provide an initial value as in the following examples:
-
@Field String myField1 = null
-
@Field Integer myField2 = 0
You can also declare the fields as type Object
as in the following examples:
-
@Field def myField1
-
@Field Object myField2
This is being tracked as JENKINS-69899.
- Jira Plugin removed from CAP (BEE-22980)
-
The Jira Plugin has been removed from the CloudBees Assurance Program (CAP).
- JIRA Integration For Blue Ocean Plugin removed from CAP (BEE-23090)
-
The JIRA Integration For Blue Ocean Plugin has been removed from the CloudBees Assurance Program (CAP).
- CloudBees Docker Build And Publish Plugin removed from CAP (BEE-22981)
-
The CloudBees Docker Build And Publish Plugin has been removed from the CloudBees Assurance Program (CAP).
- Mecurial Plugin removed from CAP (BEE-22979)
-
The Mecurial Plugin has been removed from the CloudBees Assurance Program (CAP).
- MSBuild Plugin removed from CAP (BEE-22978)
-
The MSBuild Plugin has been removed from the CloudBees Assurance Program (CAP).
- Duplicate Pipeline Template Catalogs in the Configuration as Code
jenkins.yaml
file on each instance restart (BEE-12722) -
If a Pipeline Template Catalog is configured in the CasC
jenkins.yaml
file and theid
property is not defined, the catalog is duplicated on each instance restart and in the exported CasC configuration.
Upgrade notes
- Java 11 is now required
-
Beginning with the September release, Java 11 is now required to run CloudBees CI. It is not possible to run the operations center, the controllers, or agents on Java 8 any longer. Java Web Start is no longer supported for inbound agents.
For more information, refer to Migrate to Java 11.
- 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.
- Plugin Removal from the CloudBees Assurance Program (CAP) (BEE-9215)
-
CloudBees has removed the following plugins from the CloudBees Assurance Program (CAP):
-
Proprietary plugins:
-
CloudBees Amazon Web Services Deploy Engine Plugin
-
CloudBees Even Scheduler Plugin
-
CloudBees Fast Archiving Plugin
-
CloudBees Git Validated Merge Plugin
-
CloudBees Label Throttling Plugin
-
CloudBees WikiText Plugin
-
-
Open source (OSS) plugins:
-
Azure PublisherSettings Credentials Plugin
-
Autofavorite for Blue Ocean
-
Build Timeout
-
CloudBees Docker Build and Publish
-
CloudBees Pull Request Builder for GitHub
-
Conditional BuildStep
-
Jenkins MSTestRunner plugin
-
Jira
-
JIRA Integration For Blue Ocean
-
Mercurial
-
MSBuild
-
MSTestRunner
-
Promoted Builds
-
Parameterized Trigger
-
Pipeline: Deprecated Groovy Libraries plugin
-
Run Condition
-
WMI Windows Agents
-
-
This 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.