Upgrading from Jenkins®
This section will cover upgrading from Jenkins to CloudBees Jenkins Team.
Similar to Jenkins, CloudBees Jenkins Team can run as a stand-alone Java process, inside of a Java servlet container engine such as Jetty, or even as a Docker container. Regardless of the configuration, please ensure the machine running CloudBees Jenkins Team has met the system requirements before continuing on.
The instructions below assume that the Jenkins instance version is a recent LTS, on top of which CloudBees Jenkins Team is based. For example, CloudBees Jenkins Team 2.46.2.1 is itself based on Jenkins 2.46.2 and is therefore a straight-forward upgrade. If the Jenkins version is one of the "weekly" releases, or more than 3-6 months old, please contact CloudBees Support for guidance on the most appropriate upgrade procedures for the Jenkins instance.
Upgrading in place
Linux
When upgrading from Jenkins on Linux, this guide assumes that the current Jenkins instance is using the Jenkins project’s official Linux (rpm, deb) packages, and that the upgrading CloudBees Jenkins Team instance will also use Linux packages.
These instructions also assume that the home directory, commonly referred to as
JENKINS_HOME
in configuration scripts and documentation, is
/var/lib/jenkins
.
Red Hat / CentOS
Upgrading from Jenkins to CloudBees Jenkins Team on Red Hat-based systems requires removing the
previously installed jenkins
package in favor of the cjt
package.
yum remove jenkins (1)
ln -s /var/lib/jenkins /var/lib/cjt (2)
-
Remove the previously installed
jenkins
package from the system. -
Create a symbolic link to the old
JENKINS_HOME
in order for CloudBees Jenkins Team to re-use the same home directory and its contents.
Next, follow the Red Hat installation instructions. Once
installation is complete (yum install cjt
), the ownership of the previous
JENKINS_HOME
will need to be changed to the cjt
user:
chown -R cjt:cjt /var/lib/jenkins
If there were edits made to /etc/sysconfig/jenkins
, the removal of the
jenkins
package will cause these changes to be saved into /etc/sysconfig/jenkins.rpmsave
.
Manually review this file, and copy the appropriate settings into
/etc/sysconfig/cjt
.
After these steps have been completed, CloudBees Jenkins Team can be started with service cjt
start
and the Post-Upgrade Tasks completed.
Debian / Ubuntu
Upgrading from Jenkins to CloudBees Jenkins Team on Debian-based systems requires removing the
previously installed jenkins
package in favor of the cjt
package.
apt-get remove jenkins (1)
ln -s /var/lib/jenkins /var/lib/cjt (2)
-
Remove the previously installed
jenkins
package from the system. -
Create a symbolic link to the old
JENKINS_HOME
in order for CloudBees Jenkins Team to re-use the same home directory and its contents.
Next, follow the Debian installation instructions. Once
installation is complete (apt-get install cjt
), the ownership of the previous
JENKINS_HOME
will need to be changed to the cjt
user:
chown -R cjt:cjt /var/lib/jenkins
If there were edits made to /etc/default/jenkins
, please review this file,
and copy the appropriate settings into /etc/default/cjt
.
After these steps have been completed, CloudBees Jenkins Team can be started with service cjt
start
and the Post-Upgrade Tasks completed.
openSUSE / SUSE Linux
Upgrading from Jenkins to CloudBees Jenkins Team on openSUSE-based systems requires removing the
previously installed jenkins
package in favor of the cjt
package.
zypper remove jenkins (1)
ln -s /var/lib/jenkins /var/lib/cjt (2)
-
Remove the previously installed
jenkins
package from the system. -
Create a symbolic link to the old
JENKINS_HOME
in order for CloudBees Jenkins Team to re-use the same home directory and its contents.
Next, follow the openSUSE installation instructions. Once
installation is complete (zypper install cjt
), the ownership of the previous
JENKINS_HOME
will need to be changed to the cjt
user:
chown -R cjt:cjt /var/lib/jenkins
If there were edits made to /etc/sysconfig/jenkins
, the removal of the
jenkins
package will cause these changes to be saved into /etc/sysconfig/jenkins.rpmsave
.
Manually review this file, and copy the appropriate settings into
/etc/sysconfig/cjt
.
After these steps have been completed, CloudBees Jenkins Team can be started with service cjt
start
and the Post-Upgrade Tasks completed.
Stand-alone .war
While it is strongly recommended that administrators rely on the native
packages above, CloudBees Jenkins Team can be run as a stand-alone .war
file with an existing
JENKINS_HOME
.
Follow the Stand-alone installation instructions to
download cjt.war
. When running the .war
, be sure to set the JENKINS_HOME
environment variable to the existing Jenkins directory, for example:
JENKINS_HOME=/var/lib/jenkins java -jar cjt.war
Post-Upgrade Tasks
After starting the CloudBees Jenkins Team instance, logging in as an administrator will launch the set up wizard to complete the upgrade from Jenkins.
Follow the on-screen instructions for requesting, or configuring a license.

Once the license is configured, the instance will have completed its upgrade to CloudBees Jenkins Team. Depending on the previous Jenkins configuration, CloudBees Jenkins Team may suggest upgrades or security configuration changes. To learn more about these suggtestions, continue on to the CloudBees Assurance Program.
Online version published by CloudBees, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project.
Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.
Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps.
While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.