Likelihood to Recommend It is good tool if you are doing continuous improvements in your code and you wish it goes live whenever you push code to
GitHub . So integrating Azure Pipeline, it automatically does CI/CD in the background once you push code/merge code and it is live in few minutes. It also does some automated tests if you have wrote scripts
Read full review 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 Integration with SonarQube Integration with Azure DevOps Integration with GitHub Read full review 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 The errors which we got sometimes are not clearly enough. There are some let's say hidden options, they could be more visible When the process is running we have to remember about manually refreshing to see the current status because it doesn't work automatically Read full review 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 Alternatives Considered We have used the
GitHub CI/CD. Earlier we were using the Azure Pipelines but after
GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live.
GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient
Read full review 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 we have had outages from Azure in the past Read full review 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