Over a million developers have joined DZone.

Snap CI Is Shutting Down

DZone's Guide to

Snap CI Is Shutting Down

On February 6, 2017, Snap CI announced that its last day will be August 1. As you flock to find a replacement, it's helpful to see a comparison of different platforms.

· DevOps Zone
Free Resource

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

This is really sad news for the DevOps industry. Snap CI is going away, and we can see the whole DevOps industry trying to rethink their processes. My Twitter feed was all filled with #SnapCI posts.

What Went Wrong?

Snap CI is backed up by ThoughtWorks, who are the leaders in technology consultation. According to them, they failed to create an impact on their target market through Snap CI. They'll be continuing their focus with consultation and another Continuous Delivery product, Go CD. Now, Snap CI users have to make a big decision of switching to other platforms and tools. How's that going to be? 

Today, I would like to provide a brief comparison of Snap CI and various CI/CD organizations:

Snap CI in comparison with Codeship:

Image title

Snap CI in comparison with Shippable:

Image title

Snap CI in comparison with Circle CI:

Image title

Codeship, Circle CI, and Shippable have their own benefits and advantages. Ultimately, it is the customer who is going to gauge and rate you. 

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

snap ci ,continuous integration ,continuous delivery ,devops

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}