Migrating from Jenkins LTS to CloudBees Jenkins Distribution

Stop the jenkins service and delete it.

Rename the folder where the jenkins service was running from Program Files (x86)/Jenkins to Program Files (x86)/CloudBeesJenkinsDistribution

Download the cloudbees-jenkins-distribution.zip file, and the SHA256 checksum file.

The checksum file can be used to verify that the cloudbees-jenkins-distribution.zip is correct. Compare the contents of cloudbees-jenkins-distribution.zip.sha256 with the output of the following PowerShell command:

$(CertUtil -hashfile D:\Users\USER\Downloads\cloudbees-jenkins-distribution.zip SHA256)[1] -replace " ",""

Unpack the archive and execute the CloudBees Jenkins Distribution installer, cloudbees-jenkins-distribution.msi.

Download the WAR file for CloudBees Jenkins Distribution; for your operating system and copy it to where you wish to run CloudBees Jenkins Distribution.

Copy the file to the directory where you wish to run CloudBees Jenkins Distribution.

Open a terminal and run the command:

java -jar cloudbees-jenkins-distribution.war

The process output generates a password offset by three rows of asterisks above and below the text. Copy the password. The password is also saved in a directory like /users/<username>.jenkins/secrets/initialAdminPassword, where username is replaced with your username. The exact path may vary depending upon your operating system.

*************************************************************
*************************************************************
*************************************************************

Jenkins initial setup is required. An admin user has been created and a password generated.
Please use the following password to proceed to installation:

d661ea28c6b94406ad627601b6f4aa877

This may also be found at: /Users/<username>/.jenkins/secrets/initialAdminPassword

*************************************************************
*************************************************************
*************************************************************

The terminal portion is complete when the output reads:

INFO: Obtained the updated data file for hudson.tools.JDKInstaller
Jan 24, 2019 4:38:57 PM com.cloudbees.jenkins.plugins.assurance.model.UpdateSiteDataProvider$Value get
INFO: Beekeeper is parsing UpdateSite cloudbees-jenkins-distribution-offline
Jan 24, 2019 4:38:57 PM com.cloudbees.jenkins.plugins.assurance.model.UpdateSiteDataProvider$Value get
INFO: Beekeeper is parsing UpdateSite cap-cloudbees-jenkins-distribution
Jan 24, 2019 4:42:42 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started telemetry collection
Jan 24, 2019 4:42:42 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished telemetry collection. 1 ms

Create a temporary directory on your local workstation, because you can’t directly copy a directory within a cluster into another directory within the same cluster:

shell% mkdir /tmp/jenkins_home_data

Use the kubectl get pods command to retrieve the list of pods in the Kubernetes cluster:

shell% kubectl get pods -A

NAMESPACE     NAME                             READY   STATUS    RESTARTS   AGE
default       cicd-jenkins-74b85c44cc-zsq6r    1/1     Running   0          15m
kube-system   aws-node-4gz5w                   1/1     Running   0          19m
kube-system   aws-node-5smgn                   1/1     Running   0          19m
kube-system   aws-node-7cjdc                   1/1     Running   0          19m
kube-system   coredns-7bcbfc4774-2j6lj         1/1     Running   0          31m
kube-system   coredns-7bcbfc4774-cgxrl         1/1     Running   0          31m
kube-system   kube-proxy-2pkw6                 1/1     Running   0          19m
kube-system   kube-proxy-528n4                 1/1     Running   0          19m
kube-system   kube-proxy-dt4d8                 1/1     Running   0          19m
kube-system   tiller-deploy-54fc6d9ccc-tg7fd   1/1     Running   0          16m

Use the kubectl cp command to copy the Jenkins home directory to the temporary directory, substituting the appropriate NAMESPACE and NAME from the output of the kubectl get pods command:

shell% kubectl cp <NAMESPACE>/<NAME>:/var/jenkins_home /tmp/jenkins_home_data

Finally, use the kubectl cp command to copy the old Jenkins home information into the new location, again substituting the appropriate NAMESPACE and NAME from the output of the kubectl get pods command:

shell% kubectl cp  /tmp/jenkins_home_data/ NAMESPACE/POD-NAME:/var/cloudbees-jenkins-distribution

Add the CloudBees Helm Chart Repository to your Helm installation:

shell% helm repo add cloudbees https://charts.cloudbees.com/public/cloudbees

Update your local Helm Chart Repository cache, which improves the performance of commands like helm search. To update the cache:

shell% helm repo update

After you’ve added the CloudBees repository and updated the Chart Repository Cache, you can upgrade the instance.

Upgrade the instance with the helm upgrade command, substituting the appropriate PV-NAME from the output of the kubectl get pv command, and providing a value for RELEASE-NAME (if you are uncertain about the instance’s name, use the helm list command to retrieve it):

shell% helm upgrade --set persistence.existingClaim=PVC-NAME RELEASE-NAME cloudbees/cloudbees-jenkins-distribution

Migrating to Helm

Updating the deployment and changing the docker image

Open a browser to http://localhost:8080.

Open the initialAdminPassword file using the location displayed on the Unlock Jenkins page.

Copy the password from the file.

Open a browser to http://localhost:8080.

On the Unlock Jenkins page, paste in the Administrator password retrieved in the previous section in the field. Press Continue.

Select the appropriate registration option on the License page.

Select Install suggested plugins on the Customize Jenkins page to install the curated set of plugins recommended by CloudBees.

The Getting Started page displays the setup progress. If any updates are available, you will also be given the option to upgrade. These upgrades may also be performed at a later time using the Beekeeper Upgrade Assistant.

On the Create First Admin User page, enter a username, password (twice), full name, and email address for the first admin user. Press Save and Continue.

Enter a new value for the Jenkins URL on the Instance Configuration page. You may choose to use the default value or to enter a new URL. Press Save and Finish.

You may be asked to reboot your system.