Upgrading CloudBees Jenkins Enterprise
| CloudBees will no longer be supporting CloudBees Jenkins Enterprise 1.x after July 30, 2020. This end-of-life announcement allows CloudBees to focus on driving new technology and product innovation for CloudBees CI. For information on moving to CloudBees CI, please refer to CloudBees Jenkins Enterprise 1.x to CloudBees CI on modern cloud platforms migration guide which has been created to help you with the migration process. Existing customers can also contact their CSM to help ensure a smooth transition. |
Upgrading CloudBees Jenkins Enterprise consists of the following steps:
-
Download a new CloudBees Jenkins Enterprise release
-
Install the new release locally
-
Upgrade the CloudBees Jenkins Enterprise project
-
run
cje upgrade-projectwithin the CloudBees Jenkins Enterprise project to upgrade the project
-
-
Upgrade CloudBees Jenkins Enterprise components (see notice below)
-
run
cje upgrade
-
Upgrade CloudBees Jenkins Enterprise Components Notice
During the upgrade of components, Operations Center might become unavailable for a few minutes. Several internal services will be upgraded and restarted. Services such as the routing service might make some components of the cluster inaccessible for a few seconds.
You should perform the upgrade at the appropriate time in order to minimize the inconvenience to users.
Note for OpenStack and VMWare users upgrading from 1.6.0 or later
If you are using CloudBees Jenkins Enterprise on OpenStack or VMWare and you are upgrading from CJE 1.6.0 or later, then you must login to each of the workers in your cluster and log in to the Red Hat Subscription Manager so that the required Red Hat updates can be downloaded. Here is the procedure:
STEP 1: Use DNA to list your servers. You can use the DNA servers command to list the machines that are part of your cluster. From the command-line change directory into your CJE project:
$ cd my-project
Then run the DNA servers command:
$ dna servers castle cjoc cloud-resources-verification controller-1 elasticsearch elb elbi keypairs palace route53 security-groups storage storage-bucket tiger vpc worker-1 worker-2
In the above example, there are two workers, worker-1 and worker-2.
STEP 2: Use DNA to connect to each worker. You can use the DNA connect command to establish an SSH connection to each worker. For example:
$ dna connect worker-1
Since the project contains the right keys for accessing your workers you will be connected to the worker securely, but without any password prompt.
STEP 3: Login Red Hat Subscription Manager on each worker. Once you are logged into a worker use the subscription-manager command to log in to the Red Hat service. You must specify your username and password as follows:
$ subscription-manager register --username <username> --password <password> --auto-attach
Once that is done for each worker, you can proceed with the CloudBees Jenkins Enterprise upgrade.