What do you like best about the product?

Not much to say here - it does CI/CD and works. The workflows feature is pretty good and saves us a lot of time when running our largest suites. Haven't had any issues with anything.

What do you dislike about the product?

You have to build and manage containers to run tests instead of just declaring a config, which is a mixed bag (more manual power but more to maintain). They have some convenience containers that are good for simple projects, but I think a feature where you could configure which container features you need and it generates a base Dockerfile or compose file would be really useful.

What problems is the product solving and how is that benefiting you?

Our old CI provider EOLed recently and we migrated to Circle to run our tests on each build. Like any CI system, this is crucial for agile development.

Recommendations to others considering the product:

Compare with Travis and see which style of configuration works best for your shop

What do you like best about the product?

GitHub integration is great since you can require the tests to pass before a PR can be merged

What do you dislike about the product?

I hate having to wait for other tests to be ran before knowing if mine passes. This can slow down how quick a hot fix PR gets deployed

What problems is the product solving and how is that benefiting you?

Definitely helps keep developers accountable for writing tests to make sure there isn’t a major break elsewhere in a product when a new feature is added.

Recommendations to others considering the product:

Use it, don’t get too far along on a project without testing. Don’t generate the technical debt before it’s too late.

What do you like best about the product?

Very flexible, lots of built in build tools, very tight integration with GitHub

What do you dislike about the product?

Managing multiple orgs isn't the smoothest experience. There have been A LOT of outages lately. It makes it hard to recommend an otherwise awesome build tool.

What problems is the product solving and how is that benefiting you?

CI builds and tests. Their performance plan dramatically sped up our slow builds when it's working.

What do you like best about the product?

We run a fairly complex flow that takes every new commit, runs the tests for it, builds the app then uploads it to App Store Connect. Since we're pushing several builds per day, it easily saves us at least 2 man-hours each day. It's very easy to set up, easy to customise to your own specific build pipeline and integrates well with other tools to send notifications when things go wrong.

What do you dislike about the product?

Nothing major, really. The UI could be better, but to be honest, you won't spend much time in the UI once everything is set up.

What problems is the product solving and how is that benefiting you?

The build process for a mobile app gets longer and longer these days, so CircleCI helped us automate most of the process, saving us plenty of time every day (we push multiple builds daily).

Recommendations to others considering the product:

I highly recommend implementing CircleCI as your CI backbone. You'll thank yourself.

What do you like best about the product?

Circle-ci has helped us to build a CD/CI.
Also we are using it to automatically deploy our software in staging and production environments

What do you dislike about the product?

Anything, circle-ci is a very good platform

What problems is the product solving and how is that benefiting you?

Very good, everything was ok and when i had a problem they contacted me

Recommendations to others considering the product:

Yes i definitely recomend it

What do you like best about the product?

CircleCI provides quite a nice declarative interface for CI/CD pipelines. We use CircleCI for everything from application code CI/CD to deployment of our infrastructure via Terraform, to pushing Kubernetes manifests for K8s resources. The integration with GitHub is nice, and the support for GitHub releases is a very nice feature.

I think the real power of CircleCI is that application teams are able to completely own their own pipelines. By storing configuration along with the application code developers are able to own their pathway to production using reproducible configuration.

What do you dislike about the product?

We use CircleCI Server running in AWS. I think the biggest problem we have is that the server version is quite far behind in feature set compared to the SaaS version. With no support for version 2.1 configuration, and by extension features such as parameterised commands and jobs, and orbs. This is really disappointing, because it makes it hard to utilise CircleCI to its full extent.

The other primary issues we have with CircleCI are:

- The interface is seriously lacking. The workflow view doesn't scale well with large workflows, making it annoying to use when a pipeline has more than half a dozen sequential jobs.

- The API is poor. It has limited support for programmatically managing workflow operation, and generally displays rather poor design. Not supporting the ability to retrieve a specific number of objects (e.g. "Return me the first 55 projects that I don't follow"), inconsistencies with returned fields (e.g. Followed projects from the /projects endpoint return "reponame" and "followed" fields, whereas /user/repos returns "name" and "following" fields.), inconsistent use of pagination, etc.

