CloudBees CI release notes

CloudBees CI is a fully-featured, cloud native flexible, scalable CI/CD solution that can be hosted on-premise or in the public cloud. It provides a shared, centrally managed, self-service experience for all your development teams.

Please refer to maintenance lifecycle policy to learn which versions of CloudBees CI are currently supported as well as the supported platforms page for the product to learn which platforms are supported.

If you skip versions when you upgrade, refer to previous versions of the release notes for any relevant known issues or upgrade notes. The CloudBees supported platforms and CloudBees maintenance lifecycle policies pages contain additional information about what is supported in this release.

2.332.1.4

Released: March 9, 2022

Guava library upgrade (BEE-8569)

The Guava library has been upgraded from 11.0.1 to 31.0.1.

This upgrade removes the usage of deprecated methods for all plugins in the CloudBees Assurance Program (CAP). Please ensure that all other plugins (those not in the CloudBees Assurance Program and any custom developed plugins) are updated to a recent version that is compatible. If you have questions about this upgrade, contact CloudBees Support for assistance.

2.319.2.7

Released: January 18, 2022

Apache Subversion is not available as part of the UBI Docker images

The CloudBees CI on traditional platforms Docker images were recently migrated from Debian to Universal Base Images (UBI). Please note that Apache Subversion is not available as part of the UBI Docker images.

2.319.2.5 Security release

Released: January 12, 2022

CloudBees CI on traditional platforms Docker image migration

The CloudBees CI on traditional platforms Docker images were migrated from Debian to Universal Base Images (UBI) in this release. UBI provides a more secure and stable model for building Docker images.

Please note that, as part of the migration from Debian to UBI, various system packages were not included in the CloudBees CI on traditional platforms Docker images, causing issues in some specific use cases. This issue has been resolved in release 2.319.2.7. CloudBees recommends that you install the latest version to avoid potential issues.

2.319.1.5 Security release

Released: December 1, 2021

Critical upgrade issues for customers using CloudBees Configuration as Code (CasC)
  • If using CasC for controllers to create Pipeline jobs, Multibranch Pipeline jobs, GitHub Organizations, or BitBucket Teams/Projects, you must add the cloudbees-casc-items-controller plugin to the controller’s plugins.yaml file during the upgrade process, before the first restart of the controller. Otherwise, the controller instance fails to restart after the upgrade and an Invalid kind error is returned.

    For more information, refer to Creating a CasC bundle for controllers

  • If configuring a managed controller to be automatically provisioned with CasC, you must add the cloudbees-casc-items-server plugin to the operations center’s plugins.yaml file during the upgrade process, before the first restart of the operations center. Otherwise, the operations center instance fails to restart after the upgrade and an Invalid configuration elements error is returned.

    For more information, refer to Creating a CasC bundle for the operations center.

  • If using CasC for the operations center to create Cluster Operations or controllers, you must add the cloudbees-casc-items-server plugin to the operations center’s plugins.yaml file during the upgrade process, before the first restart of the operations center. Otherwise, the operations center instance fails to restart after the upgrade and an Invalid kind error is returned.

    For more information, refer to Creating a CasC bundle for the operations center.

The cloudbees-casc-api plugin can also be removed from the controller and operations center plugins.yaml file.

2.303.2.3 Security release

Released: October 6, 2021

Do not upgrade to this version if either of the following conditions apply to your CloudBees CI or CloudBees Jenkins Platform installation:
  • You use RPM to upgrade your installation, or

  • You use the the trusted folder feature of the CloudBees Folders Plus plugin

CloudBees CI and CloudBees Jenkins Platform version 2.303.2.3 have been released with CloudBees Folders Plus plugin version 3.18, which has an issue that could prevent the instances from starting. Additionally, the RPM install package was not correctly configured. If you used it to upgrade, it could cause the operations center and client controllers to start as a new instance.

Please use version 2.303.2.5 instead of 2.303.2.3.

2.289.3.2 Security release 1 revision

Released: July 28, 2021

Removal of Apache Commons Digester from Jenkins Core

CloudBees recommends that you start to prepare for the August release of Jenkins LTS as soon as possible. The August release will include a change that removes the Apache Commons Digester from Jenkins Core. If you use Jenkins LTS plugins that are not in the CloudBees Assurance Program (CAP), you should update them before upgrading your CloudBees products to ensure compatibility with the August release. If your company uses its own proprietary (non-CloudBees) plugins, CloudBees recommends that you test them against Jenkins version 2.302+ prior to the August release. As always, backing up your data before upgrading is strongly encouraged. For details about this change and a list of impacted plugins, please see our knowledge base article Commons Digester Library Removal.

2.289.2.2 Security release

Issues with RPM installation for CloudBees CI on traditional platforms customers with custom users - Latest update: 2021-07-09

The RPM-based installation for version 2.289.2.2 is failing for some CloudBees CI on traditional platforms customers with custom users. You may receive the following error:

main process exited, code=exited, status=6/NOTCONFIGURED

