DEV@cloud to CloudBees Core migration guide

DEV@cloud to CloudBees Core migration guide

On December 15th 2018 at 12:30am UTC, all DEV@cloud services were terminated.

Customers with extended termination dates will need to back up their instance and migrate it to a CloudBees Core or Jenkins instance.

Preparing for your migration

  1. In each of your instances, create a job named _automated-backup. There are two important details about this job:

    1. This job must be manually created, but, once created, will be automatically configured.

    2. After creation, any modification to this job the job will be overwritten without notice.

  2. The _automated-backup job creates a tarball of your content in your Forge repository.

  3. The tarball is accounted for as part of your quota, and, to maintain security, all encryption keys have been removed.

  4. All CloudBees-proprietary plugins are removed to make it easier to migrate to a Jenkins instance.

Download and expand the backup

Download the tarball from your repository, and uncompress it into its own location with:

shell% mkdir jenkins-home
shell% tar xzf TARBALL.tar.gz -C jenkins-home

Remove references to CloudBees proprietary plugins

All proprietary CloudBees plugins are removed before the tarball is generated, but there are some remaining elements that must be manually removed if you are moving to Jenkins (and not CloudBees Core):

  1. In jenkins-home/nodeMonitor.xml, remove the reference to com.cloudbees.jenkins.plugins.foldersplus.SecurityTokensNodeProperty_-NodeMonitorImpl.

  2. In jenkins-home/config.xml, disable security, as shown here: Disabling security.

Install required plugins

Next, install the following plugins:

  1. token-macro

  2. cloudbees-folder

  3. async-http-client

To acquire and install these plugins, you have two options:

Command-line install
shell% curl -LSs \ -o jenkins-home/plugins/token-macro.hpi \ -o jenkins-home/plugins/cloudbees-folder.hpi \ -o jenkins-home/plugins/async-http-client.hpi

Reset your credentials

Next, check for any remaining credentials entries: remember that even if youu values in password fields, those values were encrypted with a key that no longer exists.

If you find any password values, reset them. Don’t forget to check in folders as well!

Start your new instance

After you’ve completed these steps, you can use your backup’s jenkins-home contents as the JENKINS_HOME in a new Jenkins or CloudBees Core instance.

Once you’ve started the instance, you can find elements of your configuration that may still be referencing proprietary plugins by reviewing $JENKINS_URL/administrativeMonitor/OldData/manage.