Function Overview

CodeArts Pipeline provides visualized continuous integration and continuous delivery (CI/CD) pipelines that can be orchestrated. It helps enterprises quickly realize continuous delivery and efficient automation in DevOps, shortens the time to market (TTM) of applications, and improves R&D efficiency.

CodeArts Pipeline is essentially a visualized and automated task scheduling platform. It needs to be used together with automated tasks of services such as CodeArts Build, CodeArts Check, CodeArts TestPlan, and CodeArts Deploy in CodeArts. You can orchestrate these automation tasks based on your requirements, such as application deployment in the development, test, or production environment. After the tasks are configured, they can be automatically triggered, scheduled, and executed, avoiding frequent and inefficient manual operations.

A pipeline can manage and orchestrate automatic tasks of other services. You can orchestrate pipeline stages and tasks based on production and delivery workflows when creating, copying, and editing pipelines.

An associated pipeline can be automatically executed when the following conditions are met.

• Continuous integration
• Code is committed in an associated code repository. The related branch and path of changed files meet inclusion and exclusion policies.
• A tag is created in an associated code repository. The created tag meets inclusion and exclusion policies.
• Merge request (MR)

An MR event is triggered to create, update, merge, or re-open code in an associated code repository. The related branch is in the configured scope. The branch and path of changed files meet inclusion and exclusion policies.

• Scheduled execution

The execution date and time is configured and reached.

Pipeline parameters can be transferred (referenced by ${parameter name}) for unified data flows among tasks. You only need to configure pipeline parameters to streamline data for tasks such as build, deployment, and API test. Pipeline parameters are classified into the following types:

• Custom parameters: You can customize character string, enumeration, auto-increment, and host group types.
• System parameters: Default parameters do not need to be defined and cannot be deleted or modified. These parameters include PROJECT_ID, PIPELINE_ID, PIPELINE_NUMBER, COMMIT_ID and TIMESTAMP.

Pipeline permissions can be configured by role and personnel.

• The permissions of project creators and pipeline creators cannot be changed.
• Personnel permissions are prioritized over role permissions.
• The view permission is enabled by default and cannot be disabled.
• If the run permission is disabled, edit and delete permissions are disabled at the same time.
  
• If the edit permission is enabled, the run permission is enabled at the same time.
• If the edit permission is disabled, the delete permission is disabled at the same time.
• If the delete permission is enabled, edit and run permissions are enabled at the same time.

You can configure message notifications to send service updates or emails to related personnel when a pipeline is deleted, fails to be executed, is successfully executed, or the configuration is updated. Managing the Recycle Bin.