This issue has been resolved in version 2.289.2.3. CloudBees recommends that you install version 2.289.2.3 instead of version 2.289.2.2 to avoid potential issues.

If you attempted to upgrade to version 2.289.2.2 and encountered issues, refer to this knowledge base article or contact CloudBees Support.

Remove the jquery and jquery-detached plugins from your CloudBees CI instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees CI instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees CI instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: June 30, 2021

v2.289.1.2 Security release

Exception occurs in Jetty client on CloudBees CI on traditional platforms when long files are read using SSL

When large HTTP requests are submitted while the built-in Winstone/Jetty container is configured to use SSL/TLS connections, the following exception can occur:

Encrypted buffer max length exceeded

This exception could prevent you from configuring controllers.

This issue is resolved in versions 2.277.4.4 and 2.289.2.2. If you encounter this error, you should upgrade to one of those versions as soon as possible.

Remove the jquery and jquery-detached plugins from your CloudBees CI instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees CI instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees CI instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: June 2, 2021

v2.277.4.4

Remove the jquery and jquery-detached plugins from your CloudBees CI instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees CI instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees CI instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: July 2, 2021

v2.277.4.3 Security release

Exception occurs in Jetty client on CloudBees CI on traditional platforms when long files are read using SSL

When large HTTP requests are submitted while the built-in Winstone/Jetty container is configured to use SSL/TLS connections, the following exception can occur:

Encrypted buffer max length exceeded

This exception could prevent you from configuring controllers.

This issue is resolved in versions 2.277.4.4 and 2.289.2.2. If you encounter this error, you should upgrade to one of those versions as soon as possible.

Remove the jquery and jquery-detached plugins from your CloudBees CI instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees CI instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees CI instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: May 11, 2021

v2.277.4.2 Security release

Remove the jquery and jquery-detached plugins from your CloudBees CI instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees CI instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees CI instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: May 5, 2021

v2.277.3.1

Released: April 20, 2021 Security release 2 revisions

Remove the jquery and jquery-detached plugins from your CloudBees Jenkins Platform instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees Jenkins Platform instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees Jenkins Platform instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

v2.277.2.3

Upgrading the CloudBees CasC API plugin

Issue

The CloudBees CasC API plugin has been promoted to the CloudBees Assurance Program (CAP). If you have previously modified the plugin-catalog.yaml file to include the CasC API plugin, when you upgrade, your controller(s) will not start properly and you may receive exceptions.

Workaround

You must edit the plugin-catalog.yaml file to remove the CasC plugin and version string: cloudbees-casc-api: {version: X.X}, where X.X represents the version of the CasC plugin. For more information, see Updating a plugin catalog on operations center.

Remove the jquery and jquery-detached plugins from your CloudBees Jenkins Platform instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees Jenkins Platform instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees Jenkins Platform instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: April 7, 2021 Security release 1 revision

v2.277.1.2

The setup wizard shows after updating an instance to 2.777.1.x

Issue

After updating an instance, the setup wizard is displayed.

Jenkins 2.277.1 removes the Upgrade Wizard that was no longer operational after Jenkins 2.0. This caused a regression for instances created before 2.4/2.7.1 LTS.

At the time of this writing, no fix is available for this issue.

Workaround

See the Jenkins upgrade guide for a workaround for this issue. On subsequent restarts, the setup wizard will no longer appear.

Important updates in the March release

The March release includes important updates. If you use Jenkins LTS plugins that are not in the CloudBees Assurance Program (CAP), you should update them before upgrading your CloudBees products to ensure compatibility with the March release. If your company uses its own proprietary (non-CloudBees) plugins, CloudBees recommends that you test them against Jenkins version 2.277.1 prior to updating your CloudBees products. And, as always, backing up your data before upgrading is strongly encouraged.

For details about changes in the March Jenkins LTS release, see:

Remove the jquery and jquery-detached plugins from your CloudBees Jenkins Platform instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees Jenkins Platform instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees Jenkins Platform instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

Released: March 11, 2021 Security release 2 revisions

v2.263.4.1

Released: February 11, 2021 Security release 1 revision

v2.263.2.3

User-created content regressions

Version 2.263.2.3 fixes some critical regressions found in version 2.263.2.2 of the following products:

  • CloudBees CI

  • CloudBees Jenkins Distribution

  • CloudBees Jenkins Platform

  • CloudBees Jenkins Enterprise

Potential issues include:

  • If you use external artifact storage, it is not possible to download entire directories of archived artifacts as Zip files.

  • Zip files containing directories of workspaces, archived artifacts, and similar user-created content are missing top-level directories.

  • File handles are not closed directly whenever individual files are downloaded from workspaces, archived artifacts, and other user-created content. This could result in Jenkins running out of file handles.

CloudBees recommends that you upgrade to version 2.263.2.3 to prevent potential issues with user-created content.

Released: January 21, 2021 Security release