Docs

Code Pipeline

Pipeline

Run a pipeline

Code Pipeline supports code source trigger, scheduled trigger, webhook trigger, and manual trigger. You can select the appropriate method to trigger the pipeline based on your specific use case. This article introduces the procedure for manually triggering pipeline execution.

Background information

You can run a pipeline by specifying a branch, tag, or commit ID. Please select as needed.

Termination is supported at any time during pipeline execution. After termination, currently running tasks are canceled immediately, and tasks that have not started will not be executed.

After a task in the pipeline fails to run, the pipeline stops running. Supports retrying from failed tasks; preceding tasks that have already run successfully will not be executed again, which improves pipeline efficiency.

Prerequisites

The pipeline has been created. For specific operations, refer to Create a Pipeline.

Procedure

Select workspace in the left navigation bar.

Click the name of the target workspace to enter that workspace.

Select pipeline in the left navigation bar to enter the pipeline page.

Select the target pipeline, click Run, and the Run Pipeline dialog box appears.

Enter the following parameters as required.

Other code source

Configuration Item	Descriptions
code source	Display the code source used by this pipeline. Further configuration of the pipeline code retrieval method is required. The pipeline supports retrieving code by branch, tag, or commit ID. Please select as needed. Branch: A branch consists of a series of commits. Pulling code by branch is the most common method. If you want to pull code from a specific branch, select or enter the branch name. Tag: A tag points to a specific commit and is commonly used to mark a particular version. For example, to pull the code for version V2.0, you can select or enter V2.0. Commit ID: A Commit ID is the ID of a specific commit. If you want to pull code based on a specific Commit ID, please enter the Commit ID.
Variable	If your pipeline has dynamic variables configured, you can set their runtime values here.
Operation description	Add remarks for this run; this field can be left blank.

Perforce code source

Configuration Item	Descriptions
code source	You can pull code from the Perforce code source using either Stream Codeline or ViewMapping; please select as needed. Stream CodeLine: Specifies a branch in a Stream type repository. After selecting, please specify the complete Perforce path. For example: //streamsDepot/mainline. ViewMapping: Supports specifying multiple paths across repositories. Enter each path on a separate line. For example: //streamsDepot/mainline/...//$P4CLIENT/.... You can further configure ChangelistID and ShelveID, whether you use Stream Codeline or ViewMapping. ChangelistID: Optional configuration. If ChangelistID is not specified, the latest code will be pulled by default. If ChangelistID is specified, the code corresponding to the current ChangelistID will be pulled. ShelveID: Optional configuration. After you fill in the form, the system will download the specified ShelveID content to the current directory.
Variable	If dynamic variables have been set in your pipeline, it is supported to configure the runtime values of these dynamic variables here.
Operation description	Add remarks for this run; this can be left blank.

Click confirm. The pipeline starts running, and the system navigates to the details page of the current pipeline.

The page updates the running status in real time.

When multiple tasks are running, the page displays the current progress in real time.

After a successful run, you can view outputs, run logs, and other related content. For more information, refer to view run details.

(Optional) Terminate pipeline execution

On the pipeline details page, click Terminate. A confirmation dialog appears.

After confirming the pipeline information, click Confirm to terminate the pipeline.

Optional retry on failure

On the pipeline details page, select the task card for a failed run, click Retry, and a confirmation dialog appears.

Click confirm, the pipeline starts executing from the current failed task.

Last updated: 2025.09.10 17:37:28