Configuring a Production Pipeline configure-production-pipeline

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization

On the My Programs screen, select the program.

Navigate to the Pipelines card from the Program Overview page and click Add to select Add Production Pipeline.

The Add Production Pipeline dialog box displays. Provide a Pipeline Name to identify your pipeline along with the following options. Click Continue.

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

Important Metric Failures Behavior - During pipeline setup or edit, the Deployment Manager has the option of defining the behavior of the pipeline when an important failure is encountered in any of the quality gates. The available options are:

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

On the Source Code tab 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.

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

• Git Branch - This option defines from which branch in the selected the pipeline should retrieve the code.
  • Enter the first few characters of the branch name and the auto-complete feature of this field will find the matching branches to help you select.
• Ignore Web Tier Configuration - When checked, the pipeline does not deploy your web tier configuration.
• Pause before deploying to Production - This option pauses the pipeline before deploying to production.
• Scheduled - This option allows the user to enable the scheduled production deployment.

Click Continue to advance to the Experience Audit tab where you can define the paths that should always be included in the Experience Audit.

Provide a path to be included in the Experience Audit.

• Page paths must start with /.
• For example, if you would like to include https://wknd.site/us/en/about-us.html in the Experience Audit, enter the path /us/en/about-us.html.

Click Add Page and the path is auto-completed with the address of your environment and added to the table of paths.

Continue to add paths as necessary by repeating the previous two steps.

• You can add a maximum of 25 paths.
• If you do not define any paths, the homepage of the site is included in the Experience Audit by default.

Click Save to save your pipeline.

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.
• Pause before deploying to Production - This option pauses the pipeline before deploying to production.
• Scheduled - This option allows the user to enable the scheduled production deployment. Only available for web tier targeted deployments.

Click Save.