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.

Older release notes