Status: Open (View Workflow)
Please consider a project with following publishers in this order:
- A publisher with a bug throwing an exception in its aggregation. (publisher A)
- A publisher sends notification with its aggregation. (publisher B)
In this case, the aggregation of publisher B won't be performed.
Of course, I agree that I should fix the problem in publisher A.
At the same time, I don't think it's useful that a bug in a publisher disables following aggregations. It may prevent notifications from sent to users.
I want matrix-project perform all aggregations even when any of them fail.
- is related to
JENKINS-26964 post-build action statuses handling
- links to
I've used it often enough. What's your point? Any advantage to doing that?
It's the first comment, and still would be if you hadn't started this discussion. In fact, the link you added is now at the exact same location on this page mine was when I wrote it.