|
||||||||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Workspaces, where Jenkins stores temporary build data, are supposed to be managed by Jenkins as much as possible (it's not an 'advanced project option' hidden by default by accident!). Deletion of workspace contents is trivial, and cleanup of leftover state is a common occurrence in any build, ingrained in Jenkins and plugins.
For your specific use case (which seems very unusual), it'd likely be best to not use a custom workspace, but just cd or xcopy out of that directory to accomplish your specific goals.
Maybe you're just using the wrong tool for the job: Something like Windows Scheduled Tasks might be better suited for what you're trying to accomplish
If you disagree with this point of view, consider emailing the jenkinsci-users list asking for advice in your specific situation. Issues in the tracker will reach a significant audience (and this is also the wrong place to discuss this).