Opened 8 years ago

Last modified 5 years ago

#1008 new enhancement

Last build status only reports last failure for multiple non-halt-on-failure steps

Reported by: ayust Owned by:
Priority: major Milestone: 0.9.+
Version: master Keywords: web, sprint

Description (last modified by dustin)

Sometimes there may be a string of steps in a build process that are all non-haltOnFailure (due to wanting to process certain types of errors in previous steps), but non-expected types of failure in earlier steps causes later steps to fail as well. In such cases, the fact that the grid/tgrid and waterfall last-build status blocks only report the final failure in the chain can be misleading.

Perhaps we should either a) report all failed steps, or b) report the first failed step and a note like "Failed test (and 2 more)".

Change History (4)

comment:1 Changed 8 years ago by dustin

  • Keywords web added
  • Milestone changed from undecided to 0.8.3

comment:2 Changed 8 years ago by dustin

  • Milestone changed from 0.8.3 to 0.8.+

comment:3 Changed 6 years ago by dustin

  • Milestone changed from 0.8.+ to 0.9.+

Sounds like an important part of the status display in the web UI.

comment:4 Changed 5 years ago by dustin

  • Description modified (diff)
  • Keywords sprint added

Some careful consideration of the build-level status for each step will help here.

Note: See TracTickets for help on using tickets.