CloudBees Codeship

CloudBees Codeship

Score 9.0 out of 10
CloudBees Codeship


What is CloudBees Codeship?

Codeship from CloudBees is a build automation platform from the Austrian company of the same name.
Read more

Recent Reviews

Read all reviews

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of CloudBees Codeship, and make your voice heard!

Return to navigation


View all pricing

What is CloudBees Codeship?

Codeship from CloudBees is a build automation platform from the Austrian company of the same name.

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visit


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

1 person want pricing too

Alternatives Pricing

What is CircleCI?

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…

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change…

Return to navigation

Product Demos

An Introduction to Codeship Basic
An Introduction to Codeship Pro
Return to navigation

Product Details

What is CloudBees Codeship?

CloudBees Codeship is a hosted Continuous Integration and Delivery platform. It sits between a source code repository (e.g. GitHub, GitLab or Bitbucket) and the hosting environment (e.g. Amazon Web Services) and automatically tests and deploys every change in your platform. The product aims to allow Engineering teams to focus on developing better applications instead of wasting time on maintaining a cumbersome CI server. According to the vendor, Codeship scales with the user's needs, and allows users to speed up test suites and enables developers to ship better code faster.

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.

CloudBees Codeship Videos

An Introduction to Codeship Basic
An Introduction to Codeship Pro

CloudBees Codeship Competitors

CloudBees Codeship Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported LanguagesEnglish

Frequently Asked Questions

Codeship from CloudBees is a build automation platform from the Austrian company of the same name.

CircleCI, Travis CI, and Codefresh are common alternatives for CloudBees Codeship.

The most common users of CloudBees Codeship are from Small Businesses (1-50 employees).
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings



(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Ramindu Deshapriya | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We use Codeship to manage our deployment and continuous integration pipelines across different environments, version control hosts, and technology stacks. We have implemented CI/CD workflows for various clients using Codeship, and its versatility in being able to handle different cloud environments such as AWS, Azure, GCP, and even plain old on-prem servers has made it an invaluable tool that can be applied to all requirements. The fact that it is a managed service on the cloud removes the headache of having to maintain our own instance of it.
  • Inter-cloud deployments
  • Integration with different version control providers
  • Easy-to-use UI
  • Quick configuration
  • Better capabilities for deploying CI/CD pipelines as code
  • Better support for enterprise-grade customers
  • Better logical grouping capability for projects
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.
  • Inter-cloud capability
  • Integration with different version control systems
  • Ability to deploy same codebase to multiple cloud providers
  • Managed service on the cloud
  • Reduced CI/CD server set up and maintenance time by 100%
  • Speeded up creation of deployment pipelines by 15%
  • Decreased build issue debugging time by 5%
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.
Alex Lada | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
At our company we use Codeship as part of our suite of devops tools to deliver web sites/apps to our various cloud servers. It has helped significantly streamline and speed up our deployment process to any of our clients' servers for development, staging, and actual production servers.
  • 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.
  • The only real gripe I have with Codeship is with regards to its single sign-on experience within the website. Occasionally I accidentally try to sign in with my GitHub account instead of my Bitbucket account. By the time I realize the error, it is stuck in a transition state that it does not let me "sign out of". This is fixed by clearing cookies, but it would be nice to see some sort of sign out option before you are fully signed in.
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.
  • Faster code pushes with less headaches has led to better efficiency as well as reduced frustration within the development team.
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, but it has been by far the most hands off tool we have used to deliver code.
April 10, 2018

Why we use Codeship

Kariem Hussein | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Codeship for most new projects, if we want to have a quick process to deploy from our version control system to staging or production environments. Codeship setup is quick and part of our common project bootstrap process: you can say that a project is correctly setup, if we can push code and have an updated infrastructure a few minutes later.
  • Quick setup for continuous integration: push to a specific branch and run deployment scripts to see updates on the corresponding environment
  • We can quickly see if there is something wrong: whenever we make changes, Codeship runs the whole build and then tests the code before deploying to production. The default setting is to run build and test on all branches, so there is usually no feature branch with a red build that we are not aware of
  • Deployment scripts are very easy to configure and with the limited (but powerful) setup options, we usually have a clear process that describes the deployment. This way everything is clear, even for engineers new to the project.
  • 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.
If your project is hosted on GitHub/GitLab/Bitbucket or something similar and you want to have a quick setup with CI, you should definitely use Codeship. The setup is quick and builds are running very quickly
  • 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.
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 everyone can run the scripts locally.

A declarative build configuration (as in CircleCI) is also possible with Pipeline builds, but for now, we prefer the simple and clear scripted solution provided by Codeship.
Maxim Milovanov | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
I'm using Codeship for continuous integration and deployment of my personal front end and node projects. Codeship integrates great with Bitbucket and GitHub. It's saves a lot of time with deploys and tests.
  • Easy and fast deployment
  • A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
  • Getting tests to run is fast and easy
  • Copeship is an external service, I can't install it inside our company's private network
  • I can't use it for free for my private repos
  • No open source support
Codeship is great for deploying open source personal projects, but it can't be used for internal projects. It's really hard to convince a manager to use an external tool.
  • I have only positive experiences of using Codeship for my projects.
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.
Claudio Fernando Maciel | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Codeship is used for simple CI and CD strategies for our small research and development projects. Whenever a new research project is 'bootstrapped' we instantly launch a git repository along with a codeship instance for the project thereof. There, we create our strategies for making sure our acceptance and functional tests are run before the code gets shipped onto production or onto a staging server. It's solely used by our development department, specifically by those involved in the research and development tasks.
  • Build Automation: It's no longer necessary to run many other tools along with the git push command.
  • Continuous Integration: We were finally able to achieve K.I.S.S. [keep it simple, stupid] methodology at our development environment.
  • Continuous Deployment: If everything looks good, it no longer needs to be sitting there, waiting for some other bureaucratic task sequence to be run in order to get deployed.
  • 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.
It is seemingly easy to use and has tons of different integrations. It also provides me a neat "trick" to skip the integration whenever it's necessary; simply by using a --skip-ci comment along with my git commits. It's easy to track the bug and promptly have it fixed, so it has my sped my development cycle a great deal. The overall UX is not bad, but it certainly needs some improvement. It needs to have the most repetitive tasks more 'hands on' than it is actually being displayed. Although I find it to be a very beautiful UX, it's a little hidden.
  • 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.
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 integration and continuous delivery. Codeship presented itself as a simple, straight-to-business and inexpensive way of achieving CI and CD at our company.
Return to navigation