Likelihood to Recommend 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 It is best suited for an on-premise cloud solution where customer can shift their entire production environment. Also, the customer has a preference for a Homogenous Infrastructure Environment where budget is not a challenge. It is not at all suited for a Heterogenous Environment, e.g., a Public cloud where integration becomes a huge issue, also in SMB sections where budget is challenging.
Read full review 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. Read full review Cloud enabled Solution. Support Container based Apps. Cost efficient. Supports both Public and Private Environments. Read full review 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. Read full review The Deployment is complex. Recommended Number of Physical Nodes is three or more; with less than 3 Nodes, it becomes difficult to install V-SAN. Need for better integration. If we go on the public cloud, it is a huge challenge while integrate with an open source platform. Cost can be marginally reduced. SMB segments still prefer a separate license instead of VCF, or they postpone their purchase plans. Read full review Alternatives Considered 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 Although the public Cloud Model follows Opex Costing Model, it actually leads to very high costs also, the infra model in my organization is not suited for a Public Cloud Model. Hence We decided on an On-Premise Model, and the best suited was VMware Cloud Foundation, which is a complete Software-Defined Scale-Out Architecture. I also prefer a Homogenous environment; i.e, support and services from a Single OEM, so that I Can get faster resolutions to my tickets raised.
Read full review 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. Read full review My organization has a size of 1300+ employees, using multiple applications and an exchange mail server that is hosted on On-Premise Cloud, hence scalability has not been a challenge. Having hosted my Production environment and Mail exchange Server on VCF, there has been optimum resource utilization with very little scope downtime. Hence have been able to save a lot of funds on Hardware resources. Due to the size of my organization and due the data load, I have been able to save on Resource Utilization and Organization Funds Read full review ScreenShots CloudBees Codeship Screenshots