Tuesday 13 August 2013

Heroku pipelines

After an incident this morning when I did a
 git push staging  
instead of a
 git push development  
I decided it was time to look in more depth at the heroku pipelines lab feature, and after a quick look I am very pleased I did. It allows me to just have one heroku remote which I have at the bottom of the pipeline, with staging and (eventually) production further downstream. When we are ready to release to the client for user acceptance testing then we can simply call:
 heroku pipeline:promote  
which sends the development version to staging. No need to retain separate development and staging branches in git now, we can just have the one which we promote.

No comments:

Post a Comment