3 ms·
Why worry about what is on master, if you save your build artifacts. so that if you need to go back to a the previous behavior, just redeploy the previous produ
by platz 11y ago
Why worry about what is on master, if you save your build artifacts. so that if you need to go back to a the previous behavior, just redeploy the previous productuon build output
- p4lindromica 11y agoYou code is written in golang. You've been compiling it with golang 1.5.1. Then golang 1.5.3 comes out with critical security fixes for their TLS code. That is why you care what is on master: because you need to rebuild if your runtime changes.
- joneholland 11y agoWe deploy straight from master, but tag each build. If you need to rebuild a specific version, it's as easy as checking out the tag.
- softawre 11y agoThis feels like the correct strategy to me (and it's what we do too). Deploying many branches to production seems like a nightmare at any scale.
- Too 11y agoDebugging. Some bug only happens on customer X's installation. You need to know which version customer X is running so you can reproduce the bug in house and know what other impact it might have had.