Migrating CloudBees Jenkins Platform to CloudBees Core

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

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 Core on traditional platforms.

  3. Create a copy of the jenkins directory (from your old CloudBees Jenkins Platform Client Master installation) for CloudBees Core (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 Core 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 Core 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 Core

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 Core on traditional platforms.

  3. Create a copy of the jenkins-oc directory (from your old CloudBees Jenkins Platform Operations Center installation) for CloudBees Core (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 Core 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 Core ran successfully, you can remove the old CloudBees Jenkins Platform Operations Center directory:

    rm -rf /var/lib/jenkins-oc
Copyright © 2010-2020 CloudBees, Inc.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 Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. 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.