View Pipeline Run Results

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

After a 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 run results can be viewed in multiple locations within the project:

Entry Point 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: Displays Manually Triggered for manual trigger scenarios, not displayed for code event triggers.
   • Trigger Branch/Tag: Displays the source of the trigger.
   • Status: Success/Failure/Canceled/Skipped/Ignored/Pending/Running/Failed
   • Run Number: A unique identifier, such as #42
   • Triggerer and Duration

Entry Point 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 Point Three: Pull Request Page

The Checks tab on the PR page aggregates all pipeline run 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-latest, x64, small]
        steps:
          - name: Run build
            run: make build
  test:
    name: test
    fail_fast: true         
    jobs:
      Test:
        name: unit-test
        runs-on: [ubuntu-latest, x64, medium]
        steps:
          - name: Run test
            run: make test
  deploy:
    name: deploy
    jobs:
      Deploy:
        name: push-image
        runs-on: [ubuntu-latest, 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	Each job shows the name, Runner tag, duration, and status
Step Timeline	Expands the job to display the execution duration and results step by step
Post-Processing	If the workflow defines a post stage, it is displayed separately after the main process

Note: AtomGit Action's stages mechanism 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, 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 job in the preceding stage failed, and subsequent stages were skipped by the serial mechanism; or the preceding stage configured fail_fast: true, and any job failure would terminate the entire workflow immediately.

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

A: AtomGit Action supports a post post-processing stage, which will be 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 panel of the Actions tab, select the status filter as "Failed".