3 ms·
Serious question: How/where do you check in your binary builds and debug symbols if you use git? I've read it's not great at some not-so-large project size. I
by DougN7 13y ago
Serious question: How/where do you check in your binary builds and debug symbols if you use git? I've read it's not great at some not-so-large project size. I'm using SVN on a micro-sized team with binaries from all released builds safely checked in (which means the repository is probably 100GB-ish in size), and it works great. [and to head off the argument - rebuilding from source is not an option when you have to diagnose a customer crash when they are using a 3 year old build of the software - you'd have to archive a build machine to even have a chance...]
- fournm 13y agoWhy are your binary builds living in version control?
- chris_wot 13y agoThat is the right question!
- DougN7 13y agoWhy wouldn't they? Conveniently and safely in the same location as the code they were built with. Tagged the same way. Having a separate repository is just inviting trouble down the road, no?
- fournm 13y agoBecause they're binary files, used entirely for archival purposes. They shouldn't be changing, they shouldn't have "versions" that are anything to deal with meaningfully as far as your repository is concerned. They should be in flat storage somewhere, with some directory or file name scheme that makes sense based on your version numbers / builds / what have you. Backed up, (ideally) with hashes that verify that they're the same file they once were.