Codeship vs Snap CI: What are the differences?
Developers describe Codeship as "A Continuous Integration Platform in the cloud". Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need. On the other hand, Snap CI is detailed as "Build, test, and deploy software faster with Snap's continuous integration and deployment tool". Snap CI is a cloud-based continuous integration & continuous deployment tool with powerful deployment pipelines. Integrates seamlessly with GitHub and provides fast feedback so you can deploy with ease.
Codeship and Snap CI belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Codeship are:
- Run you automated tests | Easily set up Codeship with Github or Bitbucket and trigger your automated tests with a simple push to your repository.
- 100 builds & 5 private projects free per month.
- Free for OSS.
On the other hand, Snap CI provides the following key features:
- Deployment Options - Heroku, AWS
- System Libraries - Your build runs on a RedHat 6-compatible system with commonly required libraries
- Customization Options - In addition to all that we support out of the box, we offer you the chance to customize your build extensively.
"Simple deployments" is the top reason why over 214 developers like Codeship, while over 13 developers mention "Github integration" as the leading cause for choosing Snap CI.
Product Hunt, TravelPerk, and Swat.io are some of the popular companies that use Codeship, whereas Snap CI is used by ThoughtWorks, Hazeorid, and Firecracker. Codeship has a broader approval, being mentioned in 277 company stacks & 82 developers stacks; compared to Snap CI, which is listed in 7 company stacks and 3 developer stacks.
What is Codeship?
What is Snap CI?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Snap CI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Working for a web agency, I have access to many premium services for all parts of the development process which leads to two things when it comes to working on my personal projects at home.
1: I am more fussy about the quality of tools and services that I use than I was before I went from just messing around with programming to having a developer job.
2: I really don't want to pay a single fee or any kind of subscription to services as after using them all day at work I find it hard to justify personally paying a premium to use them for a bit of time at home after work.
However with Code ship neither of these things caused any issues as I found it to be very high quality and free.
On the subject of it being free, I know there are other CI solutions that are free however if you wish to use it with a private repository then unless you already have private Github repos then the fact that Code Ship integrates with Bitbucket can be extremely convenient as it means you can set up your personal projects with free private repository and a free CI / testing solution for absolutely free.
Overall Codeship has really impressed me in every way from its pricing to its clean and simple UI and its ease of use.
Setting up continuous integration is complex and time consuming. I've used Codeship for 1 year now and I would never go back to previous systems such as self hosted Jenkins for any kind of web applications. The ability to change developer access on a per repository basis with the click of a button is very helpful and integration with all our services such as Github and Heroku make testing and deployment happen in the background so we can concentrate on our application and not worry about what state the live code is in. We also find the Slack integration (and flowdock before that) to be a great way to share the current code status with the whole team without getting spammed with emails on each commit and build state change while testing prototype branches or working on pull-requests.
Like most developers I'd love it if my deployment processes were always the same for every project so I never had to think about deployment. However, that's probably never going to happen unless we stop having clients. Codeship allows me to organize all of my deployments into one place and set them up once so that I don't have to remember the process for every nuance of every client.
Whether it's deploying a Drupal or Wordpress site to a private server, a Meteor.js app to Modulus, or just about anything else Codeship gives me the flexibility of writing my own shell scripts for custom jobs (private server) but also one-click solutions for common problems (deployment to Modulus).
Highly recommend them!
It's not easy to differentiate a CI/CD service because integrations matter so much more than the service itself. Didn't even need to read any docs, it just works exactly as you expect it to.
- Pipelines for running tests in parallel (freemium).
- Easiest setup of any CI service I've tried.
- Mandatory build status image service.
- Test runners are alright, but not that powerful. Py.test can run tests in parallel on its own, but enabling that feature doesn't seem to speed up Codeship runs.
- Doesn't detect tox environments, so you have to specify one environment per pipeline manually.
I spent half a day grepping CodeShip and now I have a sweet deployment process for WP sites. After a month of wrestling with Bamboo I decided to give CodeShip a try thanks to an article by CodeShip's Roman Kuba about deploying WP sites
I am now killin' WP development with my CodeShip + WPEngine setup. This is also making WP development/deployment fun for the first time. CodeShip f*cking rocks.
We use this as a CI tool when working on our API and related tools. The setup is relatively painless and it hooks directly into our Github repo's to provide reports and feedback.
Runs a full test suite whenever we push changes to master and if everything is good, automatically deploys our changes to production.