Jenkins Long Term Support Terms


With the release of Jenkins Enterprise from CloudBees 11.11 (November release, 2011), CloudBees has aligned itself with the Jenkins Long Term Support (LTS) Release.  This document outlines the CloudBees support model due to the LTS move.

1.0 Background

With the introduction of Jenkins Long Term Support (LTS) release, the community has committed itself to providing a stable Jenkins release roughly every 3 months. The community moves to a new branch after 3 months. The community model is described here

However, quite a number of organizations stay on a stable release for more than 3 months and desire that they are not blocked waiting for community resources to address the issues that impact them.

Organizations can address both issues by moving Jenkins Enterprise from CloudBees: CloudBees provides support for issues for 9 additional months on a LTS release and customers get access to resources that can fix issues for them.

1.1 About CloudBees

CloudBees employs a number of elite experts on Jenkins, including the founder (Kohsuke Kawaguchi) of Jenkins/Hudson. In addition, CloudBees offers the only production Jenkins in the cloud product (DEV@cloud) in the market. CloudBees runs the biggest installation of Jenkins in the world through its cloud offering). At last count, there were more than 5000 customers running their Jenkins masters in the cloud. Finally, CloudBees offers a training course on Jenkins.

CloudBees is also a key player in the community and its team has submitted scores of patches to various parts of Jenkins. Due to this unique position, it also has considerable influence with various plugin committers.

Thus, CloudBees is the premier expert on Jenkins (both on-premise and in the cloud).

2.0 Support Terms

  1. Community Rules: CloudBees provides support on the Jenkins Long Term Support  (LTS) release. The LTS release is supported for 3 months by the Jenkins community and fixes on the releases are subject to governance rules ("rules") from the Jenkins community (defined under "Model" sub-heading in the LTS document).
  2. Issue Fix Model for current LTS release: For issues on a current LTS release branch ("current-LTS"), CloudBees is subject to the aforementioned community "rules" to deliver fixes into the release. CloudBees will contribute fixes to the current Jenkins release ("Jenkins-tip") and follow due-process to  petition the community for accepting CloudBees changes into the LTS branch.
    1. Although, CloudBees cannot guarantee the acceptance of the fixes into "current-LTS" branch if the fix does not meet the community acceptance criteria for LTS patches, customer can avail of fixes through "Jenkins-tip". In a case that moving to "Jenkins-tip" is not feasible and issue is extremely critical for customers operation, CloudBees (at its discretion) can work with customers to provide one-off custom patches
    2. CloudBees will offer patches on as needed basis
  3. Issue Fix Model for past LTS release: For issues on previous LTS release ("superseded") branch, CloudBees will follow the community rules to push fixes to the superseded branch. If fixes continue to meet the community criteria, CloudBees will provide fixes by custom patches to multiple customers. As in [2], customers can move to "Jenkins-tip" to avail of fixes that do not meet the community acceptance criteria. As in [2], CloudBees will offer fixes to critical to operation issues in custom one-off patches at CloudBees' discretion
  4. Support Period: CloudBees will provide fixes for a period of 9 months from the time the community discontinues support (3 months) on the "current-LTS" release. Thus, customers can use an LTS branch for a period of 1 year since the time the branch becomes current.
  5. Support on Jenkins tip: CloudBees will provide fixes on "Jenkins-tip" and current Jenkins LTS release. Fixes for Jenkins-tip can be availed on the next weekly release. (subject to rules mentioned in bullets 1-4).
  6. Number of active Jenkins support branches: Given that CloudBees supports current-LTS branch for 9 months in addition to the 3 by the community, at a particular time there are 4 active branches. These branches are current-LTS, current-LTS-1, current-LTS-2, current-LTS-3 (where -1, -2, -3 should be read as current minus 1, 2 and 3).
  7. Run CloudBees proprietary plugins on Jenkins: With the release of Jenkins Enterprise from CloudBees 11.11 (November release, 2011), CloudBees allows customers to run plugins from Jenkins Enterprise on the current community release of Jenkins ("Jenkins-tip") (provided customer installs the CloudBees license). For a customer choosing to run these plugins on Jenkins (and not Jenkins LTS release):
    1.  If an issue requires a fix to Jenkins underlying core
      1. CloudBees will provide fixes on Jenkins-tip and not on a specific previous release of Jenkins
      2.  CloudBees will provide fixes on current-LTS release (if required) as outlined in this document
    2. If there are issues that require fixes to the plugins, CloudBees will provide fixes as part of custom patches.


Supported Jenkins Versions

CloudBees supports Jenkins versions which fall into the following categories:

  1. Jenkins Enterprise by CloudBees (up to 1 year old) - The latest Jenkins LTS is bundled into the Jenkins Enterprise by CloudBees release twice a year. CloudBees will support these releases using the same policy as a Jenkins LTS release (below)
  2. Jenkins LTS (up to 1 year old) - The Jenkins community publishes a Long Term Support release every three months, which are supported by CloudBees for up to a year. CloudBees will fix deliver fixes in the next point release of the LTS if the fix meets the community LTS criteria.
  3. Jenkins Weekly releases -The Jenkins community publishes weekly releases of the latest Jenkins code. If you are running a weekly release and have an issue which is fixed in a subsequent weekly release, we will ask you to upgrade to at least that version. We will only fix issues reproducible in the latest Jenkins-tip.
Further Clarifications
  • For Jenkins OSS (non LTS versions), we fix issues only in Jenkins-tip. The customer must verify that the issue exists on Jenkins-tip and will have to upgrade to the Jenkins-tip to get fixes. In other words, if the current version is 1.564 and you are running on 1.505, we expect you to upgrade to 1.565 (or later) to get the fix, if you verified that issue exists on 1.564.
  • For Jenkins LTS, a similar rule applies as above. We expect the customer to be on one of the CloudBees supported LTS versions and confirm that the issue exists.
    • If you are on an older build of supported LTS, we encourage you to upgrade to the latest build to verify issue exists before we can provide a fix for it.
  • OSS plugins follow the core model. If there is an issue with a particular plugin, we expect you to upgrade to the latest tip and verify that the issue exists. We will provide a fix on the tip and expect customers to upgrade their plugin to the latest version.
Have more questions? Submit a request


Please sign in to leave a comment.