CircleCI vs. CloudBees Codeship

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CircleCI
Score 8.3 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.
$0
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
Free
$0
per month
Performance
$30
per month
Server
$35
per month
Scale
Custom Pricing
No answers on this topic
Offerings
Pricing Offerings
CircleCICloudBees Codeship
Free Trial
NoYes
Free/Freemium Version
NoYes
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
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
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
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, Codesh…
CloudBees Codeship
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 …
Top Pros
Top Cons
Best Alternatives
CircleCICloudBees Codeship
Small Businesses
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
Enterprises
GitLab
GitLab
Score 8.9 out of 10
GitLab
GitLab
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
CircleCICloudBees Codeship
Likelihood to Recommend
8.0
(26 ratings)
9.0
(6 ratings)
Usability
10.0
(1 ratings)
-
(0 ratings)
Performance
7.8
(3 ratings)
-
(0 ratings)
Support Rating
6.9
(6 ratings)
-
(0 ratings)
User Testimonials
CircleCICloudBees Codeship
Likelihood to Recommend
CircleCI
CircleCI is perfect for a CI/CD pipeline for an app using a standard build process. It'll take more work for a complex build process, but should still be up to the task unless you need a lot of integrations with other tools. If you have a big team and can spare someone to focus full time on just the CI/CD tools, maybe something like Jenkins is better, but if you're just looking to get your app built, tested, and delivered without a huge amount of effort, CircleCI is probably your preferred tool.
Read full review
CloudBees
Codeship is extremely well suited for projects that are version controlled on public hosting such as Github or Bitbucket, and for situations where you need to pick up code from these systems and deploy it to different cloud environments. For example, we had two projects for the same client that were hosted on Github and needed to be deployed to AWS and Heroku. The native CI/CD tools of these cloud environments could not provide a holistic solution to deploy to both environments the way Codeship did.
Read full review
Pros
CircleCI
  • Multiple builds can be run at the same time in parallel.
  • The CircleCI web interface (UI/UX) is very easy to understand and use.
  • Easy Configuration to learn and use. Just a single configuration YAML file.
  • Many integrations. We use the GItHub, Slack, and DataDog integrations.
Read full review
CloudBees
  • Codeship provides a set of tools for quickly creating and building our deployment artifacts and push them to the designated servers.
  • Codeship's hooks allows our developers to simply push tags from our git repositories to initiate a deployment of code to a server. No one outside of the devops team needs any expertise to get our code packages delivered.
  • Codeship allows us to tie in behat and unit tests easily to prevent delivery of buggy code.
Read full review
Cons
CircleCI
  • The "phases" their config file uses to separate out options seem very arbitrary and are not very helpful for organizing your config file
  • No way that I know of to configure which version of MongoDB you use. You have to write your own shell script to download and start MongoDB if you want a specific version.
  • Hard to access build artifacts in the UI
Read full review
CloudBees
  • I would like to see a little bit more than the green/red status. If there are tests, it would be good to see how many have failed on a red build.
  • To improve build times (and reduce feedback times), it would be good to see how long build, tests, and deployment take over time. An overview like that could very easily point to potential areas of improvement. I think Codeship users do not want to bother with the build process, but, if there is anything to improve and increase productivity it's very unlikely that users wouldn't want to do this.
Read full review
Usability
CircleCI
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
CloudBees
No answers on this topic
Performance
CircleCI
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
CloudBees
No answers on this topic
Support Rating
CircleCI
Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review
CloudBees
No answers on this topic
Alternatives Considered
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 we switched.
Read full review
CloudBees
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.
Read full review
Return on Investment
CircleCI
  • It has eased the burden of standardizing our testing and deployment, making onboarding new developers much faster, and having to fix deployment mistakes much less often.
  • It allows us to focus our process around the GitHub workflow, ignoring the details of whatever environment the thing we're working on is actually hosted in. This saves us time.
Read full review
CloudBees
  • Having the code tested thoroughly. While it's obviously a part of the job that still requires the developer to sit down and to actually have some decent and thorough tests implemented, by using codeship we were able to guarantee 100% that our code was being tested each and every time it got commited and pushed onto our repositories. Leading to a faster, shorter and sure implementation iterative cycle.
  • Fewer 'man in the middle' processes which required more steps and people involved just to get the code shipped onto our deployment servers.
  • Almost inexistent learning curve. Codeship is simple to use and very intuitive. Nobody in our development department had a hard time figuring out how to have it properly configured for each new project created there.
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.