Help Center/ CodeArts Pipeline/ Best Practices/ CodeArts Pipeline Best Practices
Updated on 2025-08-13 GMT+08:00

CodeArts Pipeline Best Practices

This document includes best practices for using CodeArts Pipeline in common scenarios. Each practice is given a description and procedure.

Table 1 CodeArts Pipeline best practices

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.

Configuring Pass Conditions for Automated Code Checks

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.

Creating Tags for Code Repositories Through Pipelines

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.

Managing Pipeline Permissions

You can manage CodeArts Pipeline's project-level and resource-level permissions. This practice describes how to configure resource-level permissions.

HE2E DevOps Practice: Configuring a Pipeline

This practice describes how to connect code check, build, and deployment tasks in a DevOps Full-Process Sample Project for continuous delivery.