|
||||||||
|
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.
That's true, for the 'delete' case. However, it's a lot easier to universally say "Hey, if you have a job, mark it to 'git clean' at the end of the job if the job is successful". That takes care of most of the build scenarios where the content of the job is much larger than the repo.
It looks like I could rig up something with: https://wiki.jenkins-ci.org/display/JENKINS/Global+Post+Script+Plugin
Just seems like this would be much easier to have here since it's already controlling that cleanup process during init, and it's already aware of each of the clone paths in the job.