Migrating to Jenkins Enterprise by CloudBees from Open Source Jenkins

Apparently a few of you have been wondering ‘what is involved in moving from Jenkins OSS to CloudBees’, and you’re in luck: it’s super easy! On a scale of difficulty, with 10 being quantum computing and 1 being writing ‘hello world’ in Python, it’s probably a 2 or 3.

I won’t bore you with too much detail (which can be found here), but if you’re interested in making this migration, you have 2 options. The one you pick really depends on you and your needs:

Scenario 1: Your Jenkins version is an LTS version newer than the latest version on this list
In this case, you’ll want to install our “Enterprise by CloudBees” plugin. Simply go to your Plugin Manager (“Manage Jenkins” » “Manage Plugins”) and go to the “Available: tab. Install the plugin by checking the box next to the “Enterprise by CloudBees” and selecting the “Install without restart” option.


After installing this “meta-plugin”, you’ll now need to go to “Manage Jenkins” and select the “Install Jenkins Enterprise by CloudBees” menu option.



You’ll now have the option to pick whether you’d like to install all of the plugins packaged as a part of the Jenkins Enterprise by CloudBees offering or whether you’d prefer to just install the license for now. With the latter, you can choose which specific plugins you’d like to install later from your plugin manager.


Regardless of which option you pick, you’ll see text updates appear on screen as the required steps are completed (adding the CloudBees update center, installing plugins, etc). 


Afterwards, you’ll be prompted to input a valid license to continue.


If you’ve already purchased a license from someone in sales, simply select the third option (“I already have a  license key”) and enter your license key + certificate here. 

If you haven’t yet purchased a license, then you’ll need to register for an evaluation here by selecting the first option and entering your name + email.

And that’s it! Your OSS Jenkins master will now be a Jenkins Enterprise by CloudBees master.

Scenario 2: Your Jenkins version is an LTS version older than the latest version on this list

You can either upgrade using the meta-plugin outlined in scenario 1, or you can install the Jenkins Enterprise by CloudBees WAR with a compatible version number to the LTS version you have now - for example, you’d pick the Jenkins Enterprise 1.554 WAR if you’re running OSS Jenkins 1.554.

Once you download the WAR, you would just need set its JENKINS_HOME to be the same as the JENKINS_HOME your OSS Jenkins is currently working from and then run it.

Once you run the WAR, any plugins in your existing OSS installation’s JENKINS_HOME will be updated to the version bundled with the Jenkins Enterprise by CloudBees WAR.

Alternative installation options

  • openSUSE users can run:


sudo zypper addrepo http://nectar-downloads.cloudbees.com/nectar/opensuse/ jenkins
followed by
sudo zypper install jenkins
  • Red Hat/Fedora/CentOS users can download an RPM package by adding the key to their system:
sudo rpm --import http://nectar-downloads.cloudbees.com/nectar/rpm/jenkins-ci.org.key
Then adding the repository:
sudo wget -O /etc/yum.repos.d/jenkins.repo http://nectar-downloads.cloudbees.com/nectar/rpm/jenkins.repo
Then installing Jenkins Enterprise by CloudBees:
sudo yum update
sudo yum install jenkins
  • Ubuntu/Debian users can install Jenkins Enterprise as a Debian package by adding the keys to their system:
wget -q -O - http://nectar-downloads.cloudbees.com/nectar/debian/jenkins-ci.org.key | sudo apt-key add -
Then adding the repository. If you have already added open-source Hudson/Jenkins as a repository, be sure to remove it to avoid Jenkins Enterprise by CloudBees from being overwritten by them:
echo deb http://nectar-downloads.cloudbees.com/nectar/debian binary/ | 
sudo tee /etc/apt/sources.list.d/jenkins.list
Then installing Jenkins Enterprise by CloudBees:
sudo apt-get update
sudo apt-get install jenkins
  • Windows users can download a ZIP file from here and execute the setup program inside, then access their instance at http://localhost:8080.

Scenario 3: Your Jenkins version is an LTS version older than 1 year OR is not an LTS version

You’ll need to upgrade to an LTS version that is less than a year old and then follow either of the above instructions.

Blog Categories: 

Add new comment