Buildkite

Discover how Uber tackled a major productivity challenge in their Go monorepo: - 50 million+ lines of code - 3000+ engineers - 1000 commits daily The result? They slashed build times by 50% and dramatically improved developer productivity. Key takeaways: - Dynamic CI pipelines for flexible, scalable workflows. - Smart containerization strategies for faster builds. - Automated dependency management across 2000+ dependencies. - Improved visibility and monitoring of build processes. Learn how Uber leveraged Buildkite to transform their CI/CD pipeline, boost developer satisfaction, and maintain code quality at scale. Whether you're managing a growing monorepo or looking to optimize your development workflow, there are valuable insights for engineering teams of all sizes. Read the full story 👇 https://lnkd.in/g-Fv5tCf

Developers & engineers, you asked & we listened... You now – FINALLY – have a way to visualize your CI/CD pipelines, AND have music to practice your salsa dancing to while you wait 💃 🕺 💃 Shout out to Tom Watts for making this dream a reality 💚 Surely, your dance instructors will thank us for this (oh, and here's the technical product stuff you might want to know, also👇) ICYMI – a few weeks ago, we launched our new Buildkite build canvas: A new way to visualize your CI/CD pipelines. The canvas helps you: - View your pipeline as a directed acyclic graph (DAG) - Highlight key paths through the build - Jump to failed steps for faster debugging - Use the follow mode to see the status of running steps For all the details about the build canvas and a demo of the key features, see the announcement blog: https://lnkd.in/gh-CXnEu

The era of genAI code means more code – (a lot) faster. The problem? Legacy systems (like Jenkins) may struggle to keep up. In the article below, we explore the 3 most common issues related to Jenkins & how to overcome them. Swipe to discover: - what these issues are - why teams are getting frustrated by them - & what you can do about it P.S. Curious to learn more? Check out the full blog here: https://lnkd.in/g7FiFyr9

Uber scales up 100,000 concurrent agents to blast through 1,000 daily commits on their monorepo codebase, comprising over 500,000 files and 50 million lines of code. 🤯 Hear how Uber accelerated their monorepo software delivery by switching from legacy tools to Buildkite. In this presentation, engineers Xiaoyang Tan and Tyler French walk through the journey of how the Uber engineering team: - Built reliability tooling to help track performance and provide solutions to scale out to thousands of developers - Leveraged Buildkite to evolve their Go monorepo's CI infrastructure - Optimized the processing time by 50% Access the full webinar replay here: https://lnkd.in/gHvhJfdE

LambdaTest's 2024 Testμ ('TestMu') Conference is happening this week – Aug 21-23. Will you be there? Here's what you can expect from the conference: 💡 Learn about meaningful QA & testing trends from 60+ experts 🤙 Network with 30,000+ attendees from 132 countries 🤑 Participate in exciting challenges & win goodies worth up to $10k There's still time to join – get more details here: https://lnkd.in/gXQbytEa P.S. If you're wandering around the virtual booths, you should stop by ours & say "g'day" 👋

Introducing Buildkite's build canvas: A new way to visualize your CI/CD pipelines. The canvas helps you: - Quickly understand pipelines: View your pipeline as a directed acyclic graph (DAG). - Decode dependencies: Highlight key paths through the build. - Troubleshoot issues: Jump to failed steps for faster debugging. - Follow a build's progress: Use the follow mode to see the status of running steps. Andy Tang, Staff Platform Engineer at SEEK, shared: "The build canvas is great because it lets me visualize another team's pipeline very quickly when debugging an issue. This saves me time, as previously, I had to unpick the logic manually by inspecting their generated pipeline.yaml. For teams that have multiple levels of pipeline abstractions, this is a game changer." Eathan Langford, Developer Experience at MYOB, shared: "The canvas has made it easier for us, as the Platform team to easily see dependency pathways for steps in a build. This lets us see at a glance how the pipeline has performed and where things go wrong, easily letting us debug with our engineers." For all the details about the build canvas and a demo of the key features, see the announcement blog: https://lnkd.in/gh-CXnEu

Whether you're on the GenAI train or not, it's clear that the velocity and volume of code creation are increasing. If you're facing scaling issues with your existing tools, it will only get worse. First-generation CI/CD systems like Jenkins are starting to buckle under the pressure. Remember when deploying 10 times a year was a big deal? Today, deploying 10 times an hour is more the norm. We've heard many stories where Jenkins shows its age, but they all share some common themes: Scale ceiling: Adding your second, third, or even fourth Jenkins controller might feel manageable. But as teams hit their 10th, 20th, or more, the infrastructure becomes fragile and unmanageable. Each new controller adds complexity and risk. Plugin chaos: Jenkins relies heavily on plugins for functionality. Unfortunately, many plugins become abandonware, leaving teams to either maintain them or face security vulnerabilities. Compatibility issues slow down upgrades and can cause significant downtime. Outdated UI: The Jenkins UI is a common pain point. It's often seen as outdated and cumbersome, leading to frustration and reduced productivity. Triaging and resolving issues in CI becomes a bottleneck. These problems add up, leading to what we call "delivery decay." Teams lose valuable time waiting for pipelines to complete, dealing with crashes, and managing an increasingly complex infrastructure. The productivity cost and maintenance burden of staying on Jenkins sneaks up on you. What will be your breaking point with Jenkins? https://lnkd.in/g7FiFyr9

Whether you're on the GenAI train or not, it's clear that the velocity and volume of code creation are increasing. If you're facing scaling issues with your existing tools, it will only get worse. First-generation CI/CD systems like Jenkins are starting to buckle under the pressure. Remember when deploying 10 times a year was a big deal? Today, deploying 10 times an hour is more the norm. We've heard many stories where Jenkins shows its age, but they all share some common themes: Scale ceiling: Adding your second, third, or even fourth Jenkins controller might feel manageable. But as teams hit their 10th, 20th, or more, the infrastructure becomes fragile and unmanageable. Each new controller adds complexity and risk. Plugin chaos: Jenkins relies heavily on plugins for functionality. Unfortunately, many plugins become abandonware, leaving teams to either maintain them or face security vulnerabilities. Compatibility issues slow down upgrades and can cause significant downtime. Outdated UI: The Jenkins UI is a common pain point. It's often seen as outdated and cumbersome, leading to frustration and reduced productivity. Triaging and resolving issues in CI becomes a bottleneck. These problems add up, leading to what we call "delivery decay." Teams lose valuable time waiting for pipelines to complete, dealing with crashes, and managing an increasingly complex infrastructure. The productivity cost and maintenance burden of staying on Jenkins sneaks up on you. What will be your breaking point with Jenkins? https://lnkd.in/g7FiFyr9

Tomorrow: Scaling CI for a monorepo with over 50 million lines of code and 1,000 daily commits is a daunting task. Uber has perfected their approach, and we’ll share their insights in our upcoming webinar. Topics include Bazel for understanding and optimizing build targets, dynamically generating CI build steps for complex changes, improving CI performance with containerized environments, and Uber’s custom tools for CI efficiency. Join us tomorrow for an in-depth look at Uber’s CI strategies. Register now – registrants will get access to the webinar and a recording: https://lnkd.in/eZBtuy2n

Are you headed to AWS Summit New York? Join us along with our friends at Lacework for our post-event happy hour. Register: https://lnkd.in/gfzbY2pR