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.387.2.3 Security release

Released: April 5, 2023

Promoted Builds integration removed from the Operations Center Context plugin (BEE-31064)::

The Promoted Builds plugin was removed from the CloudBees Assurance Program (CAP). It was previously integrated with the Operations Center Context plugin.

2.375.3.3

Released: February 8, 2023

Kubernetes-client upgrade to 6.x (BEE-28247)::

The Java library used to access Kubernetes, fabric8 Kubernetes-client, has been upgraded from 5.x to 6.x.

This new Java library version enables customers to provide CustomResourceDefinitions (CRDs) to the provisioning lifecycle, even if they are not part of the client Java model.

This update has no impact for customers who do not use the YAML field under Advanced configuration on the controller configuration screen in the Operations center. For customers using the YAML field under Advanced configuration, this update has the following impact:

  • apiVersion on a resource being deserialized is now required. This prevents the unintentional parsing of custom types without a registered class as a built-in type of the same name. Refer to kubernetes-client/MIGRATION-v6.md at master · fabric8io/kubernetes-client for more technical details about this breaking change.

  • If apiVersion is missing, the controller reprovisioning will fail once the operations center is upgraded until the issue is fixed.

For more information about this upgrade, refer to this knowledge base article, The apiVersion on a resource being deserialized is required after upgrading Kubernetes-client 6.x. The article also contains a script that you can run to check for invalid configurations. The configurations listed in the output of this script should be fixed by providing a valid apiVersion.

If you have questions about this upgrade, contact CloudBees Support for assistance.

Older release notes