svanoort you might want to add this comment to the backend ticket - UX-448.

Usually we have two tickets (frontend and backend) so its clear who is doing what and keep the communication lines clear between the team members.

jdumay Ah, good point, thanks – I'll add there too (both ends need to be aware of this since it touches upon the data model used for communications here)

svanoort there are probably a few tickets some of those things are covered.

In the case of caught errors that result in overall success - I think that is ok. It may look odd and we may need to tweak how it behaves though.

For parallel: if a branch fails then the "enclosing" stage should probably be shown as a failure.

I think there will be many more little tickets to flush out these edge cases vs all at once.

mneale Yes, a failure on a branch indicates a failure for the stage... this is also true for successes across all branches. The other states are less well-defined though (we should consider providing some sort of "fuzzy" option where there are different values).

For now, I'd be happy seeing something that covers the 90% of cases but isn't going to fall over totally with the other 10%, but I want to make sure they're noted so they don't come up as a surprise.

This ticket has been redefined in JENKINS-40929. Please watch this ticket instead.