Heroku Continuous Deployment

Using Solano CI’s post-build hook, you can configure powerful continuous deployment to Heroku, including running migrations or other tasks.

Until this documentation page gets fleshed out, read on for notes and a link to a blog post walking through the setup.

Post-Build Hooks & Heroku

For smooth continuous integration between your app, Solano CI and heroku, you will need to turn off the git push URL in Solano CI when using a post-build hook.

Heroku Authentication through Solano CI

When using a post-build hook with heroku, you will need to pass your heroku login information in Solano CI. There a few ways to pass your login credentials through Solano CI to your heroku account, depending on your security needs.

For further information: http://blog.solanolabs.com/2012/05/09/heroku-continuous-deployment/ Setting Environment Variables.


Solano CI modifies or adds certain files to ruby/rails repos to better collect results from our parallel test runners (typically config/boot.rb and various config/*.yml files). Before deploying your code, you may want to revert these changes with a command like git reset --hard $TDDIUM_CURRENT_COMMIT in a post_build setup hook.