Running the Pipeline

This section introduces how to view the results of pipeline runs, check task logs, manually trigger a pipeline, and rerun failed tasks.

📄️ View Pipeline Execution Results

Applicable Scenarios: After the pipeline is triggered, you need to confirm the execution status, duration, and final result of each stage (stage) and task, to determine whether the build/test/deployment has been successfully completed.

📄️ View Task Logs

Applicable Scenarios: When a pipeline task fails or behaves abnormally, you need to view the complete log output step by step to locate specific error lines, command return codes, or environment issues.

📄️ Manually Triggering a Pipeline

Use Case: When you need to actively execute the pipeline in non-automatic scenarios — for example, debugging a branch, verifying temporary parameters, or releasing a specific version — you can manually trigger it using the workflow_dispatch event.

📄️ Re-run Failed Jobs

Applicable Scenario: When a pipeline fails due to transient errors (network jitter, Runner temporarily unavailable, third-party service timeout), you need to re-run to confirm if it's a recoverable issue.