- Configuration in a single file. This can be worked around by using the CircleCI CLI with the `config pack` command, but it would be nice to see support for spreading config across multiple files without having to include this additional, manual, step.

- Can't reference configuration within another repo (see ConcourseCI). It would be nice if we could have a repo dedicated to small, reusable CircleCI config files that can simply be referenced via the GitHub URL (with support for parameters). I know Orbs is meant to solve this issue, but right now server users don't have access to the orbs feature, and there is no support for private orbs.

- Triggers are rather arbitrary. Currently the only way to kick off a workflow is either manually, or via a PR/commit. Additional triggers, such as "PR merged" would be very useful, as this would allow us to more easily spin up and destroy PR specific temp environments.

- Can't default the resource class across all jobs in CircleCI Server.

- Can't trigger a job on the condition that a previous job failed (this would be useful for cleanup scenarios, such as a terraform apply failing halfway through applying).

- Can't run CircleCI Server on Kubernetes, have to use Nomad. This means we have to manage a separate orchestration cluster for CircleCI, rather than being able to utilise our Kubernetes expertise.

- Metrics are kinda garbage on CircleCI Server. No obvious way for gathering metrics of remote docker instances. Metrics have to be gathered mostly from Nomad, rather than CircleCI providing these metrics (e.g. Deployment metrics, build metrics like build times/job times, etc).

What problems is the product solving and how is that benefiting you?

- Kubernetes resource deployments (e.g. control-plane, operators, etc.)
- Application releases via Helm.
- Terraform automation.
- Cron style task that run on schedule.

Recommendations to others considering the product:

Only use CircleCI Server if you really have to as it takes key features from the product.

What do you like best about the product?

Easy to share configuration via workflows, contexts, orbs.

Very good Docker support

What do you dislike about the product?

Web UI hierarchy of jobs vs workflows is confusing to me

It's not easy to report on jobs at an organization-wide level

What problems is the product solving and how is that benefiting you?

Our main workload is building .NET Core applications and deploying via CloudFormation. This includes spinning up complex end-to-end automated test suites involving multiple Docker containers.

What do you like best about the product?

As an amazing and simple platform for building code on my testing and production enviroment, CircleCI helps my all my software developers coworkers and all the product team to rapidly build code, test the esctructure and aprove deployments. It's also really simple to create integrations with tecnology such as git, github and more. CircleCI makes really simple the manager processes of my workflows deploys.

What do you dislike about the product?

I don't habe any aditional deslikes for CircleCI, just some insights that could improve the platform to be better for my workflow like: improve the search filters on my jobs and workflows list. The Insights feature could have difrents types of graphics too.

What problems is the product solving and how is that benefiting you?

Building software , management deployment, security deployment process, continuous integration and testing.

Recommendations to others considering the product:

In the tech market, the service ofered for CircleCI is one of the best. It makes really easy the process of building, management and deploy software. The implantation process it is also really simple. Me and my coworkers are happy with the platform and totaly able to recomend this.

What do you like best about the product?

We have been using Amazon for a few years, not only CircleCI but also S3, EC2, Beanstalk, among others. Regarding CircleCI, it definitely made our continuous integration process much easier, with automatic deployments, multiple environments, rollbacks, among other things.

What do you dislike about the product?

Currently, everything pleases me, but there could be better and greater parallelism between the deployments. I know we can improve the plan, but currently we only have two deployments at the same time.

What problems is the product solving and how is that benefiting you?

Deploys super fast and simple, version control for dev, staging for prod, approval for production release with just 1 click.

What do you like best about the product?

I like the ability to check for rules in my config and throw errors

What do you dislike about the product?

I don't really have anything that I dislike

What problems is the product solving and how is that benefiting you?

Checking for no console logs, running tests, etc. Prevents build errors and junk getting into master

Recommendations to others considering the product:

none