forums:

I agree. Notice this option ("Clean working directory after each build") is not related to Mercurial Repository alone, but it's a bamboo global feature, like "Force Clean Build". Question: what did you expect this option will do (regarding Mercurial plans)?

I expected it just to delete the working directory files (and not .hg/) and then pull/update sources back to the working directory using the existing repository in the Working directory. Force Clean Build on the other hand would force new clone of the repository in case it has changed completely and cannot be cached in the working directory anymore. This way the "clean working directory after each build" wouldn't need to transfer the whole repository again, but just recent changesets with pull and update. Of course in our case it's probably not that big deal as the clones are local and Mercurial uses hardlinks. I guess with remote agents it's using the local remote agent cache as well.

Do we agree/disagree with customer point of view? If so, is this possible? Probably the same problem will arise in Git Plugin...