4 ms·
Automated Continuous Deployment at Heroku
- mfer 7y agoI like posts like this. They share where they were, why they changed, how they did it, and were honest about the time it's taken to get there.
- carlosdp 7y ago> Incident. This check fails if there’s a relevant incident open on the Heroku status site. Curious, what's a relevant incident in this context? (given you are using the PaaS you are developing) Like what if you are deploying an emergency fix to a service that is in the middle of an incident? > GitHub. The deployer will only promote changes which are present on the master branch. I've always preferred the pattern Github uses internally of deploying feature branches and merging when deployment succeeds. Otherwise, there's weird behavior that requires manual intervention to fix in some edge cases, since deployments can fail, and it ends up cluttering the git log with operational noise.
- anbotero 7y agoWhere is the GitHub part documented? What does "internally" mean? Like a shadow deployment strategy? Thanks!
- crymer11 7y agohttps://github.blog/2015-06-02-deploying-branches-to-github-com/ https://github.blog/2015-06-02-deploying-branches-to-github-...
- AdamN 7y ago> what's a relevant incident in this context? The typical pattern should be to block the promotion but allow the operator to override the block manually. The automated process fails safe (not promoting).