1min chapter

DevOps Paradox cover image

DOP 203: Dealing With Flaky Tests and Broken Builds With Aviator

DevOps Paradox

CHAPTER

How to Merge Changes at Scale

The Merge Q concept is essentially the first time I actually heard about this, was from a blog, a white paper by Uber. And we've taken a lot of inspiration from that, plus talking to a lot of other companies at scale. How do they merge thousands of changes in a day where every developer in the company could be thousands of developers are actually using the same codebase? How do you think about adding different layers of orchestration to ensure your builds never break? Obviously, there are many different strategies that you can apply, including batching and optimistic queuing.

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode