LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Why it matters
  • Where to find it
  • How to use it
  • Repositories
  • Workflows
  • Jobs
  • Workflow runs
  • Video walkthrough
  • Metric definitions
  • Total run time
  • Run time percentiles
  • Run time distribution
  • Failure rate

Was this helpful?

Get visibility into your CI pipeline

Swarmia provides you with the most important CI metrics for tracking your CI health

PreviousCoach software developersNextWorking agreements

Last updated 15 days ago

Was this helpful?

Why it matters

Keeping the CI fast and robust is essential for good developer experience and fast cycle times. As such, it is important to have good visibility into your CI pipeline, which is what Swarmia's CI insights aim to provide you with.

Where to find it

You can find CI metrics under .

How to use it

You can start from the top-level view by identifying which of your repositories have the busiest / slowest CI pipelines. Then, you can drill down deeper into the repository and into the individual workflows to analyze the run time trends and which part of the workflow is slow.

When you know what is slowing you down, you can then work to improve the situation.

Repositories

The top-level view offers an overview of your repositories’ CI activities:

  • Total CI run time: Total time spent on CI runs per repository. Note: A high total runtime may indicate many CI runs (e.g., due to frequent pull requests), not necessarily slow CI processes.

  • Workflow run time distribution: Visual representation of workflow runtimes. Use this to spot repositories with longer-running workflows.

Workflows

Click on a repository to view detailed workflow insights.

  • Run time distribution: Shows how long workflows take to run.

  • Typical run (p90): Monitor these trends to detect workflows that are slowing down over time.

  • Failure Rate: High failure rates in testing or linting workflows are normal—they catch issues. High failure rates in deployment workflows may indicate flaky pipelines needing attention.

Jobs

Within a workflow, click to view its constituent jobs.

  • Jobs: Details each job within the workflow (e.g., testing, linting).

  • Job run time trends (p90, p75, p50): Observe how job runtimes change over time. An upward trend suggests optimization may be needed to prevent slowdowns.

Workflow runs

  • Status: Filter runs by success or failure.

  • Branches: Filter runs by branch name. Helpful when the same workflow behaves differently on different branches (e.g., additional deployment steps on the main branch).

Click on a specific workflow run to open it in GitHub Actions. Examine logs and steps to diagnose and troubleshoot issues.

Video walkthrough

See the video below for an in-depth walkthrough of the feature:

Metric definitions

The metrics provided by the CI visibility view are defined as follows:

Total run time

This metric tells the total amount of time that the CI has spent running across the grouping of the view (repository, workflow, or job). Run time is calculated from the start of the workflow/job run to its end. Both failures and successes are included.

Run time percentiles

On the workflow and job level, we show the p50, p70, and p90 trends of the run time. (p90 = 90% of workflow runs complete below this time.)

Run time distribution

We show the distribution of the run times of the runs in the timeframe. For example, how many workflow runs had a run time between 5 to 10 minutes.

Failure rate

The percentage of runs that failed. Neutral conclusions (such as skipped or canceled) are not considered failures.

Infrastructure → CI visibility