|
||||||||
|
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.
I assume you'd have noticed Perforce deleting those files, even if it's a child process of Jenkins, so that's out.
I'm out of ideas. I think it would be interesting if you upgraded Jenkins and enabled the cleanup thread again, but I'd understand if you didn't want to do that on the production instance (although I suggest upgrading to a recent Jenkins LTS release anyway).
Any chance you can retain your old box for a bit for some experiments once the move you mention is complete?