Hey- So one thing that has got me about heroku is that there isn't necessarily a good link between the git repo and heroku releases. By this I mean that it isn't entirely obvious what is deployed and running at the moment. There are two current tools we have: * the heroku remote in the git repo * heroku releases
This gives me the current release and what is working right now, but nothing more. If I deploy something broken, there isn't a clear way to find what I'd be rolling back to. The hashes displayed in heroku releases are of the compiled slugs. I have gone through a few back and forths as to what would be a good way to fill this gap. I realized that you'd really need two different scripts since releases are created in multiple places, one in the heroku cli and one in git. The config/addon changes trigger a new release to be created, but I think that those changes are well documented in heroku releases. It was the git-push triggered releases that I wanted to track. This led me to write: https://github.com/deignacio/gthr What I'm wondering from you guys is: * is there any other way in heroku that I can get the information I'm scraping so that I'm not just scraping stderr of git push? * am I thinking about this problem in the right way that this solution seems okay? * are there any other precedents that I didn't find in my sanity check google search? * assuming that the previous questions are positive, can anyone think of any other things they'd want? Thanks for your input Dave -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
