The deployment pipeline is the core module of Continuous Deployment. Its advantage lies in supporting the combination of stages in any sequence, which provides excellent flexibility, consistency, and repeatability.
Flexibility: Supports serial and parallel control.
Consistency: Supports multiple deployment strategies and rollback, ensuring the release results as expected.
Repeatability: The deployment pipeline can be executed repeatedly, and stages can be copied and used by other deployment pipelines.
Users can configure a fully automated deployment pipeline or add manual judgment conditions at certain stages. Additionally, the deployment pipeline supports automation triggers by various events, such as webhooks and other deployment pipelines.
Create Deployment Pipeline
Go to the Application Center, and click the deployment pipeline icon in the lower-right corner of the application card.
1. Click Create Process in the top right corner.
2. You can copy a pipeline created in another application or create a new one from scratch.
Basic configuration
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.
Auto Trigger
The auto trigger supports CODING Docker Repository Trigger, TCR Personal Repository Trigger, and Git Repository Trigger.
Add deployment pipeline parameters
On the process deployment configuration page, click Add Parameter to start entering parameters.
Add stage
On the Deployment Pipeline Configuration page, click the plus icon to add a new stage. You can select the stage type from the list on the right.
Execute Deployment Pipeline
After configuring the deployment pipeline, you can set it to execute automatically based on the configured triggers or trigger it manually by submitting a release sheet in Continuous Deployment.
Deployment Pipeline Configuration
You can delete, disable, or lock a deployment pipeline, view its earlier versions, and edit JSON configuration.
Delete Deployment Pipeline
After setting, this deployment pipeline will be deleted.
Disable deployment pipeline
Once set, all triggers, including manual triggers, will be disabled from starting the deployment process. You can choose to disable it for the entire team or only within a project.
Lock deployment pipeline
Once the deployment process is locked, no modifications can be made to it in the Application Center.
View revision history
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.
Edit JSON configuration
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.
Note:
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.
