Wow, this is the exact issue I was encountering today with CodeShip. Not exactly...

smt88 · on Jan 14, 2015

Not sure what stack you're on, but I've done exactly what you're describing with Beanstalk (now a standalone product at http://dploy.io) for years.

mattkrea · on Jan 14, 2015

Thanks for the tip--looks interesting. The only addition that CodeShip provides is also running my tests (may have just missed reading that on dploy).

Stack is Node.js, RabbitMQ, MySQL, Redis, and a little bit of Go running on top of Elastic Beanstalk with Docker.

smt88 · on Jan 14, 2015

Because you're using EB and Docker, I'm not sure Dploy is right for you, but it's worth looking into.

I believe you can run arbitrary commands after you commit to a particular branch, which would allow you to run your tests.

If any of your commands exit with a failure code, the deploy is halted and you're notified via email.

(You can also set the deployments to be manual, allowing you to commit to e.g. "release" without anything happening until you want it to.)