Hello Denis, It's hard to say for sure, just from that, but these are some behaviors I believe are true:
1. If there are files left behind *inside* a git repository checked out folder, then it will run a `git clean`. No way to stop that. It will need to make sure every job run starts with a clean slate. 2. If you haven't asked it to clean working directory, then it won't delete and re-clone. So, timestamps of unmodified files should be the same (depending on how git handles them). 3. If you're able to *use* the checked out files, but have your workspace (which gets "dirty") in a location outside the repository checkout location, then GoCD shouldn't touch those directories outside the repo location. I mean: Suppose you configure the material to check out into folder "src1" and then run your build from the parent dir of "src1", then `git clean` should run only within "src1", leaving your workspace in the parent untouched. It isn't recommended to depend on something left behind, as I said, but that's one way that might work in this case, assuming it works for your build system to work that way. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/m2363x8vrh.fsf%40arvindsv.com.
