“It’s outdated, it’s been there for too long, and it’s lagging behind. But people still keep using it and stumbling on the same mistakes and problems and resource consumption.”
“It was a heavy lift to figure out the logistics around their request."
“We use CircleCI to test all of the touchpoints between our platform and Drupal, for example, and create scripts that fire up the tests automatically.”
“We have to install OS-dependent libraries depending on the programming language used for a build, which requires getting root privileges for the CI tool used. It’s not a good idea to give engineers the root privileges for security reasons, so we needed to ask the CI tool administrators to install those libraries.”
"The UI is very easy to understand, it’s easy to get new engineers up and running, and CircleCI ensures everything works.”
“CircleCI has helped us automate lots of tasks, so developers only have to worry about building the product. That gives them the necessary focus to build faster and better.”
"CircleCI helped us improve build system simplicity and stability, which reduced the support requests from our teams by 90%.”
"The overall stability of CircleCI is remarkable in comparison to previously used CI providers and other cloud-based development tools.”
“CircleCI is the backbone of our software development lifecycle, since it allows us to push software faster, test things faster, and keep iterating.”
“When I give demos of Poplog and people ask, ‘How would you put that into the CI pipeline?’ I just say, ‘CircleCI.’ It’s that straightforward.”
“If your test suite takes an hour your minimum incident resolution time can’t be faster than an hour."
“With the process changes and automation improvements that CircleCI helped us introduce, we’ve gone from just one deployment every two weeks to eight deployments every day – a 64X improvement.”
“The biggest change for me was that a lot of things we used to have to do manually are now automated. We can fix things faster, and investigate faster.”
“Having flaky tests can be a major pain. Now we have data that we can quickly drill into.”
"Since we implemented Docker layer caching, we’ve saved about 2,000 hours of developer time in the last six months.”