Keep new builds in same clone directory
ajsharp opened this issue · 3 comments
I noticed that bigtuna creates a new directory for each build, and a fresh clone at that. Is there a reason it doesn't just pull in the lastest changes for whatever branch it's on, via git pull? Having different directories forces you to automate things like copying config files over and the like for every build, which is not the worst thing in the world, but seems unnecessary. Thanks.
Not sure if this is a good thing or not - I'd rather have it start clean and have my build steps be able to handle setting up the project regardless of its state (i.e. make my build steps idempotent). Certainly for a VCS like git, we could use "git clean" to assure that the repository is reset to its original state, but that wouldn't solve your config files problem - git clean (with the options I'm thinking of) would clear out your config files.
FYI, this is similar to #39.
Cool, thanks for the response. I completely understand what you're saying here, and I think it's more of a design decision in a CI system rather than a "good" or a "bad" thing to be doing. Either way, I'm good with this approach.