SELECT PRODUCT

Migrating from CloudBees Jenkins Platform to CloudBees CI
Migrating from CloudBees Jenkins Enterprise 1.x to CloudBees CI
Introduction
Migrating instances on Kubernetes to Helm
Migrating instances on OpenShift to Helm
Migrating from Helm 2 to Helm 3
Trial guide

Migrating CloudBees Jenkins Platform to CloudBees CI

Migrating a Client Master instance from CloudBees Jenkins Platform to CloudBees CI

Back up your CloudBees Jenkins Platform Client Master instance before starting your migration.
The minimum requirement for such a backup is to save a copy the $JENKINS_HOME directory from your CloudBees Jenkins Platform Client Master instance. If the BUILD_DIRECTORY is outside the $JENKINS_HOME directory, then you must save a copy of this directory as well.

  1. Ensure you have stopped your CloudBees Jenkins Platform Client Master instance.

    sudo service jenkins stop

  2. Install the Client Master for CloudBees CI on traditional platforms.

  3. Create a copy of the jenkins directory (from your old CloudBees Jenkins Platform Client Master installation) for CloudBees CI (named cloudbees-core-cm) and change the ownership of this new directory to the new cloudbees-core-cm user:

    cd /var/lib/
sudo cp -rf jenkins/* cloudbees-core-cm/
cd cloudbees-core-cm/
sudo chown -R cloudbees-core-cm:cloudbees-core-cm .

  4. Start your new CloudBees CI Client Master instance.

    sudo service cloudbees-core-cm start

  5. Uninstall the CloudBees Jenkins Platform Client Master:

    • On Ubuntu or Debian.

      sudo apt-get purge jenkins

    • On Red Hat, CentOS, Fedora or Amazon Linux 2.

      sudo yum remove jenkins

    • On OpenSUSE.

      sudo zypper remove jenkins

  6. ( Optional ) If the migration of your Client Master instance to CloudBees CI ran successfully, you can remove the old CloudBees Jenkins Platform Client Master directory:

    rm -rf /var/lib/jenkins

Migrating an Operations Center Instance from CloudBees Jenkins Platform to CloudBees CI

Back up your CloudBees Jenkins Platform Operations Center instance before starting your migration.
The minimum requirement for such a backup is to save a copy the $JENKINS_HOME directory from your CloudBees Jenkins Platform Operations Center instance. If the BUILD_DIRECTORY is outside the $JENKINS_HOME directory, then you must save a copy of this directory as well.

  1. Ensure you have stopped your CloudBees Jenkins Platform Operations Center instance.

    sudo service jenkins-oc stop

  2. Install the Operations Center for CloudBees CI on traditional platforms.

  3. Create a copy of the jenkins-oc directory (from your old CloudBees Jenkins Platform Operations Center installation) for CloudBees CI (named cloudbees-core-oc) and change the ownership of this new directory to the new cloudbees-core-oc user:

    cd /var/lib/
sudo cp -rf jenkins-oc/* cloudbees-core-oc/
cd cloudbees-core-oc/
sudo chown -R cloudbees-core-oc:cloudbees-core-oc .

  4. Start your new CloudBees CI Operations Center instance.

    sudo service cloudbees-core-oc start

  5. Uninstall the CloudBees Jenkins Platform Operations Center:

    • On Ubuntu or Debian.

      sudo apt-get purge jenkins-oc

    • On Red Hat, CentOS, Fedora or Amazon Linux 2.

      sudo yum remove jenkins-oc

    • On OpenSUSE.

      sudo zypper remove jenkins-oc

  6. ( Optional ) If the migration of your Operations Center instance to CloudBees CI ran successfully, you can remove the old CloudBees Jenkins Platform Operations Center directory:

    rm -rf /var/lib/jenkins-oc
Migrating from CloudBees Jenkins Enterprise 1.x to CloudBees CI