Trunk

CI gets more painful as teams grow. @brettdg talks with @trunkio founder and CEO @EliSchleifer about CI pain, flaky tests, merge queues, and what starts to break as engineering teams scale. Watch on YouTube below, or listen wherever you get your podcasts.

excited to share a special surprise! check out our "roadmap CLI" and get inspiration for your valentine's cards ❤️ trunk.io/roadmap?campai… ... there might be a secret command 🤫

AI is making code generation 10x faster, but the rest of the dev lifecycle still feels stuck in 2019. A thread on why our tooling is buckling under AI-paced output 🧵

Lessley Dennington and @Ambily8 from @GitHub showcased building AI-enhanced GitHub Actions workflows. Even the smartest workflows fail, and when they do, someone still has to dig through logs and context-switch from feature work. That's why we're focused on automating root cause analysis and surfacing actionable fixes right in the workflow. What's in your CI debugging toolkit? Still relying on grep and hope, or have you automated parts of the root cause analysis? #KeepCIGreen #GitHubUniverse #GitHubActions

Thanks for the great session by @mayankbhola from @lambdatesting presenting on AI-driven testing with KaneAI at @GitHubUniverse! AI-generated tests bring incredible coverage, but we're seeing a pattern: rapid test suite growth often means more flaky tests that block merge queues. As test suites scale with AI assistance, detecting and quarantining flaky tests early becomes critical to keeping velocity gains intact. #KeepCIGreen #GitHubUniverse #TestAutomation

We're proud sponsors of #BazelCon 2025! 🎉 Atlanta on Nov 10-11 - we can't wait to connect with the @Bazelbuild community that's pushing the boundaries of build systems at scale. At Trunk, we've built our CI Reliability Platform specifically for teams running Bazel in massive monorepos. Companies like @brexhq, @Waabi_ai, @AppliedInt, and @glydways trust us to keep their builds fast and reliable with target-parallel merge queues, BEP-native flaky test detection, and cache-aware intelligence. Stop by our booth for: 🥣 Limited edition "Flaky" cereal boxes (because the only flakes in your codebase should be in your breakfast) 🎮 Enter our raffle to win a ModRetro Chromatic, the ultimate Game Boy Color throwback console Whether you're a maintainer, contributor, or just love geeking out about build performance, we want to hear your war stories. See you in Atlanta! #BazelCon2025 #Bazel #DevTools #CI #Monorepo

The @trunkio team is heading to GitHub Universe next week! Looking forward to two days of developer conversations, learning about what's new in the ecosystem, and geeking out over all things dev tools and workflows. If you're heading to Fort Mason, let's meet up! Drop us a note or come say hi. Always excited to chat with folks building great software. #GitHubUniverse #DevTools #KeepCIGreen

@ProductHunt Ready to give it a try? 📺 Watch the demo: youtu.be/ORE30UUvOJk 🚀 Vote on Product Hunt: producthunt.com/products/trunk… 🌐 Learn more: trunk.io/flaky-tests 📖 Get started: docs.trunk.io/flaky-tests

✅ Works with any language and CI provider ✅ Quarantines flaky tests on CI ✅ Keeps your team shipping instead of debugging random failures We're live on @ProductHunt today - every upvote helps us reach more frustrated developers! 🔗 producthunt.com/products/trunk…

🎉 Trunk Flaky Tests is now out of beta after months of user testing and feedback! No more random CI failures blocking your PRs. No more "just rerun it and pray it works" moments. Watch how it works youtu.be/ORE30UUvOJk

🚀 Excited to announce the launch of Trunk Flaky Tests! You can now detect, quarantine, and eliminate flaky tests from your codebase. Works with any language, any test runner, and any CI provider. Keep your CI Green. Get started today at trunk.io/flaky-tests

The math is simple: - Spending $3K+ monthly on CI? - Have 20+ engineers? - 30+ PRs per day? Trunk pays for itself in CI savings alone. 📊 Read More: trunk.io/blog/outgrowin… 🚀 Learn more about Trunk Merge Queue: trunk.io/merge-queue 5/5

Real customer example: - Team of 50 engineers - Was spending: $15K/month on CI - After Trunk: $4K/month on CI - Savings: $11K/month vs $500 Trunk cost ROI: 22x in CI costs alone (not counting dev productivity gains) 4/5

💸 Your CI bill is growing faster than your team, and it's not sustainable. Here's why most merge queues are expensive... and how to fix it: 🧵👇

The result: ✅ Teams don't block each other ✅ Fast changes merge in minutes, not hours ✅ Complex changes get proper validation ✅ Monorepo becomes productivity multiplier again Stop fighting your architecture. Make it work for you. 📖 trunk.io/blog/outgrowin… 4/4

Trunk's solution: Parallel queues 📝 Docs queue: 2 min → merge ✅ 🔧 Backend queue: 45 min → merge ✅ 🎨 Frontend queue: 15 min → merge ✅ All run simultaneously. Teams work independently again. 3/4

Your monorepo is supposed to make development faster. Instead, it's become a coordination nightmare. Here's how to fix it: 🧵👇