“I can use Insights from CircleCI to see all of the stages a test went through. I’m able to fail faster, which keeps my productivity higher."

“By allowing us not to focus on infrastructure, we’re able to aim [our efforts] where we think we can provide more value, and that’s one of the great takeaways I’ve had from working with CircleCI.”

“Using CircleCI caused a marked jump in our confidence that we can merge our pull requests without breaking real Gatsby applications downstream.”

“CI/CD is critical for success for all companies, but there are a lot of ways to do it. CircleCI allows us to easily and quickly get projects onboarded and connect them with other parts of the tech stack.”

"Our engineers couldn’t imagine living without test splitting – they get test feedback in about 10 minutes.”

“CircleCI is integral to what we do here,” says Nick Iovino, Infrastructure Engineer at AdWerx. “It makes everything stress-free. We know that if something goes wrong, it’s going to be pretty easy to revert or remediate. We know that if we have downtime, it’s going to be pretty short – …

“Our approach was very much one size fits all. We were happy with any solution that did automated and fast builds.”

"Now that we’re a mid-size company, I don’t foresee us changing anything for the next few years.”

“The Next Domestic Passenger Project was launched and ANA is developing a system as a transformation support partner for ANA Group’s existing and new businesses.”

“Our company handles both front-end and back-end system development. We felt that the ability to build an environment that matches the characteristics of each system was a good fit for our business.”

“There are many different environments we run tests in. To have the confidence that all the pieces are functioning takes a lot of dev hours.”

“With 17 engineers, everyone is touching the same codebase."

“We chose CircleCI because it was easy to set up and gave good visibility to the whole team about the state of our tests. It worked out of the box with pre-built images that supported most of our system components. We were able to easily configure specific Docker images for …

“A lot of folks think it’s just content. But there’s a lot going on behind the scenes to get that text on the screen and deliver it to millions of people.”

“We had one teammate who was running Jenkins – logging in the morning, checking, breaking everything, and asking us to fix the issues he introduced. It was time-consuming for him and for at least one person on each specific team.”