Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Platform Engineering Podcast

Platform Engineering Podcast artwork

Green CI and Merge Queue Mastery with Trunk’s Eli Schleifer

Apr 15, 202650 minAudio
  • Apple Podcasts

When a flaky test can stall a merge queue, “just rerun CI” stops scaling fast. Cory talks with Trunk co-founder and CEO Eli Schleifer about the outer loop problems that show up as teams ship more code - especially with AI-assisted development increasing PR volume. They break down what a merge queue is, why logical merge conflicts happen even when individual PRs are green, and how predictive testing helps protect main without forcing constant retesting. Eli also explains how Trunk approaches flaky tests: collecting JUnit results, using quarantines so known flakes don’t block delivery, and fingerprinting failures to tell the difference between “this always times out” and “this was just broken by a recent change.” The conversation closes on how review and quality practices may shift as code generation accelerates - and what still needs strong guardrails like tests, security checks, and reliable CI signals. Guest: Eli Schleifer, co-founder and CEO of Trunk Eli Schleifer leads Trunk’s technical vision and product strategy, focused on closing the gap between AI-speed code generation and human-speed delivery by removing the bottlenecks that slow modern engineering teams. Trunk’s platform eliminates flaky tests, resolves merge queue constraints, and redesigns CI systems to enable high-throughput, continuous delivery. Prior to founding Trunk, Eli was CTO at Directr, which was acquired by Google, and has served in engineering leadership roles at YouTube, Uber, and Microsoft. Eli Schleifer, X Trunk, website Trunk, Slack Trunk, Github Trunk, X Links to interesting things from this episode: Balsamiq “Code First Engineering” by Eli Schleifer

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Guests

  • Eli Schleifer Guest Inferred

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Taking a Summer Break: What Would You Like To Hear This Fall?

    Jul 15, 20263 minAudio

    We're hitting pause for the summer on new episodes of the Platform Engineering Podcast, but don’t worry, we’ve got some great episodes in the feed to keep you entertained in the meantime. If you’ve got suggestions for...

    • Apple Podcasts

    Credit the people on this episode

  2. What Do Service Meshes Actually Solve? (William Morgan, Buoyant/Linkerd)

    Jun 24, 202656 minAudio

    Network calls fail in ways function calls never do - and once a monolith becomes microservices, reliability problems show up fast: retries amplify load, latency spikes cascade, and “what talks to what?” becomes hard to...

    • Apple Podcasts

    Credit the people on this episode

  3. Continuous Integration at Agentic Velocity with CircleCI’s Rob Zuber

    Jun 10, 202650 minAudio

    When code gets cheaper to produce, feedback becomes the limiting factor - CI, reviews, and the handoffs between tools can quietly slow everything down. Rob Zuber breaks down what platform engineers are seeing as teams...

    • Apple Podcasts

    Credit the people on this episode

  4. Durable Execution for Real‑World Failures with Temporal’s Cornelia Davis

    May 27, 202646 minAudio

    A lot of infrastructure and automation fails for ordinary reasons: rate limits, flaky networks, partial permissions, long-running jobs, and retries that vanish when the process restarts. Durable execution is a way to...

    • Apple Podcasts

    Credit the people on this episode

  5. You Need AI Sysadmins Can Trust, With Cribl's Nikhil Mungel

    May 13, 202655 minAudio

    What happens when a non-deterministic AI system is asked to touch production telemetry or generate changes for an SRE pipeline? The cost of being “close enough” can be lost data, downtime, or a security incident....

    • Apple Podcasts

    Credit the people on this episode