Skip navigation

Marking builds with test failures as UNSTABLE vs FAILED

Hey folks,

 

I'm toying with the idea of adding -Dmaven.test.failure.ignore=true to the Maven build line for our Jenkins jobs.  This would have the following effects when there are test failures:

  1. The Maven build will complete successfully (assuming there are no compilation or checkstyle errors).
  2. The build will be marked as UNSTABLE instead of FAILED (yellow bubble instead of red)

Because the Maven build will complete, we will be notified of test failures in all modules, as opposed to the first module with failures.  We can continue to prevent triggering downstream builds for UNSTABLE builds and will continue to receive email notifications when builds transfer from STABLE->UNSTABLE->STABLE.

 

What are your opinions on the matter?

Poll Results
  • I love it! (75%)
    27/36
  • Surely you must be joking? (25%)
    9/36

Comments

Archive Poll

Confirm archive of Marking builds with test failures as UNSTABLE vs FAILED

Archiving expires a poll and removes it from the active polls list.

To restore an archived poll, edit the poll, change the dates as desired, and save the poll.

Delete Poll

Warning: This will delete the poll and all of its comments.