Skip to main content

Clone CI/CD pipeline to the same target or securely between a new or other existing target.

In severalsome situations,cases, you mightmay want to moveclone a deployed CI/CD pipeline from one target to another one.or Onthe same target for distributing your project pipeline in Production, Staging, and Test environments.

When using Elestio, you can safely moveclone a pipeline between identical, new, or existing targets even if the pipelineit contains data.


To consider a few situations:

  • Your CI/CD target is overloaded (too much CPU/RAM usage)
  • You want to move a workload from one location to another
  • Your CI/CD target is down

In all those situations you will want to move some or all of your pipelines to another CI/CD target (new or existing one).

Moveclone a CI/CD PipelinePipeline, tofollow anotherthese CI/CDsteps:

    1) From the Elestio dashboard, click on CI/CD in the left menu then click on your pipeline to open the overview.

    Managed Service Dashboard (11).pngScreenshot 2022-11-04 182320.png


    2) Click on the MoveClone Pipeline button

    Screenshot 2022-09-29 191235.pngScreenshot 2022-11-04 183801.png

    From there


    You can indicatethen ifidentify whether you want to moveclone your pipeline to newthe same, new, or existing infrastructure or existing infrastructure.VM/target.

    If you selectchoose Existingto infrastructureDeploy on an existing VM, you have tomust select in the list the existing CI/CD target,target forfrom the list; if you choose to Deploy on a new infrastructureVM, you willmust have to indicatespecify the Provider / Region / VM Size to create.create; and if you want to clone on the same VM, choose to Deploy on an existing VM and select the same target name from the targets dropdown.

    When cloning a pipeline for all VMs (same, new, or existing), make sure the new pipeline name differs from the source pipeline name.

    Managed Service Dashboard (12).pngManaged Service Dashboard.png

    MovingCloning a pipeline to an existing CI/CD target is FREE. 

    When you moveclone a pipeline we are automating those operations:

    1. Do a fresh backup of your data on S3 (Backups must be activated before movingcloning your pipeline)
    2. Shuttingif downyou choose to copy the app stack of the
    3. (New infrastructureVM only): Deploying a new VM that will be used as the new CI/CD target
    4. Deploy the pipeline (from source or from docker registry) on the new target
    5. Restore the latest backup we took at step one from S3
    6. Check if the pipeline is running correctly on the new target, if not cancel the operation and send a warning email
    7. Change the DNS entry to point to the new target IP address
    8. Send a confirmation email when the pipeline is restoredcloned and ready

    The whole process usually takes less than 3 minutes, but it can last longer ifin theresome is a lot of data to back up/restore.cases.