CloudBees Codeship vs. GoCD

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
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
GoCD
Score 8.0 out of 10
N/A
GoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.N/A
Pricing
CloudBees CodeshipGoCD
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CloudBees CodeshipGoCD
Free Trial
YesNo
Free/Freemium Version
YesNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CloudBees CodeshipGoCD
Considered Both Products
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 …
GoCD
Chose GoCD
GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to …
Chose GoCD
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The …
Best Alternatives
CloudBees CodeshipGoCD
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
CloudBees CodeshipGoCD
Likelihood to Recommend
9.0
(0 ratings)
9.0
(0 ratings)
User Testimonials
CloudBees CodeshipGoCD
Likelihood to Recommend
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
GoCD is easy to set up. So if you just want to get some pipelines up & running quickly, & they're quite stable, or you can have many pipelines for different needs then GoCD is great. Still, if you only want to have a few pipelines, but with the flexibility to run them with different parameters dynamically, then Jenkins is better.
Read full review
Pros
  • Easy and fast deployment
  • A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
  • Getting tests to run is fast and easy
Read full review
  • Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
  • The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
  • Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
Read full review
Cons
  • 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
  • UI can be improved
  • Location for settings can be re-arranged
  • API for setting up pipeline
Read full review
Alternatives Considered
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
I prefer using GoCD compared to Jenkins. The UI makes sense, I like the simplicity to hit the 'Play' button for a straightforward deployment of the 'Play +' if you need to override some settings when deploying whereas Jenkins, you have the whole page for each pipeline. The environment makes sense but can often confuse the user while GoCD simply has a drop-down to select your environment.
Read full review
Return on Investment
  • 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
  • ROI has been good since it's open source
  • Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
  • More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
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.