Configuring Non-Production Pipelines configuring-non-production-pipelines

Access the Pipelines card from the Cloud Manager home screen. Click +Add and select Add Non-Production Pipeline.

On the Configuration tab of the Add Non-Production Pipeline dialog, select the type of non-production pipeline you with to add.

• Code Quality Pipeline - Create a pipeline that builds your code, runs unit tests, and evaluates code quality but does NOT deploy.
• Deployment Pipeline - Create a pipeline that builds your code, runs unit tests, evaluates code quality, and deploys to an environment.

Provide a Non-Production Pipeline Name to identify your pipeline along with the following additional information.

• Deployment Trigger - You have the following options when defining the deployment triggers to start the pipeline.

  • Manual - Use this option to manually start the pipeline.
  • On Git Changes - This option starts the CI/CD pipeline whenever commits are added to the configured git branch. With this option, you can still start the pipeline manually as required.

If you choose to create a Deployment Pipeline, you must also define the Important Metric Failures Behavior.

• 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 is essentially emulating a user manually rejecting each failure.
• Continue Immediately - If selected, the pipeline procedes automatically whenever an important failure occurs. It is essentially emulating a user manually approving each failure.

Click Continue.

On the Source Code tab of the Add Non-Production Pipeline dialog, you must select which type of code the pipeline should process.

• Full Stack Code
• Targeted deployment

On the Source Code tab, you must define the following options.

• Eligible Deployment Environments - If your pipeline is a deployment pipeline, you must select to which environments it should deploy.
• Repository - This option defines from which git repo that the pipeline should retrieve the code.

• 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 helps you find the matching branches that you can select.

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

• Pipeline - 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 - Execute product functional tests against the development environment.
  • Custom Functional Testing - Execute custom functional tests against the development environment.
  • Custom UI Testing - Execute custom UI tests for custom applications.
  • Experience Audit - Execute Experience Audit

Click Save.

Define the Eligible Deployment Environments.

• If your pipeline is a deployment pipeline, you must select to which environments it should deploy.

Under Source Code, define the following options:

• Repository - This option defines from which git repo that the pipeline should retrieve the code.

• 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.

Click Save.