CodeArts Pipeline Best Practices
This document includes best practices for using CodeArts Pipeline in common scenarios. Each practice is given a description and procedure.
Practice |
Description |
---|---|
Fixing a Bug for Quick Release Through a Change-triggered Pipeline |
Use a change-triggered pipeline to fix a bug and quickly release the fix. |
Configure code check thresholds and apply pass conditions to a stage for automated checks. |
|
Transferring CodeArts Pipeline Parameters to CodeArts Build and CodeArts Deploy |
Transfer a pipeline version number parameter to a CodeArts Build task and a CodeArts Deploy task. |
Create a repository tag through the pipeline contexts. |
|
Configuring a Pipeline Gate for a Code Repository Merge Request |
Configure an automated pipeline gate for merge requests to improve code quality and team collaboration efficiency. |
You can manage CodeArts Pipeline's project-level and resource-level permissions. This practice describes how to configure resource-level permissions. |
|
This practice describes how to connect code check, build, and deployment tasks in a DevOps Full-Process Sample Project for continuous delivery. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot