This document describes the deployment pipeline in CODING Continuous Deployment (CODING-CD).
You must activate the CODING DevOps service for your Tencent Cloud account before you can use CODING Project Management (CODING-PM).
The deployment pipeline is the core module of Continuous Deployment. It enables arbitrary combination of stages in any sequence, while maintaining excellent flexibility, consistency, and repeatability.
You can configure a fully automated pipeline or add manual judgment conditions at certain stages. In addition, the pipeline can be triggered automatically by various events, such as webhooks and other pipelines.
Go to CODING-CD Console, and then click the deployment pipeline icon in the lower-right corner of the application card.
Basic configurations of an application can be regarded as the starting point for a full build. This allows you to set trigger conditions, or configure the notifications for a pipeline.
The auto trigger supports CODING Docker Repository Trigger, TCR Personal Repository Trigger, and Git Repository Trigger.
Go to the Deployment Pipeline Configuration page, and then click Add Startup Parameters.
On the Deployment Pipeline Configuration page, click + to add a new stage, and select the stage type from the list on the right.
After the pipeline configuration is complete, you can use the preset trigger to execute the pipeline automatically, or manually trigger the pipeline by submitting a release order in Continuous Deployment.
You can delete, disable, or lock a deployment pipeline, view its earlier versions, and edit JSON configuration.
If you click "Delete", the pipeline will be deleted.
If you click "Disable", the pipeline can neither be launched via any trigger nor triggered manually. You can disable a pipeline for the team or a certain project.
If you click "Lock", the pipeline cannot be edited through the CODING-CD Console. You can specify whether the pipeline can be updated through API.
When a new pipeline configuration is saved, the previous version will be added to revision history. On the Revision History page, you can make a comparison between different versions, and restore to any earlier version.
Any changes made in the CODING-CD Console are saved in JSON files. You can add new fields to a pipeline, or edit the JSON content to customize configuration items not displayed in UI.
This allows you to edit a deployment pipeline in the text box, but it may affect the availability of the pipeline. We support restoring to any specific version in the revision history.