TrustRadius: an HG Insights company

Codeship (discontinued)

Score9 out of 10

10 Reviews and Ratings

What is Codeship (discontinued)?

Codeship was a hosted Continuous Integration and Continuous Delivery (CI/CD) platform designed to automate software building, testing, and deployment workflows. Acquired by enterprise software delivery provider CloudBees in February 2018, the cloud-based service integrated with source code repositories—including GitHub, GitLab, and Bitbucket—to execute automated test suites and deploy application updates to hosting environments such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. CloudBees officially discontinued and sunsetted the CloudBees Codeship product on January 31, 2026, ending all technical support and service operations. The listing is retained as a legacy record to preserve historical user reviews and research data.

Read more details.

Categories & Use Cases

Who Buys & Uses Codeship (discontinued)

Codeship (discontinued) Reviews

What users are saying about Codeship (discontinued).
View all Codeship (discontinued) reviews

Codeship is a handy little cross-platform CI/CD tool

Incentivized
Ramindu DeshapriyaView profile
Lead Consultant - Technology in Information Technology at Virtusa (10,001+ employees)

Pros

  • Inter-cloud deployments
  • Integration with different version control providers
  • Easy-to-use UI
  • Quick configuration

Cons

  • Better capabilities for deploying CI/CD pipelines as code
  • Better support for enterprise-grade customers
  • Better logical grouping capability for projects

Most Important Features

  • Inter-cloud capability
  • Integration with different version control systems
  • Ability to deploy same codebase to multiple cloud providers
  • Managed service on the cloud

Return on Investment

  • 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%

Alternatives Considered

Jenkins and AWS CodePipeline

Other Software Used

Tableau Server, AWS CodeCommit, Jenkins

Review of Codeship from the perspective of overall reliability in a small development team

Incentivized
Alex LadaView profile
Senior Web Developer in Information Technology at Liberty Concepts (11-50 employees)

Pros

  • 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.

Cons

  • 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.

Return on Investment

  • Faster code pushes with less headaches has led to better efficiency as well as reduced frustration within the development team.

Alternatives Considered

Acquia Platform, Travis CI and Gitlab

Other Software Used

Drupal, WordPress, Acquia Platform

Why we use Codeship

Kariem HusseinView profile
CTO in Information Technology at Trayn (11-50 employees)

Pros

  • 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.

Cons

  • 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.

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.

Alternatives Considered

CircleCI and Bitbucket

Life is easer with Codeship!

Incentivized
Maxim MilovanovView profile
Senior Software Engineer in Information Technology at EPAM Systems (10,001+ employees)

Pros

  • Easy and fast deployment
  • A lot of tool integrations (Slack, GitHub, Bitbucket, GitLab)
  • Getting tests to run is fast and easy

Cons

  • 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

Return on Investment

  • I have only positive experiences of using Codeship for my projects.

Other Software Used

Jenkins, Visual Studio IDE

Simple and Intuitive Tool for Continuous Delivery

Incentivized
Claudio Fernando MacielView profile
Sr. Software Developer in Research & Development at CONSLOG - Construction Software (11-50 employees)

Pros

  • 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.

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.

Return on Investment

  • 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.

Alternatives Considered

Bitbucket, Gitlab and Jenkins

Codeship (discontinued) Alternatives

Products similar to Codeship (discontinued) that may also meet your needs.
View all Codeship (discontinued) alternatives
Travis CI
CompareLearn more
CircleCI
CompareLearn more
Codefresh
CompareLearn more