CloudBees maintenance lifecycle


CloudBees maintenance lifecycle policies

This page provides the maintenance lifecycle and End of Life policies for CloudBees products.

Related pages:

CloudBees releases product updates in two different ways:

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.

Currently supported rolling releases

Product

Release and release notes

Release date

Download

CloudBees Core for Traditional Platforms - Client Master

2.164.2.1, rev 2

2019-04-10

Download

CloudBees Core for Traditional Platforms - Operations Center

2.164.2.1, rev 2

2019-04-10

Download

CloudBees Core for Cloud Platforms

2.164.2.1

2019-04-10

Download

CloudBees Jenkins Distribution

2.164.2.1, rev 2

2019-04-10

Download

CloudBees Jenkins Enterprise

1.11.17

2019-03-29

Download

CloudBees Jenkins Platform

2.164.2.1, rev 2

2019-04-10

Download

CloudBees Jenkins Platform Operations Center

2.164.2.1, rev 2

2019-04-10

Download

Fixed releases

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.

Currently supported fixed releases

Release Release Date Maintenance End Support End Products

2.107

July 18, 2018

April 18, 2019

July 18, 2019

  • CloudBees Jenkins Platform

  • CloudBees Jenkins Platform Operations Center

2.138

February 19, 2019

November 19, 2019

February 19, 2020

  • CloudBees Jenkins Platform

  • CloudBees Jenkins Operations Center

DEV@cloud End Of Life (EOL)

CloudBees shut down the DEV@cloud service at 12:30AM UTC on December 15, 2018.

However, some customers may have negotiated an extended shutdown schedule. For former DEV@cloud customers on an extended shutdown schedule, there are two modern CloudBees solutions available for consideration:

  • CloudBees CodeShip is a hosted, automated CI/CD for your webapps is focused on flexibility, speed, and low overhead. It runs entirely in the cloud and is a great fit for all Linux-based applications you may need to build but don’t have extra time to manage.

  • CloudBees Core provides extensive governance, compliance, team management and flexible customization. CloudBees Core can run in your own cloud, or on-premise, and is backed by Jenkins and the robust plugin ecosystem to support any of your DevOps needs.

Customers who need to migrate their data to a new solution should consult the DEV@cloud Migration Guide.