CircleCI vs. CloudBees Codeship

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CircleCI
Score 9.5 out of 10
N/A
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$15
per month
CloudBees Codeship
Score 9.0 out of 10
N/A
Codeship from CloudBees is a build automation platform from the Austrian company of the same name.N/A
Pricing
CircleCICloudBees Codeship
Editions & Modules
Server
Contact Sales
Performance
starting at $15
per month
Scale
starting at $2000
per month
No answers on this topic
Offerings
Pricing Offerings
CircleCICloudBees Codeship
Free Trial
NoYes
Free/Freemium Version
YesYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CircleCICloudBees Codeship
Considered Both Products
CircleCI
Chose CircleCI
Based on the cost for feature set that we needed we went with CircleCI. There were also more people on our team that knew how to use CircleCI already compared to other products which made it a preferred choice for ramp up. Other products were not as robust and quick to …
Chose CircleCI
CircleCI is the only product we've used.
Chose CircleCI
We use CircleCI when we need a good, independent CI/CD provider in an existing workflow. That said, we've begun investing more heavily in GitHub actions as it's closer to where our code is stored. CircleCI is a feature of a workflow, and can be filled by many different service …
Chose CircleCI
CircleCI is a sass product which means you don't need to maintain your own servers. This can also be a negative as you are dependent on their service. This also means you can't ssh into a machine to see what went wrong like you can with Jenkins. However for most users this …
Chose CircleCI
Because the Travis CI features are not very good, it has a lot of problems with concurrency and the uptime of the on-cloud solution was the worst we have ever tried.
Chose CircleCI
CircleCI is still being developed and worked on continually while TravisCI is not.
Chose CircleCI
CircleCI seemed to have a quicker setup than other similar products, with a good integration with GitHub repos. Projects are quick and easy to set up within the UI, and workflows can then be created off the back of those fairly intuitively. Clever interpretation of commit …
Chose CircleCI
CircleCI is the company that is innovating compared to the other ones. I think it's a great piece of software compared to other open source options that don't have as much functionality and improved capability over time.
Chose CircleCI
While the UI on CircleCI is not my favorite, it's leagues better than Travis CI. I really like Heroku CI much better, but the functionality is much more limited there. If Heroku CI had the same functionality as CircleCI, I probably wouldn't use CircleCI.
Chose CircleCI
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 …
Chose CircleCI
CircleCI does a lot of what we need it to do; however, I believe Jenkins is a better Continuous Integration tool. Jenkins has more capabilities and integrations. In addition, Jenkins is a much more widely used tool, which means more developers are familiar with it and have …
Chose CircleCI
Not having to manage / deal with a Jenkins server is fantastic. I don't have much personally against Jenkins. I've set up and run a Jenkins server before. It's just complexity that doesn't really have much to do with the business beyond getting our software to our customers. My …
Chose CircleCI
Since CircleCI gave us its infrastructure we don't have to worry about servers, provisioning and maintenance. Also CircleCI provides us great features to increase speed of builds by adding more containers to the build. Jenkins is the best open source alternative but it requires …
Chose CircleCI
Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on …
Chose CircleCI
It was our CTO who did the evaluation, not me, but as I recall other services weren't as parallelizable. We knew we wanted to run on many containers simultaneously for fast test results.
Chose CircleCI
For us it really came down to CricleCI being the fastest and simples tool to get started with. The GitHub integration is slick and seamless and the scripting config file allowed us to configure our entire build system, including tests, in less than a day. It's very light weight …
Chose CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with Github. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
Chose CircleCI
Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.

Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at …
Chose CircleCI
Travis CI is great for open source projects – it's completely free, but CircleCI offers some support for closed projects as well. CircleCI has cheaper pricing plans, and you are able to customize them as much as you want. At Travis CI you can select only a predefined amount of …
Chose CircleCI
The biggest downside to CircleCI is that it doesn't support parameterized builds, that is testing your code against language version X and Y, or framework version A and B. Beyond that, it is really a great product.
Chose CircleCI
I had used Travis CI in some of my open source projects. However, it was too expensive for us so I looked for an alternative that was in our budget. Scrutinizer is also very useful, but also out of our budget. When we get larger I could see myself using Scrutinizer for quality …
Chose CircleCI
I think these three tools are just as good as the other except that Travis CI supports mobile a lot better but price wise, CircleCI is the best that I have found and is supports the need for a startup. For a long while, CircleCI had Docker support before Codeship but now, …
Chose CircleCI
We looked at various others, but the clincher for us was really iOS build support and CircleCi was one of the few that had it.
CloudBees Codeship
Chose CloudBees Codeship
Codeship is easier to use than Jenkins because it does not require you to set up your own server, and it provides a large amount of out-of-the-box integrations for version control systems and cloud environments. AWS CodePipeline is native to AWS and cannot deploy applications …
Chose CloudBees Codeship
Codeship has been easier for our devops team to work with as far as making delivery plans and build scripts. Anecdotally, it has been more stable over time, cutting down on time investigating why some random part of the delivery process has broken. I am not sure why this is, …
Chose CloudBees Codeship
We have been using Codeship for a few years, and what we like is that it's very clear what is built and when. We usually only have one-liners for any configuration option (build, test, deploy) and this way all changes to the build are managed in the version control system and …
Chose CloudBees Codeship
Our company uses Jenkins for all internal deployment processes for one very important reason - it's hosted internally. But Codeship is great for personal use - it has intuitive UI, easy setup and tons of integrations.
Chose CloudBees Codeship
Back in those days, we didn't know about Gitlab, and Bitbucket didn't provide a CI pipeline. Jenkins is just too much for the simple tasks we wanted to achieve, besides, we didn't have a dedicated server for the sole purpose of having our code pipelined though continuous …
Best Alternatives
CircleCICloudBees Codeship
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CircleCICloudBees Codeship
Likelihood to Recommend
8.0
(0 ratings)
9.0
(0 ratings)
Usability
10.0
(0 ratings)
-
(0 ratings)
Performance
7.8
(0 ratings)
-
(0 ratings)
Support Rating
6.9
(0 ratings)
-
(0 ratings)
User Testimonials
CircleCICloudBees Codeship
Likelihood to Recommend
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.
Read full review
Codeship is very well suited to teams that have specialized devops members along with other specialized developers. It lets the other developers focus on what they do best, without having to learn another technology stack. This has cut down on a lot of headaches at our company with developers needing to deploy code to various different hosting services across different content management systems. The experience to push code is essentially the same for a developer no matter what the underlying technology is
Read full review
Pros
  • 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.
