|
||||||||
|
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.
Cannot find the original Hudson commit—looks like they deleted that repository, and http://git.eclipse.org/c/hudson/org.eclipse.hudson.core.git/ has no commit of that name, so I guess they rewrote history too. Anyway IIRC it was to globally disable publishers after a failure. Probably that is wrong, because the decision is distinct for each publisher. For mailer, certainly you want it to run if there is a failure—that is the whole point! For artifact archiving and Javadoc, running after a failure is probably pointless. For JUnit test results, it is generally useful to still collect anything that might have been created prior to the failure. I am not sure introducing new UI options in each publisher is wise; better to pick the right behavior unless there is a real reason to believe that some jobs will need one behavior and others will need the opposite.