Viewing a Pipeline
On the pipeline details page, you can view basic pipeline information and perform operations on pipelines as needed.
Procedure
- Log in to CodeArts Pipeline.
- On the Pipelines tab page, search for the target pipeline and click the task name. The pipeline Execution History page is displayed.
You can click the time filter in the upper right corner to view execution records by time. By default, executions in the past 7 days are displayed. You can switch to 14 days and 31 days.
During the first execution, the execution histories page is empty. Records are generated only after the first execution.
- Click the execution ID to access the Pipeline Details page.
Click in the upper right corner to edit, copy, and delete pipelines, and view pipeline operation history (creation and editing operations) as required.
Perform the following operations on the Pipeline Details page:
Operation
Description
Retry
If the task fails, you can click Retry in the upper right corner to continue the task.
Run
Click Run in the upper right corner to execute the pipeline again with the latest configuration and generate an execution record.
Download
Click Download next to Output to download the build package automatically built using the pipeline.
NOTE:- A build package is available only for build tasks.
- If there are multiple build packages, click Download All.
- Only the latest 10 build packages are displayed. To download other build packages, switch to the Release Repos page.
View logs
Click a task card to view the task log.
NOTE:No log will be generated for tasks of DelayedExecution and PipelineSuspension.
More operations
Click in the upper right corner of the page to edit, copy, and delete pipelines, and view pipeline operation history (creation and editing operations) as required.
NOTE:By default, only project managers and creators (project creators or pipeline creators) can delete pipelines. You can configure permissions for different roles.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.