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?

Usamos a alguns anos a Amazon não somente o circleci mas também s3, ec2, benastalk entre outros sobre circle, concerteza facilitou muito nosso processo integração continua, deploys automático e vários ambientes, rollback dentre outros

What do you dislike about the product?

Atualmente tudo me agrada, o que poderia ser melhor e paralelismo maior entre os deploys. Sei que podemos melhorar o plano, mas atualmenteso temos dois deploys ao mesmo tempo

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

Deploys super.rapido e simoles, controle de versão dev, homolog prod, aprovação de publicação em produção com apenas 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

What do you like best about the product?

Love the pipelines and orbs. Web interface is nice to use

What do you dislike about the product?

If one job fails you can’t continue pipeline

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

Best cicd that’s integratable with GitHub

What do you like best about the product?

The simplicity with which I can automate the build, testing, and deployment workflow in a few very short-time.

What do you dislike about the product?

It doesn't support manually trigger builds.
Available metrics are a bit poor.

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

It has been helpful to automate the build, testing, and deployment process quickly in many projects. We can focus on app configuration files without having to worry about infrastructure setup and maintenance on the CI server side.

What do you like best about the product?

The continuous deployment process with circle CI is easy to setup with GitHub . You can have the different pipelines configured for production and staging environments and circle manages them without any trouble .

What do you dislike about the product?

Need to manually change the configs whenever I update my dev environment like tool version change or coco pods version change or fast lane version change. If it can automatically update its configs based on my project settings, that would be awesome. This is the only issue I have at the moment.

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

It really saves lot of dev time in sending out the builds. You could save an hour a day minimum with this. Especially if you were to send multiple builds every day for testing, this should be your saviour.

What do you like best about the product?

I particularly like the automated workflows and on top of it, integration with third party apps like slack.
It is easy to use and learn.
Widely accepted so large community support available.
You don't need to resolve dependencies unlike other simillar platforms.
It is lightweight and have robust cloud servers.
Quick setup.
Debugging is easy.
It has built-in assistance for Docker in the workflow.

What do you dislike about the product?

CircleCI offers a limited setting for encrypted files and maximum data on CircleCI is available for developers to access.
Cost per user is high.

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

We are able to solve our Continues Integration, testing and releases with the help of CircleCI. Having automated releases is the most beneficial thing for us.

Recommendations to others considering the product:

I would simply say 'Go for it, give it a try and you won't look back for anything else for you CI/build processes'.