|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
So Build definition's delete before loading is what you are doing now if I understand your forum question. Basically deleting the entire sandbox directory and then loading. I got from your forum post that this is too heavy.
Sounds to me like you want the sandbox to hold exclusively just the contents of the workspace being built (i.e. some other build step can't populate the sandbox directory with other contents like scripts, tools, etc.). As well when the load takes place, it replaces the contents on disk with whats in the repository. If there are files/folders/links that are ignored & not in the repository, they should be deleted from disk (often build artifacts like bin directory, .class files etc. are marked as ignored and not in the repo, so they should be deleted to ensure a full build). Currently our load operation will leave those ignored items on disk.
Just want to be sure I understand your definition of "pristine".