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
        • Jira best practices
        • 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
    • Creating & managing teams
      • Teams API
    • Managing users and roles
    • Organization settings
      • Jira setup
      • Data quality
        • Pull request data quality
        • Linking pull requests to issues
      • Investment balance
      • 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
    • Team settings
      • Mapping work to your team
      • Sprints
      • Team notifications
    • Notifications
      • Personal notifications
  • 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
    • Retrospective guide
  • 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
  • Working agreements
    • Set up working agreements
  • 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
  • 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
  • Summary
  • Example
  • Why it matters
  • How to use it
  • Where to find it
  • Frequently asked questions
  • Why is my time to deploy 0?

Was this helpful?

Time to deploy

Time to deploy is the average time between a pull request merge and deployment.

PreviousThroughputNextBatch size

Last updated 8 days ago

Was this helpful?

Summary

Time to deploy is one of the , key to understanding the health of a team’s deployment infrastructure. Measures the time it takes from pull request merge to deployment. Part of .

Example

If you merge a pull request at 2:10pm and it's deployed by 2:34pm, the time to deploy is 24 minutes.

Why it matters

Time to deploy helps measure how long it takes to deploy a release into a development, testing, or production environment. Measuring this metric can help improve deployment and delivery methods, processes, and tools.

Useful for understanding how much delay your current deployment process is causing in your deployment process.

How to use it

If you have a high time to deploy or have seen a recent increase, having a discussion with your team to understand the root cause behind this can help unlock key areas for improvement in your delivery.

Time to deploy is not available when using as the deployment source. For more information, see .

Where to find it

You can find time to deploy (as well as the other DORA metrics) under Metrics → DORA

Frequently asked questions

Why is my time to deploy 0?

The most common reasons are:

You're using as the deployment source. This is because we only know when the PR was merged but don't get any signal when it is in production. If you want to track time to deploy, you need to use another .

The deployment(s) don't have .

DORA metrics
change lead time
merged pull requests
Deployment settings
merged pull requests
deployment source
associated pull requests