This document describes the deployment pipeline in CODING Continuous Deployment (CODING-CD).
Prerequisites
You must activate the CODING DevOps service for your Tencent Cloud account before you can use CODING Project Management (CODING-PM).
Open Project
1. Log in to the CODING Console and click Use Now to go to CODING page.
2. On the Workspace homepage, click
on the left to go to the CODING-CD Console.
Function Overview
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.
Flexibility: Supports serial or parallel control
Consistency: Supports multiple deployment strategies and rollback, ensuring the release results as expected
Repeatability: Deployment pipelines can be executed repeatedly, and the stages can be copied to other pipelines.
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.
Create Deployment Pipeline
Go to CODING-CD Console, and then click the deployment pipeline icon in the lower-right corner of the application card.
1. Click the Create Pipeline button in the upper-right corner.
2. You can copy any pipelines created in other applications, or create a new one. CODING also offers sample pipeline templates for Kubernetes and Tencent Cloud Auto Scaling.
Basic Configurations
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
Go to the Deployment Pipeline Configuration page, and then click Add Startup Parameters.
Add stage
On the Deployment Pipeline Configuration page, click + to add a new stage, and select the stage type from the list on the right.
Execute Deployment Pipeline
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.
Deployment Pipeline Configuration
You can delete, disable, or lock a deployment pipeline, view its earlier versions, and edit JSON configuration.
Delete pipeline
If you click "Delete", the pipeline will be deleted.
Disable deployment pipeline
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.
Lock deployment pipeline
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.
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.
Yes
No
Was this page helpful?