More people across CircleCI are getting the chance to build. And that hands-on experience creates a different kind of understanding of the tools developers use, the problems they run into, and the work our customers do every day. Rob Zuber on what happens when the barrier to building gets lower. More from Rob and Jim Rose in this Peer Review: https://circle.ci/4gzETRv
CircleCI
Software Development
San Francisco, California 36,644 followers
CI/CD at AI speed. Validate code autonomously. Ship confidently.
About us
CircleCI is CI/CD built to accelerate code delivery with limitless scale and speed. We help engineering teams validate code autonomously and ship with confidence at AI speed. Trusted by thousands of teams worldwide to power their software delivery.
- Website
-
https://circleci.com/
External link for CircleCI
- Industry
- Software Development
- Company size
- 201-500 employees
- Headquarters
- San Francisco, California
- Type
- Privately Held
- Founded
- 2011
- Specialties
- continuous integration, continuous delivery, SaaS, cloud computing, developer tools, enterprise, continuous deployment, containers, PaaS, DevOps, CICD, CI/CD, software delivery, CI platform, software testing, and developer experience
Products
![Click here to view CircleCI]()
CircleCI
Continuous Integration (CI) Software
CircleCI is the world’s largest shared continuous integration and continuous delivery (CI/CD) platform, and the central hub where code moves from idea to delivery. As one of the most-used DevOps tools that processes more than 1 million builds a day, CircleCI has unique access to data on how engineering teams work, and how their code runs. Companies like Spotify, Coinbase, Stitch Fix, and BuzzFeed use us to improve engineering team productivity, release better products, and get to market faster. Founded in 2011 and headquartered in downtown San Francisco with a global, remote workforce, CircleCI is venture-backed by IVP, Sapphire Ventures, Owl Rock, NextEquity Partners, Scale Venture Partners, Threshold Ventures, Baseline Ventures, Top Tier Capital Partners, Industry Ventures, Heavybit, and Harrison Metal Capital.
Locations
Employees at CircleCI
Updates
-
🗽 NYC! We're getting together with Qodo on October 22 to talk about what happens when AI agents move beyond the demo and into production. Our very own Ryan Hamilton will share findings from three Loop Lab experiments exploring how to build agent loops that ship green PRs on the first push. Join us for Ryan's talk, a panel discussion, and networking with fellow builders!
-
Smarter Testing is now generally available in CircleCI. 🎉 Instead of running your entire test suite after every code change, Smarter Testing uses Test Impact Analysis to identify and run only the tests affected by that change. In this example, a change to one pricing file meant just 44 of 9,716 tests needed to run. The other 9,672 were skipped, taking test runtime from 3 minutes and 56 seconds to 22 seconds. Smarter Testing also dynamically splits tests across nodes based on historical performance and can automatically rerun flaky tests. Learn more and get started: https://circle.ci/3TotSLg
-
CircleCI reposted this
AI can help us write code faster. But how quickly can we check that it actually works? Does it happen to you? 1. Your agent finishes a change. 2. You push it, wait for CI, discover a failure, and send it back for another fix. 3. Then you wait again. Across a team, those repeated cycles add up in development time and compute costs. In this video, I walk through the problem and how CircleCI’s Chunk sidecars can help. 👇 1️⃣ What the data shows CircleCI’s 2026 annual State of Software Delivery report gives some context: - For the typical team, daily workflow runs on feature branches increased by about 15%. - Daily workflow runs on the main branch fell by almost 7%. - Main-branch workflow success dropped to 70.8%. Note: More activity while developing changes doesn’t automatically translate into more successful delivery. 2️⃣ How Chunk sidecars help The idea is to bring focused checks into the agent’s development loop. → Send changes to a lightweight remote environment configured for your project → Run selected builds or tests, which CircleCI calls “microbuilds” → Return failures while the agent still has the task in context → Give the agent a chance to fix the issue and validate again before pushing → Help avoid another push, wait, and fix cycle for issues those checks catch You keep coding locally while validation happens remotely. A sidecar only checks what you actually run. Check out the video below for complete walkthrough👇 Learn more: https://lnkd.in/d6eFTeMQ ♻️ Repost if you found this helpful 💚
-
CircleCI reposted this
AI can help us write code faster. But how quickly can we check that it actually works? Does it happen to you? 1. Your agent finishes a change. 2. You push it, wait for CI, discover a failure, and send it back for another fix. 3. Then you wait again. Across a team, those repeated cycles add up in development time and compute costs. In this video, I walk through the problem and how CircleCI’s Chunk sidecars can help. 👇 1️⃣ What the data shows CircleCI’s 2026 annual State of Software Delivery report gives some context: - For the typical team, daily workflow runs on feature branches increased by about 15%. - Daily workflow runs on the main branch fell by almost 7%. - Main-branch workflow success dropped to 70.8%. Note: More activity while developing changes doesn’t automatically translate into more successful delivery. 2️⃣ How Chunk sidecars help The idea is to bring focused checks into the agent’s development loop. → Send changes to a lightweight remote environment configured for your project → Run selected builds or tests, which CircleCI calls “microbuilds” → Return failures while the agent still has the task in context → Give the agent a chance to fix the issue and validate again before pushing → Help avoid another push, wait, and fix cycle for issues those checks catch You keep coding locally while validation happens remotely. A sidecar only checks what you actually run. Check out the video below for complete walkthrough👇 Learn more: https://lnkd.in/d6eFTeMQ ♻️ Repost if you found this helpful 💚
-
The old playbook was pretty straightforward: build the product, refine it, then build the organization that takes it to market. That separation doesn’t really exist anymore. Jim Rose on why building has become a continuous part of the job when the tools, technology, and expectations can change every 48 hours. More from Jim and Rob Zuber in this Peer Review: https://circle.ci/4gzETRv
-
Turns out telling coding agents what to do over and over again doesn't actually make them better at fixing CI failures. Here's what worked instead (and cut token usage by 25%): https://circle.ci/474f2Nh
-
Our first-ever SF Tech Week event is in the books! 🌉 Yesterday, we hosted a hands-on workshop with Rob Zuber about how engineering teams can rethink their software factories as the way we build changes. More than 80 people joined us, from founders and engineering leaders to software, AI, and ML engineers. The conversations kept going right up until we had to call it a day. Thanks to everyone who spent part of a very busy Tech Week with us, to Rob for leading the workshop, and especially to Angeline M. and the rest of the team for bringing the whole thing together. 💚 (And because one event wasn’t enough for Rob, he headed over to Camp AI later that evening for a demo on production-ready agents!)
-
-
Happy SF TECH WEEK by a16z! We've got plans for you tomorrow. 🎉 More code is being generated faster than ever. The challenge now is knowing what you can trust enough to ship. Rob Zuber is leading a hands-on workshop on exactly that, sharing what his team has learned before we work through it together. We'll have lunch and coffee from Cento, a Chunk keyboard up for grabs, and office hours with our field engineers. Come hang with us: https://lnkd.in/g8JHzi8u
-