Creating a Pipeline

Updated 4 months ago by Copado Solutions

Copado enables you to create a pipeline using different options: 

  • The pipeline wizard (this option only applies to Salesforce pipelines).
  • The New button on the Pipelines tab.
  • The Pipeline subtab on the Getting Started page.
  • Cloning an existing pipeline

In this article, you will learn how to create a pipeline using the last three options. If you want to use the pipeline wizard, review the Pipeline Wizard article.

Creating a Pipeline from the Pipelines Tab

If you are building a multi-cloud pipeline, you can easily create your pipeline using the New button on the Pipelines tab since some of the steps performed by the wizard are not required for this type of pipeline. However, you can use the option for both Salesforce and non-Salesforce pipelines. 

To create a new pipeline, follow the steps below:

  1. Navigate to the Pipelines tab and click on New.
  2. Give your pipeline a name.
  3. Flag the Active checkbox.
  4. Select a Git Repository record. If you have not created a Git Repository record yet, review the article Git Repository Overview.
  5. Select the main branch, usually master (main if you are using GitHub as your provider).
  6. Select a platform (e.g., Heroku).
  7. If you are building a multi-cloud pipeline, select a promotion and a deployment automation template in the Promotion Automation and Deployment Automation fields.
    If the out-of-the-box templates don’t suit your needs, and you need to add additional parameters, you can clone these templates and select the cloned template in these two fields.
  8. If you are working with Copado DX, you can enable it in the Copado DX section.
  9. Once you are done, click on Save.

Now that you have created the Pipeline record, go ahead and create the pipeline connections to connect the different environments. Review the Pipeline Connections article for more information about how to do this.

Creating a Pipeline from the Getting Started Page

  1. Navigate to the Getting Started tab and locate the Pipeline subtab.
  2. Click on New Pipeline:
  3. Give your pipeline a name.
  4. Select a platform.
  5. Select a Git Repository record. If you don’t have one yet, create a new one.
  6. Specify the main branch.
  7. Flag the Active checkbox.
  8. Click on Create.
  9. Go ahead and create the pipeline connections by clicking on New Pipeline Connection.
  10. Once you are done, navigate to the newly created Pipeline record by clicking on the new tab icon. There, you can select the promotion and deployment automation templates and add the system properties if you are building a  non-Salesforce pipeline, and further customize your pipeline.

Cloning a Pipeline with Environments

Some clouds, such as MuleSoft or Heroku, require a different pipeline for each application. Therefore, if you have multiple applications, you need to build various pipelines. To simplify the process of creating new development pipelines, you can use the button Clone with Environments on the Pipeline record page. After you have created your first pipeline, you can use this option to create other pipelines:

  1. Navigate to an existing pipeline.
  2. Click on Clone with Environments:

    Clone with Environments button
  3. By default, Copado assigns this cloned pipeline the name Clone of [your pipeline name], but you can update it and give it a more relevant name:

    Clone with Environments popup
  4. In multi-cloud pipelines, you usually have a different repository per each application. If this is the case, remove the existing Git Repository record from the modal and select a different one (if you don’t have a Git Repository record, follow the article referenced in the section above to create a new one).
  5. Update the name of the environments and branches as needed.
  6. Click on Save.
  7. Once you are done cloning the pipeline, there are some other steps you need to follow:
    1. By default, the cloned pipeline is inactive, so edit it and flag the Active checkbox.
    2. System properties in multi-cloud pipelines are also cloned together with the environments, however, the value is empty. Navigate to the System Properties related list in each of the environments and update them as required.
    3. If you are cloning a Salesforce pipeline:
      1. Authenticate the credential for the new pipeline's production org
      2. Navigate to the cloned Pipeline record page and edit the pipeline connection of the production environment.
        1. Remove the pre-selected environment from the destination environment lookup and select the environment record corresponding to the new pipeline production credential.
      3. Navigate to the Pipeline Configuration page and authenticate all the environments by clicking the blue key icon on each environment box.


How did we do?