|
||||||||
|
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 don't think this qualifies as a dev list question (especially given the fact the source of this behavior really easy to find if you only do a little leg work). Readers may be knowledgable, but if they're interested in answering user questions and have the time, they'll read the users list.
The exception is if you want to figure out yourself what's going on in core (assuming you know Java well enough to go that route at all), did the research, and still cannot figure it out. As usual http://www.catb.org/esr/faqs/smart-questions.html#before applies.
Workspace Cleanup plugin, assuming this is what you use, declares its post-build action needs to run as pretty much the last step (needsToRunAfterFinalized is true, and it's a Notifier).
Not sure what you mean, but running Jenkins in a debugger would help determine why it executes things in a specific order. Don't know whether it logs anything relevant, but I doubt it.
If you determine then that core misbehaves, that would be the basis for a great issue report.