View Pipeline Execution Results

This document introduces how to view the pipeline execution status through multiple entry points, including the Actions tab, commit history page, and PR page details.

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.

Configuration Instructions

Pipeline execution results can be viewed in multiple entries within the project:

Entry One: Project Homepage → Actions Tab

1. Enter the target project page, click on the Actions tab in the top navigation bar.
2. The left sidebar lists all workflow names; click on the target workflow.
3. The right side displays the list of runs for this workflow, with each record containing:
   • Trigger Event: such as push, pull_request, workflow_dispatch, etc.
   • Trigger Branch/Tag: shows the source of the trigger
   • Status Badge: ✅ Success / ❌ Failure / 🟡 Running / ⏸ Cancelled / 🔶 Skipped
   • Run Number: a unique identifier, such as #42
   • Trigger Person and Duration

Entry Two: Commit History Page

On the Commits page of the code repository, a simplified status badge appears next to each commit record. Clicking it will jump to the corresponding run details.

Entry Three: Pull Request Page

The Checks tab on the PR page aggregates all pipeline execution results triggered by this PR, helping reviewers quickly assess code quality.

Run Details Page

After clicking a run, you enter the details page, and the content displayed depends on the stages structure defined in the workflow:

# .gitcode/workflows/build.yml
stages:
  compile:
    name: Build
    jobs:
      Build:
        name: compile
        runs-on: [ubuntu-24, x64, small]
        steps:
          - name: Run build
            run: make build
  test:
    name: test
    fail_fast: true         
    jobs:
      Test:
        name: unit-test
        runs-on: [ubuntu-24, x64, medium]
        steps:
          - name: Run test
            run: make test
  deploy:
    name: deploy
    jobs:
      Deploy:
        name: push-image
        runs-on: [ubuntu-24, x64, large]
        steps:
          - name: Run deploy
            run: make deploy

The details page is arranged vertically according to the stages order:

Display Area	Description
Stage Sidebar	Lists each stage in the order defined by stages, indicating the status
Job Card	Displays the job name, Runner tag, duration, and status
Step Timeline	Shows the execution duration and results step by step after expanding the job
Post Processing	If the workflow defines a post stage, it is displayed separately after the main process

Note: The stages mechanism of AtomGit Action defaults to serial execution — the next stage starts only after all jobs in the previous stage are successful. If a stage sets fail_fast: true, then any job failure in that stage will immediately terminate the current stage and skip all subsequent stages.

Status Badge Embedding

You can embed the run status badge into README:

![Build Status](https://atomgit.com/{owner}/{repo}/badges/{workflow_name}/pipeline.svg)

Common Issues

Q: Why does a certain stage show as "Skipped" in the details page?

A: A previous stage had a failed job, and the subsequent stages were skipped due to the serial execution mechanism; or the previous stage was configured with fail_fast: true, causing the entire workflow to terminate upon any job failure.

Q: What does the "post" stage appearing in the run details page mean?

A: AtomGit Action supports a post post-processing stage, which is executed even if the main process fails, commonly used for resource cleanup, notification pushing, etc.

Q: How to view only failed runs?

A: In the left filter column of the Actions tab, select the status filter as "Failed".