CloudBees CI release highlights
What’s new in CloudBees CI 2.361.2.1
- Initial Release of CloudBees Inactive Items Plugin (BEE-23073)
A new preview feature, the CloudBees Inactive Items Plugin, has been introduced for licensed CloudBees CI users. The CloudBees Inactive Items plugin analyzes the jobs, folders, multibranch pipelines, and organization folders within your controller and produces a report that lists the inactive items.
The CloudBees Inactive Items Plugin is a Preview feature. Refer to the CloudBees Inactive Items Plugin documentation for more information.
- Managed controllers do not start as the operations center is not available to serve the CasC bundle through HTTP (BEE-16819)
When a managed controller starts from the HTTP bundle file or the bundle link file now, it restarts until the operations center is available for the HTTP download.
- Controller provisioning with CasC is not using the Jenkins shared thread pool (BEE-20192)
Instead of a specific thread pool, controller provisioning with CasC now uses the Jenkins shared thread pool.
- CasC bundle files did not support YAML anchors (BEE-15845)
The anchors are now supported at any location in a YAML file. The anchor description element name must be prefixed by
x-colors-declaration: &colors - red - green - blue ... items: - kind: "freeStyle" name: "project-alpha-freestyle" ... parameters: - choice: name: foreground-color choices: *colors - choice: name: background-color choices: *colors
Refer to Using YAML anchors and Using YAML anchors
- New CLI and HTTP endpoints to get the effective bundle of a new bundle (BEE-23033)
You can now validate the new version of a bundle before you upload it to the operations center through the Controller Bundle Location Service.
A new CLI downloads the effective bundle applying the inheritance so it can be validated on the controller using the
casc-bundle-validatecommand. The expected input is a zip file that contains all of the bundles (including parent bundles) that have changes. The output is the effective bundle in text format.
java -jar jenkins-cli.jar -s JENKINS_URL -webSocket -auth user:token casc-get-effective-bundle -b bundle-id < /path/to/zip/file
A new HTTP endpoint downloads the effective bundle applying the inheritance so it can be validated on the controller using the
casc-bundle-mgnt/casc-bundle-validateendpoint. The expected input is a zip file that contains all of the bundles (including parent bundles) that have changes. The output is the effective bundle in zip format.
- Auto-triggered build after a draft PR is moved to ready-for-review (BEE-23832)
Previously, use of the
avoid pull requests marked as draftsfeature to trigger a build of a multibranch job did not auto-trigger builds while the PR was in draft mode. However, when the
avoid pull requests marked as draftsfeature was used, webhooks cannot trigger the build automatically after the PR is moved from
Now, the PRs in draft mode do not trigger builds, but when the PR is moved from
ready-for-review, the webhooks trigger the build automatically. The
converted-to-draftevents are now managed by github-branch-source-plugin.
- CloudBees SSH build agents disconnect on rekey events (BEE-18090)
CloudBees SSH build agents disconnected with a host key verification error due to a known issue in SSHD 2.8.0, tracked by SSHD-1264.
The SSHD dependency has been upgraded to a version with the fix, which solves the problem.
- Improved robustness of self-signed certificate provider (BEE-23076)
In some edge cases, the self-signed certificate could not be loaded.
This issue has been resolved.
- Managed controller configuration warning shows broken icons (BEE-23294)
Warnings in the managed controller configuration screen show broken icons.
The issue has been resolved. Warnings are now displayed properly.
- The CyberArk credentials were not working with CasC from folders (BEE-22331)
The CyberArk credentials configured at the folder level could not be imported or exported.
This issue is now fixed.
- Hot reload of CasC bundles takes too long (BEE-22912)
Hot reload (both forced and normal) of CasC bundles can now be launched asynchronously, avoiding timeouts. The UI launches hot reload asynchronously, by default. The REST and CLI interfaces launch hot reload synchronously, by default, to maintain backwards compatibility. You can change the behavior by using a parameter in the requests.
This issue is now fixed.
- JCasC export of CyberArk credentials returns an exception if global credentials are not enabled (BEE-23220)
If the CyberArk Credential Provider Plugin is configured, but the global credentials are not enabled, a configuration export shows an error in the YAML file. This error is displayed using either the Jenkins Configuration as Code or the CloudBees CasC Client plugins.
This issue is now fixed.
- The CloudBees product description is missing in the Support Bundle (BEE-22518)
The product description in a support bundle’s
about.mdfile was not properly filled in anymore.
This issue has been resolved.
- 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).
- The offline Update Center signature expires potentially and old versions of the product do not start up (BEE-10093)
The offline Update Center can only be updated by upgrading the WAR file and the WAR file is trusted, giving no added security by signing the file that is inside the WAR file. The product might not start up when the certificate that is used to sign the JSON is no longer valid (occurs if the product had not been upgraded in a long time). The JSON embedded inside the WAR file is no longer signed.
- Duplicate Pipeline Template Catalogs in the Configuration as Code (CasC) for Controllers
jenkins.yamlfile on each instance restart (BEE-12722)
If a Pipeline Template Catalog is configured in the CasC
jenkins.yamlfile and the
idproperty is not defined, the catalog is duplicated on each instance restart and in the exported CasC configuration.
- 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 Migrating 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.
- 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 Integration For Blue Ocean
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 (CasC) for Controllers 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.
- Jenkins upgrade notes