CircleCI

Good for CI/CD and also for automating smaller tasks

Comentarios: We use CircleCI for our CI/CD pipeline almost every single day. It manages and runs automated tests for all the remote branches, so we can catch issues before they escalate. When ever something gets merged into our dev, staging or master branches, it auto tests, builds and deploy all the infrastructure with Terraform and pushes the newer version to docker.

Puntos a favor:

The pipelines can be broken into different steps, which makes debugging, managing and approving individual phases way easier. Also, looking at the logs and being able to share static permalinks to them is quite useful when you have larger teams. We all can see the progress of the building pipelines in real time and can debug and manage them. Great tool over all.

Contras:

Sometimes it fails and doesn't immediately let's you go to debug the issue. Also, some settings for the VMs are tricky to set up right.

CircleCI - For Simple, Easy & feature rich CI/CD

Comentarios: Overall I love CircleCI UI, ease of deployment & it is feature rich. Availability & execution parameterization can be improved.

Puntos a favor:

Best part of circleCI is the ease of continuous delivery feature it offers, it's very easy to integrate it with GitHub too. Another pro of CircleCI over other CI/CD tool like Jenkins is the simple yet feature rich UI. For beginners or pros, this workflow management tool is pretty simple yet futuristic. It also makes running automated test cases for different branches really easy before deployment.

Contras:

There is room for improvement in areas where Jenkins is already winning, like skipping parts of execution stages that are not required every time new change is pushed. Another one would be the execution time, using it with terraform to run plans & eventually apply, it can take hours if your infrastructure is complex & there is no way to actually divide it in stages. Better central monitoring & dashboard for different projects can be helpful, somewhat like Jenkins shows rainy, cloudy or clear skies signifying project health.

Does the job, but lacking in features

Puntos a favor:

It's relatively simple to get started. I like that you can pick between Docker and VMs. It integrates with GitHub nicely.

Contras:

The Docker in Docker paradigm doesn't work for us since we use containers. We end up using VMs anyways. I think the configuration language is not that great to use and can quickly get unwieldy for larger CI workflows (especially when repeating jobs with different parameters). There are also outages at least once a quarter.

Great once you're all set up

Puntos a favor:

- Easy to understand yaml config format - Integration with GitHub - Workflows for powerful deployment and release strategies - Good community support

Contras:

- I am not the biggest fan of the recent UI update. If the "expand" toggle is set to true, everything jumps resulting in me clicking things unintentionally. - Many of us have workflows that we do not use on every push (e.g. deploying to testing). With the next UI changes, the UI has a timer column which is always updating, why??? - Why can't I select a default project? When I now browse to circleci, I always have to select a project. Most developers only ever work on one project at a time, let us choose one!

One of the top CI/CD service

Puntos a favor:

With a Github/Bitbucket account, it is easy to setup the CircleCI account. It automatically detects all the repositories. We can easily add the configuration file and start using the pipelines. Various customisation and parallelisation options are provided. Lot of possibilities for automation and customisation. Overall a good product.

Contras:

It was bit of a hassle to start first, the configuration were not very easy. Also struggled a bit to manage various Github organisations. Once easy and setup, it's easy and fast.