Why we use Codeship
April 10, 2018

Why we use Codeship

Kariem Hussein | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Codeship

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


More Reviews of CloudBees Codeship