This page provides the maintenance lifecycle and end-of-life policies for CloudBees products.
CloudBees Build Acceleration
The following table shows the anticipated End of Life dates for active versions of CloudBees Build Acceleration (CloudBees Accelerator):
| Version | Release date | End of Life target date |
|---|---|---|
12.4.x |
June 30, 2023 |
December 31, 2024 |
12.3.x |
November 18, 2022 |
May 31, 2024 |
12.2.x |
May 31, 2022 |
November 30, 2023 |
12.1.x |
November 8, 2021 |
May 31, 2023 |
12.0.x |
December 21, 2020 |
June 30, 2022 |
11.3.x |
July 30, 2020 |
January 31, 2022 |
11.2.x |
Jan 29, 2020 |
July 31, 2021 |
11.1.x |
July 2, 2019 |
January 31, 2021 |
11.0.x |
January 7, 2019 |
July 31, 2020 |
Use these dates to plan for any CloudBees Build Acceleration upgrades. The End of Life dates are estimates that are based on plans for future versions and the SLA requirement that at least two active CloudBees Build Acceleration versions must be available at a time.
CloudBees CD/RO
CloudBees releases product updates for CloudBees CD/RO with rolling releases.
Rolling releases
Rolling releases are published approximately once per month. Each new rolling release includes important fixes and new features for the product.
Maintenance updates and support for rolling releases
CloudBees provides maintenance updates for only the latest rolling release.
CloudBees provides diagnostic support of issues reported in rolling releases that are up to a year old. If a customer is running a rolling release more than one year old, CloudBees may require the customer to upgrade to a supported rolling release before diagnosing the issue.
Calendar versioning
CloudBees CD/RO uses a calendar versioning convention. The version number consists of the following fields:
Major: four digit year.
Minor: two digit month.
Micro: This is a patch version number starting with zero.
Modifier: An optional text tag, such as "dev", "alpha", "beta", "rc1", and so on.
Examples
The release version 2023.02.0 would be the first release in February 2023. The release version 2023.03.2 would be the second patch release in March 2023.
The following table shows the anticipated end-of-life dates for versions of CloudBees CD/RO (CloudBees CD):
| Version | Release date | End-of-life target date |
|---|---|---|
2023.08.0 |
August 15,2023 |
August 14,2024 |
2023.06.0 |
June 20, 2023 |
June 19, 2024 |
2023.04.0 |
April 10, 2023 |
April 9, 2024 |
2023.03.0 |
March 9, 2023 |
March 8, 2024 |
2023.02.0 |
February 3, 2023 |
February 2, 2024 |
10.11.x |
December 13, 2022 |
December 12, 2023 |
10.10.x |
November 10, 2022 |
November 9, 2023 |
10.9.x |
October 7, 2022 |
October 6, 2023 |
10.8.x |
September 2, 2022 |
September 1, 2023 |
10.7.x |
August 5, 2022 |
August 4, 2023 |
10.6.x |
June 30, 2022 |
June 29, 2023 |
10.5.x |
April 28, 2022 |
April 27, 2023 |
10.4.x |
January 31, 2022 |
January 30, 2023 |
10.3.x |
September 20, 2021 |
September 19, 2022 |
10.2.x |
June 3, 2021 |
June 2, 2022 |
10.1.x |
February 26, 2021 |
February 28, 2022 |
10.0.x |
June 30, 2020 |
Dec 31st, 2021 |
9.0.x |
February 4, 2019 |
July 31, 2021 |
8.0.x |
August 1, 2017 |
December 31, 2019 |
7.0.x |
October 3, 2016 |
January 31, 2019 |
6.0.x |
June 20, 2015 |
December 31, 2017 |
5.0.x |
May 12, 2014 |
March 31, 2017 |
4.2.x |
December 21, 2012 |
December 31, 2015 |
Use these dates to plan for any CloudBees CD/RO upgrades. The end-of-life dates are estimates that are based on plans for future versions and the SLA requirement that at least two active CloudBees CD/RO versions must be available at a time.
CloudBees CI and CloudBees Jenkins Platform
CloudBees releases product updates for CloudBees CI and CloudBees Jenkins Platform through a set of rolling releases. CloudBees Jenkins Platform also has a fixed release.
Rolling releases
Rolling releases are published approximately once per month. Each new rolling release includes important fixes and new features for the platform.
Maintenance updates and support for rolling releases
CloudBees provides maintenance updates for only the latest rolling release.
CloudBees provides diagnostic support of issues reported in rolling releases that are up to a year old. If a customer is running a rolling release more than one year old, CloudBees may require the customer to upgrade to a supported rolling release before diagnosing the issue.
| If upgrading from a rolling release older than 2.361.1.2, customers may experience technical difficulties. CloudBees ensures compatibility only between supported versions of the product and recommends upgrading early and often to avoid these difficulties. If you are having difficulties upgrading, contact CloudBees Support for assistance. |
Currently supported rolling releases
Product |
Latest rolling release |
Latest rolling release date |
Oldest rolling release with diagnostic support |
Oldest rolling release with diagnostic support release date |
Download |
CloudBees CI on traditional platforms |
September 20, 2023 |
September 9, 2022 |
|||
CloudBees CI on modern cloud platforms |
September 20, 2023 |
September 9, 2022 |
|||
CloudBees Jenkins Platform |
August 23, 2022 |
September 9, 2022 |
Fixed releases for CloudBees Jenkins Platform
Fixed releases are a more conservative release model, suitable for organizations that prefer a conservative approach to upgrades over new features and feature enhancements. Fixed release lines deliver a release only when security fixes for the distribution are released, and consist solely of incremental security and high-severity bug patches.
Maintenance updates and support for fixed releases
CloudBees provides maintenance updates to a fixed release for 9 months following its availability date and support for 12 months following its release.
For example, if a high-severity issue is resolved within 9 months of the release being made available, that fix will be backported to any fixed releases that fall within the 9-month maintenance window. If a customer encounters a problem that is resolved in the next release, and the currently installed version is out of the maintenance period, CloudBees support will recommend that the customer move to the current fixed release.