Add a non-production pipeline configuring-non-production-pipelines

Sign into Cloud Manager at experience.adobe.com.

In the Quick access section, click Experience Manager.

In the left side panel, click Cloud Manager.

Select an organization that you want.

On the My Programs console, click a program.

In the left side panel, click Pipelines.

On the Pipelines page, near the upper-right corner, click Add Pipeline > Add Non-Production Pipeline.

On the Configuration tab of the Add Non-Production Pipeline dialog box, select one of the following non-production pipelines you want to create:

• Code Quality Pipeline - Creates a pipeline that builds the code on a GIT branch, runs unit tests, and evaluates code quality without deploying to an environment.
• Deployment Pipeline - Creates a pipeline that builds the code, runs unit tests, evaluates code quality, and deploys to a non-production environment.

Under the Pipeline Configuration section, in the Non-Production Pipeline Name field, type a description for your non-production pipeline.

Under the Deployment Options section, select one of the following deployment triggers that you want to use:

• Manual - Lets you manually start the pipeline.
• On Git Changes - Starts the pipeline when commits are added to the configured Git branch. With this option, you can still start the pipeline manually, as required.

Select the Important Metric Failures Behavior that you want to use.

• Ask every time - This behavior is the default setting and requires manual intervention on any important failure.
• Fail Immediately - If selected, the pipeline is canceled whenever an important failure occurs. It essentially emulates a user manually rejecting each failure.
• Continue Immediately - If selected, the pipeline procedes automatically whenever an important failure occurs. It essentially emulates a user manually approving each failure.

Click Continue.

The remaining steps that you use to complete the configuration of your non-production pipeline depend on the type of source code you choose to use.
On the Source Code tab of the Add Non-Production Pipeline dialog box, select which type of code the non-production pipeline should process.

• I am using Full Stack Code
• I am using Targeted deployment

See CI/CD Pipelines for more information about the types of pipelines.

In the Source Code section, define the following options.

• Eligible Deployment Environments - Available only when you edit a non-production pipeline. If your pipeline is a deployment pipeline, you must select to which environments it should deploy.

• Repository - From the drop-down list, choose the Git repository that the pipeline uses as its source. Cloud Manager builds code from the repository that you choose here.

  note tip
  TIP
  See Adding and Managing Repositories so you can learn how to add and manage repositories in Cloud Manager.

• Git Branch - From the drop-down list, choose which branch in the selected repository the pipeline should build from. The default is main. The pipeline uses the chosen branch as the source for build and deployment. If necessary, click Refresh to update the list of available branches for the selected repository. Use this option if a recently created branch does not appear in the list.

• Build Strategy

  • Full Build - Builds all modules in the repository every time

  • BETA Smart Build - Builds only modules that have changed since the last commit.
    Learn more about using Smart Build in a non-production pipeline.

    note important
    IMPORTANT
    Smart Build is available only for Code Quality pipelines and Dev Full Stack Code deployment pipelines.

• Ignore Web Tier Configuration check box - When checked, the pipeline does not deploy your web tier configuration.

In the Pipeline section, if your pipeline is a deployment pipeline, you can choose to run a testing phase. Check the options that you want to enable in this phase. If none of the options are selected, the testing phase is not displayed during the pipeline’s run.

• Product Functional Testing - Run product functional tests against the development environment.
• Custom Functional Testing - Run custom functional tests against the development environment.
• Custom UI Testing - Run custom UI tests for custom applications.
• Experience Audit - Run Experience Audit

Click Save.

Under the Source Code section, define the following options:

• Repository - This option defines from which GIT repository that the non-production pipeline should retrieve the code.

  note tip
  TIP
  See Adding and Managing Repositories so you can learn how to add and manage repositories in Cloud Manager.

• Git Branch - This option defines from which branch in the selected pipeline should retrieve the code. Enter the first few characters of the branch name and the auto-complete feature of this field. It finds the matching branches that you can select.

• Code Location - This option defines the path in the branch of the selected repo from which the pipeline should retrieve the code.

If you enabled Experience Audit, click Continue to advance to the Experience Audit tab where you can define the paths that should always be included in the Experience Audit.

• If you enabled Experience Audit, see the document Experience Audit for details on how to configure.
• If you did not, skip this step.

Click Save to save the pipeline.