The user wants to migrate from Jenkins OSS to Cloudbees CI on traditional platforms.
- CloudBees CI (CloudBees Core)
- CloudBees CI (CloudBees Core) on traditional platforms - Client Master
- CloudBees Jenkins Platform - Client Master
- Jenkins LTS
Ensuring you have regular backups of your JENKINS_HOME. The backups should be stored on separate hardware from your Jenkins instance, at a minimum, even better would be an offsite location such as cloud storage.
We also want to take another backup immediately before you start the migration.
Testing if these backups are valid is also critical as if the backup is not valid and we encounter a severe issue during the migration, the way to recover from the failure is to restore from the backup you took immediately prior to the migration. A great way to test the validity of these backups is with a Test environment.
- First, be sure that you have your Cloudbees Core license, you will need it during the migration.
- We recommend to let all running builds complete before you begin to migrate.
- Stop the service.
- Make a new backup of the JENKINS_HOME folder.
- Install the Cloudbees Core (RPM, deb, war file, …). This new service must point to the same OSS JENKINS_HOME folder.
- Start the new service.
- Enter the license and let the recommended plugins to be installed.
At this point, the migration is already finished.
After this, go to
Manage Jenkins -> Beekeeper Upgrade Assistant -> CAP Configuration and ensure
Enroll this instance in the CloudBees Assurance Program is checked. Then go to
Manage Jenkins -> Manage Plugins and under the
Updates tab, upgrade all plugins, and restart the instance.
This way, your plugins will be updated to the recommended version.
To finish with, follow these articles to configure your instance with our recommendations: