4 ms·
It's fairly common and works pretty well if you have a good test coverage and monitoring in place. GitHub is a documented example (and I happen to deploy branc
by thibaut_barrere 14y ago
It's fairly common and works pretty well if you have a good test coverage and monitoring in place.
GitHub is a documented example (and I happen to deploy branches daily too :-):
https://github.com/blog/1241-deploying-at-github https://github.com/blog/1241-deploying-at-github
- amatix 14y agoI've read several times about github's use of branches in deployment/production. How are DB schema/data migrations handled (and kept safe/sane)? Presumably hubot and friends prevent Bad Things from happening by deploying a branch that doesn't match the current DB state?
- wahnfrieden 14y agoI didn't say one way is strictly better. There are tradeoffs to consider and that's all that really matters. I'm not sure it occurred to the OP that there are benefits to forgoing remote branches, so I mentioned it.
- thibaut_barrere 14y agoMy bad, I read "Consider not doing that." as a more strict recommendation!
- wahnfrieden 14y agoSorry, I was too blunt :)