Migrating from CloudBees Jenkins Distribution to Jenkins LTS

2 minute read

CloudBees no longer supports CloudBees Jenkins Distribution as of February 24, 2021. Please refer to the following step-by-step documentation for Migrating from CloudBees Jenkins Distribution to Jenkins LTS. The increased alignment between CloudBees Jenkins Distribution and Jenkins means users will experience zero impact to Pipeline execution. Existing customers can also contact CloudBees Support to help ensure a smooth transition.

Please see About the CloudBees Jenkins Distribution retirement for more information.

Follow these steps to migrate from CloudBees Jenkins Distribution to Jenkins LTS.

This document explains how to migrate from a CloudBees Jenkins Distribution WAR file installation to a Jenkins installation. If you are using another type of distributable, such as RPM, Suse, or Docker, the logic is the same.

CloudBees Jenkins Distribution includes some specific libraries or plugins that prevent a Jenkins controller from starting correctly. These files need to be removed from the JENKINS_HOME so a Jenkins WAR file can be run instead.

To migrate from CloudBees Jenkins Distribution to Jenkins LTS:

  1. Download an LTS version of Jenkins that is based on the same version as the CloudBees Jenkins Distribution version you are using. For example, if you are using CloudBees Jenkins Distribution, download Jenkins LTS 2.249.2.

  2. Open your browser at https://<yourControllerUrl>/script and run the following script:

    UpdateSite site = new UpdateSite("default", "https://updates.jenkins.io/update-center.json")
  3. Stop your CloudBees Jenkins Distribution controller.

  4. From the ${JENKINS_HOME} directory for this CloudBees Jenkins Distribution, run the following shell code to remove specific files and directories:

    # If JENKINS_HOME is undefined, `cd` into the home directory of CloudBees Jenkins Distribution, and run
    # export JENKINS_HOME=$( pwd )
    mkdir $CB_REMOVE_DIR
    mv updates $CB_REMOVE_DIR
    cd plugins
    mv cloudbees-analytics* \
       cloudbees-assurance* \
       cloudbees-administrative-monitors* \
       cloudbees-license* \
       cloudbees-uc-data-api* \
       cloudbees-support* \
       nectar-license* \
  5. Start the downloaded Jenkins WAR using the same method you used before for CloudBees Jenkins Distribution.