|
||||||||
|
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. I'll install it.
It seems to happen only in jobs that have removing old builds configured, doing it in the builds directory is actually rather non-trivial.
I also have a job where I really do care about the workspace (it does not have any artifacts, even). I see now it is a different problem, but for me it is a bigger problem; I have to somehow tell it not to ever delete the workspace (I can't easily do the work in random directory instead, because it is not a shell script but uses Jenkins builder).