DEV@cloud to CloudBees Core migration guide
On December 15th 2018 at 12:30am UTC, all DEV@cloud services were terminated: DEV@cloud End Of Life announcement
Customers with extended termination dates will need to back up their instance and migrate it to a CloudBees Core or Jenkins instance.
In each of your instances, create a job named
_automated-backup. There are two important details about this job:
This job must be manually created, but, once created, will be automatically configured.
After creation, any modification to this job the job will be overwritten without notice.
_automated-backupjob creates a tarball of your content in your Forge repository.
The tarball is accounted for as part of your quota, and, to maintain security, all encryption keys have been removed.
All CloudBees-proprietary plugins are removed to make it easier to migrate to a Jenkins instance.
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
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):
jenkins-home/nodeMonitor.xml, remove the reference to
jenkins-home/config.xml, disable security, as shown here: Disabling security.
Next, install the following plugins:
To acquire and install these plugins, you have two options:
shell% curl -LSs \ https://updates.jenkins.io/latest/token-macro.hpi -o jenkins-home/plugins/token-macro.hpi \ https://updates.jenkins.io/latest/cloudbees-folder.hpi -o jenkins-home/plugins/cloudbees-folder.hpi \ https://updates.jenkins.io/latest/async-http-client.hpi -o jenkins-home/plugins/async-http-client.hpi
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!
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
Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.
CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center and DEV@cloud are trademarks of CloudBees, Inc.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about.
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 content, 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 content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.