|
||||||||
|
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.
Jenkins doesn't even delete project workspaces when projects are deleted, so deleting any other caches would be surprising behavior.
This would require fairly complex behavior anyway, as nodes could be offline when the project gets deleted (and there would be the expectation that it'd get deleted the next time the slave is online). Pretty big can of worms right there for questionable benefit.
FWIW all of this could be implemented in the plugin through extension points that already exist AFAICT, so requires no core improvements. (I just don't think this would be useful.)