Help Center/ CodeArts Pipeline/ Service Overview/ Functions
Updated on 2025-10-27 GMT+08:00
View PDF
Share

Functions

This section outlines the key functions supported by CodeArts Pipeline. You can check if a certain function is available in a region on the console.

Pipeline orchestration

Orchestrate other automated tasks of other services. You can orchestrate stages and jobs when you create, clone, or edit a pipeline. For details, see Orchestrating Pipeline Jobs.

Pass conditions

Set rules and policies to decide in what conditions a pipeline can complete the current stage. For details, see Configuring a Rule and Configuring a Pipeline Policy.
  • A rule defines different comparison operators based on extension thresholds to determine whether to apply the extension output to stage pass conditions. Multiple such rules constitute a policy.
  • A policy is a set of rules defined as different condition templates for a step extension. Each policy can be applied to multiple pipelines. There are tenant-level policies and project-level policies. You can use them to control pipeline runs for high-quality delivery.

Execution Control

Configure event triggers, scheduled tasks, webhooks, and concurrent execution policies for a pipeline. For details, see Configuring Pipeline Execution Plans.

  • Event trigger
    • Code commit: You can filter branches and paths by including or excluding specific ones. Target branches and paths will be monitored for code commits.
    • Merge request: You can filter branches and paths by including or excluding specific ones. Target branches and paths will be monitored for merge request events such as MR creation, updating, reopening, and code merge.
    • Tag creation: You can filter tags by including or excluding specific ones. The associated code repository will be monitored for tag creation.
  • Scheduled task

Set a specific time to automatically trigger a pipeline.

  • Webhook

Configure webhooks to automatically trigger a pipeline through a third-party system.

  • Concurrency

By default, five concurrent executions are allowed in a pipeline. Excess instances will not be executed. Alternatively, you can change the maximum number of concurrent instances (running and paused).

Parameter Management

Pipeline parameters can be transferred among jobs. By configuring pipeline parameters, you can streamline data of build, deployment, and API test jobs. The following describes different types of parameters. For details, see Configuring Pipeline Parameters
  • Predefined parameters: They are preconfigured by the system and cannot be configured, deleted, or edited.
  • Custom parameters: You can add parameters of string, enumeration, or auto-increment type.
  • Parameter groups: You can associate all pipelines in the same project with a parameter group.

Permission Management

Configure permissions for a single pipeline by role or user. For details, see Configuring Pipeline Permissions.

  • By default, role permissions of a pipeline are the same as those of the project that the pipeline belongs to. A user with permissions to edit or execute pipelines can also check pipelines.
  • The permissions of the project creator and pipeline creator cannot be changed.
  • By default, user permissions automatically synchronize with role permissions. If user permissions are changed, the new user permissions overwrite role permissions.

Notifications

Configure event notifications (system messages, Feishu, WeCom, and DingTalk notifications) for a pipeline. For details, see Configuring Pipeline Notifications.