Read full review
  • Easy and fast deployment
  • A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
  • Getting tests to run is fast and easy
Read full review
Cons
  • 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.
Read full review
  • UX: The overall UX is not bad, but it still needs a lot of improvement.
  • It took me quite a while to realize that in order to switch projects I needed to press my current project name so a dropdown would appear.
  • Integration with bitbucket is somewhat hidden from the users's hands. Got to make some improvements there.
Read full review
Usability
CircleCI interface is awesome in that it is relatively modern and makes it clear exactly which parts of the engineering lifecycle you are in
Read full review
No answers on this topic
Performance
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.
Read full review
No answers on this topic
Support Rating
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.
Read full review
No answers on this topic
Alternatives Considered
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.
Read full review
Codeship is easier to use than Jenkins because it does not require you to set up your own server, and it provides a large amount of out-of-the-box integrations for version control systems and cloud environments. AWS CodePipeline is native to AWS and cannot deploy applications reliably to other cloud environments such as GCP or Azure.
Read full review
Return on Investment
  • 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
Read full review
  • We have a few small projects with different developers and Codeship shows everyone clearly, if something work, or if it doesn't.
  • In one small project with a team of three developers, we have configured two builds and it takes 2-5 minutes for everyone on the team to push changes to an infrastructure handling a little over 3M users.
Read full review
ScreenShots

CloudBees Codeship Screenshots

Screenshot of Get an overview of all your builds, identify failed builds easily and take action right from the dashboard.Screenshot of Information for a single build, inspect log files for each step and notice at a glance which pipeline and step are failing.Screenshot of Simply enter your setup and test commands, or choose from templates available for a wide range of stacks.Screenshot of Deploy to various web services without having to worry about the process. Simply choose your deployment target, which branch you want to deploy and off you go.Screenshot of We take care of all the complicated parts of the deployment. You simply fill in the blanks and you're all set.Screenshot of Get notifications for your builds on a multitude of services. You can also ping your own services to implement custom logic.