Buildkite

CI/CD is a very mature market... (happy 20th b-day, Jenkins, you old rascal!) That doesn't mean it's lost its allure, though. AI-assisted coding, AI/ML projects & the outrageous scale of mobile app development are here to shake things up. And meeting these new demands won't be easy... ...which is why we're excited to share what we've been building here at Buildkite. (spoiler: it is not kites… ??) Today, we're proud to announce the launch of our new Scale-Out Delivery Platform – a way for software teams to confidently move beyond CI/CD... ...& turn delivery into their competitive advantage. "But what does this marketing PR stunt even mean?!?" we hear you snark! Happy to clarify. We describe it like this: Buildkite's Scale-Out Delivery Platform scales in four distinct dimensions: - concurrency - components - workloads - compute with the following tools to support them: - scalable workflow orchestration with Buildkite Pipelines - faster test workloads with Test Engine - secure artifact management with Package Registries - optimized mobile app delivery with Mobile Delivery Cloud With our new platform, your teams will be ready to handle anything – keeping innovation at the forefront (not treating it as “just one more thing…”). So, are you ready to tame complexity & turn software delivery into your competitive advantage? If "yes," visit Buildkite [dot] com to learn more & start your 30-day free trial. If "no," cool cool cool cool...just keep scrolling & enjoy the rest of your day. P.S. You can read more about the news here: https://lnkd.in/gVw9tanW

A few weeks ago, in San Francisco, we met up with over 30 software engineers to discuss the biggest challenges in software delivery. Here's a quick tl;dr:

Evaluating package management tools? See how Buildkite stacks up to one of the biggest tools on the market: https://hubs.ly/Q03dqgpN0

Your packages shouldn't need a database to be reliable and fast. Many traditional repository managers are built on database-dependent architectures that become bottlenecks at scale. This fundamental limitation means that as your team grows, you're forced to invest more and more in database management, tuning, and scaling - skills that are increasingly hard to find and retain. Modern cloud-native architectures separate the control plane from the data plane, keeping your packages in your own cloud storage while delegating the hard parts to a managed service. With Buildkite's Private Storage Link, your packages remain in your own AWS S3 buckets - giving you complete control and data sovereignty while eliminating the operational burden. Curious about how to set up Private Storage Link and keep your packages in your own cloud? ?? https://hubs.ly/Q03dm8kS0

DevOps teams are spending hours maintaining package repositories instead of shipping features. When your engineers are debugging database connectivity issues with Artifactory or tuning PostgreSQL performance at 2am, they're not delivering value to your customers. Traditional approaches often require dedicated infrastructure teams just to keep package management running at scale, especially when high availability is a must. There's a smarter way to handle your artifacts without the operational burden. See how ?? https://hubs.ly/Q03cpNq00

Join us tomorrow, 25 March 2025 for a special session featuring Ken Thompson VP of Product at Buildkite - a leading platform revolutionizing continuous integration and delivery used by winning companies such as Uber, Canva, Shopify, and many others. Ken brings over 14 years of SaaS experience, including 12 years in product management, and has been instrumental in helping engineering teams ship faster with fewer headaches. Don't miss this opportunity to gain insights from an industry leader. Register now: https://lnkd.in/gvvc-Aaa Recording will be available on: https://lnkd.in/grvkbHbp

I am no fan of YAML, so I am happy to announce we've started publishing a library to help folks define their pipelines in a programming language. Available in JavaScript, TypeScript, Python, Go and Ruby. Treat your CI/CD pipelines like software. https://lnkd.in/gbv5mVxZ

If you are headed to SREcon next week, stop by our tailgate party with Spacelift, honeycomb.io, Oso and Cloudsmith. ?? https://lnkd.in/gcsGVnhH

?? Friday resource roundup: Discover the impacts of AI-generated code on large monorepos: https://hubs.ly/Q03c9BZ50 Understand the challenges of scaling Jenkins for monorepos: https://hubs.ly/Q03c9C0X0 See why teams are moving from static > dynamic pipelines: https://hubs.ly/Q03c9Bw_0 Hear how Hasura "burned down 2000 lines of YAML": https://hubs.ly/Q03c9C5z0 Hope you find these resources valuable – have a great weekend!

Your delivery pipeline should be real software, not just a bunch of scripts. When Jenkins first came out, using XML to wrap shell scripts was cutting-edge for CI/CD. Teams used it because it was simple and worked well enough. But when your codebase grows to millions of lines and thousands of daily changes, you hit a wall. You just can't write the complex logic you need for smart test selection using only Groovy and Bash. The big change is moving from fixed, pre-written pipelines to ones that your code generates on the fly. This lets you shape your build process using the same programming languages you use for your actual products. This isn't a small tweak—it's a completely new way of thinking about how to deliver software at scale. See how we help you do this: https://hubs.ly/Q03c9Bky0