|
||||||||
|
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/d/optout.
Wipe out repository and force clone is a last-ditch technique to handle those cases where the repository is no longer usable. It should generally only be needed for recovery, not for everyday operation. Wipe out workspace is the same type of operation, and I use it with about the same frequency to recover from some form of repository damage.
I need to use that setting at times when I'm testing bug reports in the git plugin or the git client plugin because a repository was only partially cloned, or because a build operation damaged the contents of the git repository.
If you're using Unix based (Linux, FreeBSD, OpenBSD, Solaris, HP-UX, AIX, etc.) slave agents, you could consider reducing the disc space and the clone time of your large repository by using a "reference repository" on each slave machine. A reference repository is a bare repository kept at a known location on the slave machine, referenced by Jenkins jobs which need the contents of that repository. The Jenkins job repository then include pointers into the bare repository instead of copying the content from the central repository. I've found it saves significant time on my large repositories.