|
||||||||
|
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.
I guess it is deliberate, but one thing that annoys me is that we define some order of execution for the publisher/notifier in job config, and this runAfterFinilized affects it. From an end user prospective it is pretty difficult to find it out as it does not reflect from ui.
So one option is also to raise a bug on the workspace cleanup to run after finalize, so if it is the last one in the list, then it really gets executed as the last one....