|
||||||||
|
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.
Thanks for the clarification of the location. I've marked that text with "strike-through" because I think removing "Wipe out workspace" would be a break in backwards compatibility and would remove one of the ways people recover from problems. There are so many ways to need a fresh clone of a git repository that I don't see much hope of the plugin covering all the use cases I've already experienced where I had to wipe the workspace.
The subversion plugin has the equivalent of "Wipe out workspace", so I think there is a reasonable precedent to retain that option.