Codeship from CloudBees is a build automation platform from the Austrian company of the same name.
N/A
Codefresh
Score 7.0 out of 10
N/A
Codefresh is a continuous integration/delivery and automation platform for Kubernetes that allows users to build, test, deploy and gather feedback on apps, from the company of the same name in Codefresh.
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.
While deploying docker images on kubernetes pods I must say Codefresh helped me a lot. It has made my work easy as an Automation tool. I can setup a simple pipelines to automate my build for kubernetes. but for more complex pipelines Codefresh need some improvement
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.
Continuous Integration and Continuous Development. we can setup jobs that automatically triggered when there is any changes in code and starts building up the build images automatically and then pushing images to Container Registry
We can involve Version control system like github, bitbucket, gitlab etc for integration of Codefresh with our code stored in these Version control systems.
On the failure of any jobs/pipeline Codefresh can also send Notification on our email.
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.
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.
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.
