CircleCI vs. CloudBees Continuous Integration

CircleCI is well suited if you, your developer, or team of developers have already worked with it in the past. They don't need to go through the learning curve of yet another Continuous Integration tool. Circle handles Continuous Integration workflows very well, including pretty complex workflows. With that said, Circle can get expensive if you need to run multiple containers in parallel and might not be as easy to setup as some alternatives, such as Jenkins.

Incentivized

If you're running Jenkins in your enterprise and it's in the critical path of your software pipelines, I highly recommend CloudBees Jenkins over the open source version of the product to ensure you've got the customer and technical support you'll need for your Jenkins platform to be successful.

Incentivized

• Full customization and scripting abilities. Using tools like bash scripts, SSH, and Node, running almost anything upon committing some code to GitHub becomes possible.
• Integration with all of our favorite services. GitHub and Slack in particular are crucial to our business and CircleCI's integration is seamless and full-featured.
• Great config file syntax. Many CI services require you to perform advanced configuration in a UI. This is fine at first (and CircleCI offers this for many options available), but when you start needing to manage a large number of projects, committing configuration changes to a Git repository is more consistent and maintainable than making the change many different times manually in a UI.

Incentivized

• Customer Support
• Solutions engineering

Incentivized

• CircleCI mostly getting built into both upstream platforms (Github/Gitlab) and downstream platforms (AWS, Azure, GCP), in which cases it's often a better fit or can be used as a part of existing tooling
• UX can be confusing to navigate and see what's happening.

Incentivized

• File or Workspace Management
• Agent configurations at master level
• Better Support for issues in product

Incentivized

CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in

Incentivized

It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.

Incentivized

I haven't personally used their support service, but I have heard from others that they are responsive. I've also seen only one or two downtimes in over a year of use and both were no more than an hour or two.

Incentivized

Support seems very unreachable from my experience. They handle cases if developers are facing issues, support seems to be very limited. It's not like other tools in a market where every mail is being taken priority and responses are sent. We see a lack in this particular aspect when it comes to CloudBees Jenkins Platform.

Incentivized

Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the infrastructure and scale yourself. They're both good products if you require more than CircleCI, but if not, skip the extra headache and go with something simple like CircleCI.

Incentivized

Easy to lean, use, highly customizable pipelines, works well for version control, etc. Example Digital.ai gives all those features which can be done in Jenkins like builds, deployment, release management, etc. But, it requires universal templates to be created which are difficult to maintain and readable like groovy pipelines in Jenkins.

Incentivized

• Saves us a lot of time and reduces potential mistakes by making our deployment and QA process completely automated
• Builds docker images for us so we don't have to build them locally on our machines
• Runs tests automatically on every commit, so we catch mistakes early

Incentivized

• Positive - Handles number of requests
• Positive - Customizations of pipelines helps integrate many type of frameworks
• Negative - Cache management on agents for dependencies downloaded
• Positive - credential management helps reduce configurations to be done for each project job at manual level

Incentivized