# Keep CI green and ship faster | Trunk > Markdown mirror of DialtoneApp's public top-site detail page for `trunk.io`. URL: https://dialtoneapp.com/top-sites/trunk.io/index.md Canonical HTML: https://dialtoneapp.com/top-sites/trunk.io ## Summary - Domain: `trunk.io` - Website: https://trunk.io - Description: ai readable | score 30 | purchase read only - Label: ai_readable - Payment surface: Not available - Purchase boundary: read_only - Control boundary: unknown - Rank: 185023 ## robots ~~~text # * User-agent: * Content-Signal: search=yes, ai-train=yes, ai-input=yes Allow: / # GPTBot User-agent: GPTBot Allow: / # ChatGPT-User User-agent: ChatGPT-User Allow: / # ClaudeBot User-agent: ClaudeBot Allow: / # PerplexityBot User-agent: PerplexityBot Allow: / # Google-Extended User-agent: Google-Extended Allow: / # Googlebot User-agent: Googlebot Allow: / # Bingbot User-agent: Bingbot Allow: / # Applebot-Extended User-agent: Applebot-Extended Allow: / # cohere-ai User-agent: cohere-ai Allow: / # Host Host: https://trunk.io/ # Sitemaps Sitemap: https://trunk.io/sitemap.xml Sitemap: https://trunk.io/feed.xml ~~~ ## llms ~~~text # Trunk > CI reliability platform that helps engineering teams detect flaky tests, accelerate merges, and keep CI green. Founded in 2021. SOC 2 Type II certified. - Last updated: 2026-03-12 - Full version: https://trunk.io/llms-full.txt Trunk eliminates two critical bottlenecks in software development: flaky tests that erode CI reliability, and merge conflicts that slow down code delivery. The platform serves DevEx, DevOps, and engineering teams at companies like Brex, Faire, Metabase, Zillow, and CockroachDB. ## Docs - [Full Documentation](https://docs.trunk.io/llms.txt): Complete platform documentation covering Merge Queue, Flaky Tests, setup, administration, and API references ## Core Products - [Flaky Tests](https://trunk.io/flaky-tests): Automatically detect, quarantine, and eliminate flaky tests across any language, test runner, and CI provider. Features AI-powered failure analysis, auto-quarantine during CI runs, ticketing integrations (Jira, Linear), PR comments, Slack alerts, and webhooks. - [Merge Queue](https://trunk.io/merge-queue): Enterprise merge queue with anti-flake protection, intelligent batching (up to 100 PRs), parallel queue lanes, auto-bisection on failure, predictive testing, priority merging, and stacked PR support. Tests every PR against latest main. ## Pricing - [Pricing](https://trunk.io/pricing): Free tier (up to 5 committers, 5M test spans/month), Team tier (unlimited committers, merge queue, multi-CI support), Enterprise tier (SAML, on-premise, volume discounts, custom integrations) ## Integrations ### Merge Queue Build Systems - [Merge Queue + Bazel](https://trunk.io/merge-queue/trunk-merge-and-bazel): Dynamic parallel queues powered by Bazel dependency graph - [Merge Queue + Nx](https://trunk.io/merge-queue/trunk-merge-and-nx): Dynamic parallel queues powered by Nx project graph ### Supported Test Frameworks - [Pytest](https://trunk.io/testing/pytest), [Playwright](https://trunk.io/testing/playwright), [Cypress](https://trunk.io/testing/cypress), [Vitest](https://trunk.io/testing/vitest), [Mocha](https://trunk.io/testing/mocha), [Jasmine](https://trunk.io/testing/jasmine), [Karma](https://trunk.io/testing/karma), [RSpec](https://trunk.io/testing/rspec), [Minitest](https://trunk.io/testing/minitest), [PHPUnit](https://trunk.io/testing/phpunit), [Maven](https://trunk.io/testing/maven), [Bazel](https://trunk.io/testing/bazel), [Cargo Nextest](https://trunk.io/testing/cargo-nextest), [Go (gotestsum)](https://trunk.io/testing/gotestsum), [Go (junit-report)](https://trunk.io/testing/go-junit-report), [XCTest](https://trunk.io/testing/xctest), [Swift Testing](https://trunk.io/testing/swift-testing), [Android](https://trunk.io/testing/android), [Unittest](https://trunk.io/testing/unittest), [Cucumber](https://trunk.io/testing/cucumber) ## Comparisons - [Trunk vs GitHub Merge Queue](https://trunk.io/trunk-vs-github-merge-queue): Trunk's parallel lanes architecture validates independent changes concurrently instead of GitHub's single FIFO queue, enabling faster merges at scale. - [Trunk vs Mergify](https://trunk.io/trunk-vs-mergify): Trunk offers dynamic parallel queues, optimistic merging, pending failure depth, and flaky test protection—all absent from Mergify. - [Trunk vs BrowserStack](https://trunk.io/compare/trunk-vs-browserstack): Trunk specializes in flaky test detection and management in CI/CD pipelines, while BrowserStack focuses on cross-browser and cross-device testing compatibility. - [Trunk vs CircleCI](https://trunk.io/compare/trunk-vs-circleci): Trunk provides CI-agnostic flaky test management with quarantining and ticketing, whereas CircleCI's test insights are limited to its own ecosystem. - [Trunk vs Launchable](https://trunk.io/compare/trunk-vs-launchable): Trunk's standout advantage is automatic test quarantining that isolates flaky tests from blocking CI, a capability Launchable lacks. - [Trunk vs LambdaTest](https://trunk.io/compare/trunk-vs-lambdatest): Trunk specializes in flaky test management with deep developer workflow integration (PR comments, Jira ticketing), while LambdaTest is a broader cross-browser testing platform. - [Trunk vs Gradle](https://trunk.io/compare/trunk-vs-gradle): Trunk offers platform-agnostic flaky test detection across multiple CI systems and frameworks, while Gradle Develocity focuses primarily on the Gradle ecosystem. - [Trunk vs Rainforest QA](https://trunk.io/compare/trunk-vs-rainforest-qa): Trunk automates flaky test detection within existing CI/CD pipelines, while Rainforest QA focuses on no-code test creation with a retry-based approach. - [Trunk vs Codecov](https://trunk.io/compare/trunk-vs-codecov): Trunk actively manages flaky tests through quarantining and ticketing, while Codecov focuses on code coverage analytics with only basic flaky test detection. - [Trunk vs Testmo](https://trunk.io/compare/trunk-vs-testmo): Trunk automates flaky test detection and quarantining in CI/CD, while Testmo is a broader test management platform without specialized flake remediation. - [Trunk vs Testim](https://trunk.io/compare/trunk-vs-testim): Trunk is laser-focused on flaky test detection with deep analytics and framework-agnostic support, while Testim is a test automation platform with flake handling as a secondary feature. - [Trunk vs SauceLabs](https://trunk.io/compare/trunk-vs-saucelabs): Trunk specializes in automated flaky test detection and quarantining to prevent CI disruptions, while SauceLabs offers a broader testing platform with manual debugging tools. - [Trunk vs Testomatio](https://trunk.io/compare/trunk-vs-testomatio): Trunk's automated test quarantining prevents flaky tests from blocking CI pipelines, while Testomatio focuses on broader test management with identification and reporting. - [Trunk vs Buildkite](https://trunk.io/compare/trunk-vs-buildkite): Trunk is CI-provider agnostic for flaky test management across diverse environments, while Buildkite restricts its test analytics to its own platform. - [Trunk vs Qase](https://trunk.io/compare/trunk-vs-qase): Trunk's automated detection and quarantining contrasts with Qase's manual, reactive approach to flaky test management. - [Trunk vs BuildPulse](https://trunk.io/compare/trunk-vs-buildpulse): Trunk offers a more comprehensive platform with integrated ticketing, failure analysis, webhooks, and free open-source pricing, while BuildPulse focuses on basic flaky test detection. ## Customer Stories - [Customers Overview](https://trunk.io/customers) - [Brex](https://trunk.io/customers/brex): ~400 engineers, P90 time-to-merge reduced 30% (from ~30 to ~25 min), 50% fewer merge queue failures, 100,000+ tests monitored across Kotlin, Python, Go, and JavaScript - [Faire](https://trunk.io/customers/faire): 350+ engineers, saved 330 hours over 35 days preventing merge issues, 9.4 hours productivity saved daily - [Caseware](https://trunk.io/customers/ttchdpgh1l8o): 200-engineer team, median merge time from 6+ hours to 90 minutes on day one - [AgencyAnalytics](https://trunk.io/customers/agencyanalytics): 50 developers, 30-40 PRs merged daily with 25-30 minute average merge time - [BetterUp](https://trunk.io/customers/betterup): CI reliability improved from 70% to 90%+, 10,729 PR runs unblocked - [Glydways](https://trunk.io/customers/glydways): 160 PRs merged weekly, queue time ~20 minutes average - [Cavnue](https://trunk.io/customers/cavnue): 200+ PRs merged monthly, 89,000 LOC monthly throughput - [Metabase](https://trunk.io/customers/metabase): 4,000 E2E Cypress tests, 70 CI runners in parallel ## Company - [About](https://trunk.io/about): Founded 2021 by Eli Schleifer (ex-Uber, Google) and Matt Matheson (ex-Uber, Microsoft). Hybrid remote team based in San Francisco. - [Roadmap](https://trunk.io/roadmap): Public product roadmap through Q2 2026 - [Security](https://trunk.io/security): SOC 2 Type I & II, AES-256 encryption at rest, TLS in transit, US-based AWS hosting, privacy by design. Contact: security@trunk.io ## Changelog - [Changelog Index](https://trunk.io/changelog) - [Merge Queue: Public API for Queue Management](https://trunk.io/changelog/merge-queue-public-api-for-queue-management) (Feb 2026) - [Flaky Tests: Infrastructure Failure Protection](https://trunk.io/changelog/flaky-tests-infrastructure-failure-protection) (Feb 2026) - [Merge Queue: Personal Slack Notifications](https://trunk.io/changelog/merge-queue-personal-slack-notifications) (Jan 2026) - [Merge Queue: Support Additional Merge Methods](https://trunk.io/changelog/merge-queue-support-additional-merge-methods) (Jan 2026) - [Merge Queue: Filter Metrics by Impacted Targets](https://trunk.io/changelog/merge-queue-filter-metrics-by-impacted-targets) (Jan 2026) - [Merge Queue: Direct Merge to Main](https://trunk.io/changelog/merge-queue-direct-merge-to-main) (Jan 2026) - [Merge Queue: Independent Concurrency for Batch Bisection](https://trunk.io/changelog/merge-queue-independent-concurrency-for-batch-bisection) (Jan 2026) - [Merge Queue: Test Caching for Batch Failure Isolation](https://trunk.io/changelog/merge-queue-test-caching-for-batch-failure-isolation) (Jan 2026) - [Flaky Tests: New API Endpoints](https://trunk.io/changelog/flaky-tests-new-api-endpoints) (Nov 2025) - [Plugins 1.7.4](https://trunk.io/changelog/plugins-1-7-4) (Nov 2025) - [Plugins 1.7.3](https://trunk.io/changelog/plugins-1-7-3) (Oct 2025) - [Flaky Tests: Auto Quarantine No Longer Applied to Broken Tests](https://trunk.io/changelog/flaky-tests-auto-quarantine-no-longer-applied-to-broken-tests) (Sep 2025) - [Flaky Test: Corrected CLI Test Failure Reporting Flag](https://trunk.io/changelog/flaky-test-corrected-cli-test-failure-reporting-flag) (Sep 2025) - [UI Refresh: Enhanced Dashboard Experience](https://trunk.io/changelog/ui-refresh-enhanced-dashboard-experience) (Sep 2025) - [Flaky Tests: New Endpoint and Xcode 26 Support](https://trunk.io/changelog/flaky-tests-new-endpoint-and-xcode-26-support) (Aug 2025) - [CI Autopilot: Stacked PRs, CI Triggers and MCP Support](https://trunk.io/changelog/ci-autopilot-stacked-prs-ci-triggers-and-mcp-support) (Aug 2025) - [CI Autopilot: Private Beta Initial Release](https://trunk.io/changelog/ci-autopilot-private-beta-initial-release) (Aug 2025) - [Code Quality: Plugins 1.7.2 and CLI 1.25.0](https://trunk.io/changelog/code-quality-plugins-1-7-2-and-cli-1-25-0) (Aug 2025) - [Flaky Tests: Commit Details in Timeline](https://trunk.io/changelog/flaky-tests-commit-details-in-timeline) (Jul 2025) - [Flaky Tests: Manual Test Status Overrides](https://trunk.io/changelog/flaky-tests-manual-test-status-overrides) (Jun 2025) ## Blog - [Blog Index](https://trunk.io/blog) - [Don't Build Agents, Build Context Enrichment](https://trunk.io/blog/don-t-build-agents-build-context-enrichment) - [Trunk Flaky Tests Is Out of Beta](https://trunk.io/blog/trunk-flaky-tests-is-out-of-beta) - [When Your Development Team Actually Needs a Merge Queue](https://trunk.io/blog/when-your-development-team-actually-needs-a-merge-queue) - [Outgrowing GitHub Merge Queue](https://trunk.io/blog/outgrowing-github-merge-queue) - [In Defense of VSCode: Why Are We Paying for Cursor?](https://trunk.io/blog/in-defense-of-vscode-why-are-we-paying-for-cursor) - [Cursor's Bugbot Code Reviewer and Web App Are a DX Nightmare](https://trunk.io/blog/cursor-s-bugbot-code-reviewer-and-web-app-are-a-dx-nightmare) - [Don't Let AI Debug Your Code Alone, Yet](https://trunk.io/blog/don-t-let-ai-debug-your-code-alone-yet) - [Early Thoughts on Kiro, Amazon's New Agentic IDE/VSCode Fork](https://trunk.io/blog/early-thoughts-on-kiro-amazon-s-new-agentic-ide-vscode-fork) - [Engineers Shouldn't Babysit Pipelines. AI Agents Should.](https://trunk.io/blog/engineers-shouldn-t-babysit-pipelines-ai-agents-should) - [The Joy of a Boring Codebase](https://trunk.io/blog/the-joy-of-a-boring-codebase) - [AI Tools Are Not Time Machines](https://trunk.io/blog/ai-tools-are-not-time-machines) - [Attempting to Engineer the Chaos Out of AI Agents](https://trunk.io/blog/attempting-to-engineer-the-chaos-out-of-ai-agents) - [DevOps Without the Drain: How AI Frees Developers from Repetitive Ops Work](https://trunk.io/blog/devops-without-the-drain-how-ai-frees-developers-from-repetitive-ops-work) - [You Don't Need a Developer Experience Team to Have a Good Internal DevEx](https://trunk.io/blog/you-don-t-need-a-developer-experience-team-to-have-a-good-internal-devex) - [Beyond the Editor: Bringing AI to the Rest of Your Dev Workflow](https://trunk.io/blog/beyond-the-editor-bringing-ai-to-the-rest-of-your-dev-workflow) - [Merge Fast or Merge Cheap: Fine-Tuning Merge Queues to Handle an Increase in PRs from AI Agents](https://trunk.io/blog/merge-fast-or-merge-cheap-fine-tuning-merge-queues-to-handle-an-increase-in-prs-f) - [Beyond XCTSkip: Stop Flaky iOS Tests from Blocking Your Team](https://trunk.io/blog/beyond-xctskip-stop-flaky-ios-tests-from-blocking-your-team) - [Eradicating Flaky Tests](https://trunk.io/blog/eradicating-flaky-tests) - [How to Avoid and Detect Flaky Tests in Vitest](https://trunk.io/blog/how-to-avoid-and-detect-flaky-tests-in-vitest) - [Stop Flaky Tests from Sabotaging Your Merge Queue](https://trunk.io/blog/stop-flaky-tests-from-sabotaging-your-merge-queue) - [The Ultimate Guide to Flaky Tests](https://trunk.io/blog/the-ultimate-guide-to-flaky-tests) - [What We Learned from Analyzing 20.2 Million CI Jobs - Part 1](https://trunk.io/blog/what-we-learned-from-analyzing-20-2-million-ci-jobs-in-trunk-flaky-tests-part-1) - [What We Learned from Analyzing 20.2 Million CI Jobs - Part 2](https://trunk.io/blog/what-we-learned-from-analyzing-20-2-million-ci-jobs-in-trunk-flaky-tests-part-2) - [How to Avoid and Detect Flaky Tests in Pytest](https://trunk.io/blog/how-to-avoid-and-detect-flaky-tests-in-pytest) - [Flaky Tests Now in Public Beta](https://trunk.io/blog/announcing-trunk-flaky-tests) - [How ESLint Lints Their Code with Trunk Code Quality](https://trunk.io/blog/improving-linting-experience-in-eslint-s-open-source-repo-with-trunk-code-quality) ## Learn - [Learn Index](https://trunk.io/learn) - [How to Avoid and Detect Flaky Tests in Playwright](https://trunk.io/learn/how-to-avoid-and-detect-flaky-tests-in-playwright) - [Pytest vs Unittest: A Comparison](https://trunk.io/learn/pytest-vs-unittest-a-comparison) - [What Is a Merge Queue and Do You Need One?](https://trunk.io/learn/what-is-a-merge-queue-and-do-you-need-one) - [How DevOps Testing Tools Solve Real Development Challenges](https://trunk.io/learn/how-devops-testing-tools-solve-real-development-challenges) - [10 Software Testing Tools That Actually Solve Real Problems in 2025](https://trunk.io/learn/10-software-testing-tools-that-actually-solve-real-problems-in-2025) - [Practical Guide to AI-Powered Automated Testing Strategies](https://trunk.io/learn/practical-guide-to-ai-powered-automated-testing-strategies) - [Generative AI for Efficient and Accurate Software Testing](https://trunk.io/learn/generative-ai-for-efficient-and-accurate-software-testing) - [Comparative Analysis of Testing Solutions](https://trunk.io/learn/comparative-analysis-of-testing-solutions) - [The Role of Artificial Intelligence in Modern Quality Assurance](https://trunk.io/learn/the-role-of-artificial-intelligence-in-modern-quality-assurance) - [Navigating the Challenges of Testing AI-Based Software](https://trunk.io/learn/navigating-the-challenges-of-testing-ai-based-software) - [10 Essential DevOps Tools for Software Development](https://trunk.io/learn/10-essential-devops-tools-for-software-development) - [10 DevOps Automation Tools That Actually Improve Software Development Workflows](https://trunk.io/learn/10-devops-automation-tools-that-actually-improve-software-development-workflows) - [How Top Engineering Teams Are Optimizing Developer Productivity](https://trunk.io/learn/how-top-engineering-teams-are-optimizing-developer-productivity) - [10 Free AI Testing Tools for Efficient Software Quality Assurance](https://trunk.io/learn/10-free-ai-testing-tools-for-efficient-software-quality-assurance) - [The Comprehensive Guide to Test-Driven Development (TDD)](https://trunk.io/learn/the-comprehensive-guide-to-test-driven-development-tdd) - [Context Switching in Software Engineering: How Developers Lose Productivity](https://trunk.io/learn/context-switching-in-software-engineering-how-developers-lose-productivity) - [The Complete Roadmap to Automated GUI Testing Techniques](https://trunk.io/learn/the-complete-roadmap-to-automated-gui-testing-techniques) - [Advanced Test Automation Strategies Using Artificial Intelligence](https://trunk.io/learn/advanced-test-automation-strategies-using-artificial-intelligence) - [Advantages of Automation Testing](https://trunk.io/learn/advantages-of-automation-testing) - [Advantages of Continuous Integration](https://trunk.io/learn/advantages-of-continuous-integration) - [AI Code Analyzer (Free)](https://trunk.io/learn/ai-code-analyzer-free) - [AI Code Review Tools](https://trunk.io/learn/ai-code-review-tools) - [AI-Driven Testing](https://trunk.io/learn/ai-driven-testing) ## Legal - [Terms of Service](https://trunk.io/terms) - [Privacy Policy](https://trunk.io/privacy) - [Master Services Agreement](https://trunk.io/msa) - [Subprocessors](https://trunk.io/subprocessors) ~~~ ## llms-full ~~~text # Trunk — Full Reference > CI reliability platform that helps engineering teams detect flaky tests, accelerate merges, and keep CI green. Founded in 2021. SOC 2 Type II certified. - Last updated: 2026-03-12 - Summary version: https://trunk.io/llms.txt --- ## Company Overview Trunk eliminates two critical bottlenecks in software development: flaky tests that erode CI reliability, and merge conflicts that slow down code delivery. The platform serves DevEx, DevOps, and engineering teams at companies like Brex, Faire, Metabase, Zillow, and CockroachDB. Founded in 2021 by Eli Schleifer (ex-Uber, Google) and Matt Matheson (ex-Uber, Microsoft), Trunk is a hybrid remote team based in San Francisco. The company is SOC 2 Type I and Type II certified, uses AES-256 encryption at rest, TLS in transit, and hosts on US-based AWS infrastructure with privacy-by-design principles. - Website: https://trunk.io - Documentation: https://docs.trunk.io - Public Roadmap: https://trunk.io/roadmap - Security: https://trunk.io/security (contact: security@trunk.io) --- ## Product: Trunk Flaky Tests **URL:** https://trunk.io/flaky-tests Trunk Flaky Tests automatically detects, quarantines, and eliminates flaky tests across any language, test runner, and CI provider. It is designed for engineering teams who need reliable CI pipelines without the overhead of manually tracking and debugging intermittent test failures. ### How It Works 1. **Detection:** Trunk analyzes test results uploaded from your CI runs. Tests that produce inconsistent results (pass/fail for the same code) are flagged as flaky. 2. **Quarantine:** Flaky tests are automatically quarantined during CI runs. They still execute and their results are tracked, but they no longer block the pipeline. 3. **Analysis:** AI-powered failure fingerprinting groups different failure modes of the same test, helping developers understand root causes with full context. 4. **Resolution:** Integrations with Jira, Linear, and other ticketing systems create tickets for flaky tests. Slack alerts and PR comments keep teams informed. Webhooks enable custom workflows. An MCP server enables AI-powered root cause analysis directly in your development environment. ### Key Features - Auto-quarantine during CI runs — flaky tests don't break your pipeline - AI-powered failure fingerprinting — groups failure patterns for root cause analysis - PR comments — developers see flaky test impact on their pull requests - Jira and Linear integration — automatic ticket creation for flaky tests - Webhooks — build custom automation workflows - API - integrate with your existing infrastructure - MCP server — enables AI-powered root cause analysis of flaky tests in your IDE or agent workflow - Multi-CI support — works with GitHub Actions, Jenkins, CircleCI, Buildkite, GitLab CI, Semaphore, Harness, and more - Framework agnostic — supports Pytest, Playwright, Cypress, Vitest, Jest, Mocha, Jasmine, Karma, RSpec, Minitest, PHPUnit, Maven, Bazel, Cargo Nextest, Go (gotestsum), Go (junit-report), XCTest, Swift Testing, Android, Unittest, Cucumber, and more - Metrics tracking — number of flaky and broken tests, pass rates, PRs impacted ### FAQ **What are flaky tests?** Flaky tests are tests that fail and pass inconsistently, even when the code hasn't changed. They mess with the reliability of your test suite and can waste valuable development time. **Why do flaky tests happen?** Flaky tests usually come from things like race conditions, unstable dependencies, or shared test data. They're caused by issues that are hard to reproduce and fix, like improper test setups or asynchronous operations. **How does Trunk help with flaky tests?** Trunk Flaky Tests finds, quarantines, and helps remove flaky tests from your code. It helps you identify patterns, figure out why your tests are flaky, and fix them before they slow down your team. **How do flaky tests affect productivity?** Flaky tests make developers waste time rerunning tests, digging through logs, and chasing problems that might not exist. Over time, they slow down your CI pipeline and make it harder to release code. **What kinds of tests can be flaky?** Any test can be flaky, including unit tests, integration tests, end-to-end tests, or UI tests. They are especially common in systems that involve significant concurrency or external dependencies. **What is failure fingerprinting?** Trunk uses AI to recognize the different ways a single test fails. It groups these failures so you can see patterns and fix the root cause, with full context of what's happening. **How do I prevent flaky tests?** To avoid flaky tests, you need stable test data, proper handling of asynchronous events, and isolated test environments. Trunk helps by automatically catching flaky tests and letting you quarantine them without blocking progress. **Which CI providers does Trunk work with?** Trunk works with all major CI providers, including GitHub Actions, Jenkins, CircleCI, and Bitbucket Pipelines. It integrates easily with your existing tools and workflows. **How do I track and fix flaky tests in Trunk?** You'll get alerts when a test becomes flaky. You can also track the history of flaky tests and get detailed insights into their causes, then use tools like Jira to make sure they're fixed. **How does auto-quarantining work?** Trunk automatically quarantines flaky tests during your CI runs. This means the flaky tests won't break your pipeline, but they're still tracked and monitored. **How long does it take to set up Trunk Flaky Tests?** Setting up Trunk Flaky Tests takes just a few minutes. Follow the setup guide at https://docs.trunk.io/flaky-tests and you'll be up and running quickly. **What metrics does Trunk track?** Trunk tracks metrics like flaky test rates, CI time per pull request, and time wasted due to flakiness. These numbers help you measure the real impact of flaky tests on your team's productivity. **Who uses Trunk?** Trunk is trusted by companies like Zillow, Metabase, Vidyard, and Waabi to keep their tests stable and their CI pipelines running smoothly. --- ## Product: Trunk Merge Queue **URL:** https://trunk.io/merge-queue Trunk Merge Queue is an enterprise-grade merge queue that prevents broken main branches by testing every PR against the speculative future state of main. Unlike GitHub's built-in single FIFO queue, Trunk supports parallel lanes, intelligent batching, and built-in flaky test protection. ### How It Works 1. **Enqueue:** Developers submit their PR to the merge queue via GitHub comment, Slack command, or API call. 2. **Predictive Testing:** The queue creates a speculative merge of the PR against main plus all PRs ahead in line, then runs CI against this state. 3. **Parallel Lanes:** Independent changes (identified via impacted target analysis, Bazel dependency graph, or Nx project graph) are tested in parallel lanes, eliminating unnecessary serialization. 4. **Batching:** Compatible PRs are batched together (up to 100 PRs) to reduce CI costs and merge latency. 5. **Failure Handling:** On failure, auto-bisection identifies the offending PR. Flaky test detection prevents spurious ejections. 6. **Merge:** Once CI passes, PRs are automatically merged to main. ### Key Features - Dynamic parallel queue lanes — independent changes test concurrently - Intelligent batching — up to 100 PRs per batch - Auto-bisection on failure — automatically identifies the breaking PR - Predictive testing — reduces redundant CI runs - Priority merging — granular priority levels and direct merge option - Stacked PR support — merge chains of dependent PRs - Anti-flake protection — integrates with Trunk Flaky Tests - Pending failure depth — holds failed PRs while next PRs continue testing - Slack integration — built-in DM and channel notifications - Full REST API — PR operations and queue management/configuration - Webhooks — PR lifecycle events and batch events with detailed payloads - Prometheus metrics endpoint — observability and dashboards - Per-branch queues — separate queues for different branches - Multiple merge methods — squash, merge, rebase - On-premise deployment available ### Integrations - Bazel — dynamic parallel queues powered by Bazel dependency graph - Nx — dynamic parallel queues powered by Nx project graph --- ## Pricing **URL:** https://trunk.io/pricing ### Free Tier - Up to 5 committers - 5M test spans per month - Community support ### Team Tier - Seat based committers, 1M test spans per commiter - Multi-CI support - Priority support - Advanced analytics ### Enterprise Tier - SAML/SSO authentication - On-premise deployment option - Volume discounts - Custom integrations - Dedicated support - Custom SLAs --- ## Supported Test Frameworks - **Python:** Pytest, Unittest - **JavaScript/TypeScript:** Playwright, Cypress, Vitest, Jest, Mocha, Jasmine, Karma - **Ruby:** RSpec, Minitest, Cucumber - **PHP:** PHPUnit - **Java:** Maven - **Rust:** Cargo Nextest - **Go:** gotestsum, go-junit-report - **Swift/iOS:** XCTest, Swift Testing - **Android:** Android Test - **Multi-language:** Bazel --- ## CI Provider Support - GitHub Actions - Jenkins - CircleCI - Buildkite - GitLab CI - Semaphore - Harness - Bitbucket Pipelines - Any CI that can upload JUnit XML --- ## Customer Stories ### Brex ~400 engineers on a monorepo with 100,000+ tests across Kotlin, Python, Go, and JavaScript. Auto-quarantining flaky tests with Trunk drove a 30% P90 time-to-merge reduction (from ~30 to ~25 minutes), eliminated 50% of merge queue failures, and shifted the Release Infrastructure on-call from firefighting to proactive work. https://trunk.io/customers/brex ### Faire 350+ engineers. Saved 330 hours over 35 days preventing merge issues. 9.4 hours of productivity saved daily across the engineering team. https://trunk.io/customers/faire ### Caseware 200-engineer team. Reduced median merge time from 6+ hours to 90 minutes on day one of deploying Trunk Merge Queue. https://trunk.io/customers/caseware ### AgencyAnalytics 50 developers. Merges 30-40 PRs daily with 25-30 minute average merge time using Trunk Merge Queue. https://trunk.io/customers/agencyanalytics ### BetterUp CI reliability improved from 70% to 90%+ using Trunk Flaky Tests. 10,729 PR runs unblocked by automatic flaky test quarantining. https://trunk.io/customers/betterup ### Glydways 160 PRs merged weekly with queue time averaging ~20 minutes using Trunk Merge Queue. https://trunk.io/customers/glydways ### Cavnue 200+ PRs merged monthly. 89,000 lines of code monthly throughput with Trunk Merge Queue. https://trunk.io/customers/cavnue ### Metabase 4,000 E2E Cypress tests managed with Trunk Flaky Tests. 70 CI runners operating in parallel. https://trunk.io/customers/metabase --- ## Comparisons ### Trunk vs GitHub Merge Queue Trunk's parallel lanes architecture validates independent changes concurrently instead of GitHub's single FIFO queue, enabling faster merges at scale. Key advantages: parallel lanes, intelligent batching, flaky test protection, Slack integration, full REST API, detailed analytics, and configuration-as-code. https://trunk.io/trunk-vs-github-merge-queue ### Trunk vs Mergify Trunk offers dynamic parallel queues, optimistic merging, pending failure depth, and flaky test protection — all absent from Mergify. Trunk also provides more granular priority levels and comprehensive CI cost management. https://trunk.io/trunk-vs-mergify ### Trunk vs BrowserStack Trunk specializes in flaky test detection and management in CI/CD pipelines, while BrowserStack focuses on cross-browser and cross-device testing compatibility. Trunk provides automatic quarantining and CI-pipeline integration that BrowserStack lacks. https://trunk.io/compare/trunk-vs-browserstack ### Trunk vs CircleCI Trunk provides CI-agnostic flaky test management with quarantining and ticketing, whereas CircleCI's test insights are limited to its own ecosystem. Trunk works across any CI provider. https://trunk.io/compare/trunk-vs-circleci ### Trunk vs Launchable Trunk's standout advantage is automatic test quarantining that isolates flaky tests from blocking CI, a capability Launchable lacks. https://trunk.io/compare/trunk-vs-launchable ### Trunk vs BuildPulse Trunk offers a more comprehensive platform with integrated ticketing, failure analysis, webhooks, and free open-source pricing, while BuildPulse focuses on basic flaky test detection. https://trunk.io/compare/trunk-vs-buildpulse --- ## Technical Architecture Trunk is a cloud-hosted platform (with on-premise option) that integrates with your existing CI/CD pipeline: 1. **Data Collection:** A lightweight CLI uploads test results (JUnit XML format) from your CI runs to Trunk's platform. 2. **Analysis Engine:** Trunk's backend analyzes test results across runs, identifying statistical patterns of flakiness and correlating failures with code changes. 3. **Merge Queue Engine:** For merge queue, Trunk orchestrates speculative merges on your GitHub repository, creating temporary branches and triggering your existing CI workflows. 4. **API Layer:** Full REST API for programmatic access to all features — queue management, PR operations, test data, and configuration. 5. **Integrations:** Webhooks, Slack, Jira, Linear, and GitHub integrations enable seamless workflow automation. --- ## Legal - Terms of Service: https://trunk.io/terms - Privacy Policy: https://trunk.io/privacy - Master Services Agreement: https://trunk.io/msa - Subprocessors: https://trunk.io/subprocessors ~~~