Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32994

Mark build with failed test as unstable instead of failed


      When I have a single cucumber test, the following is printed on my console:

      Build step 'Publish Cucumber test result report' changed build result to FAILURE

      According to the official terminology this should be marked as "unstable" instead, since "failure" indicates a unsuccessful build.

      This consequently causes subsequent tasks in the pipeline to not trigger. The only workarround - triggering on failure - will result on broken builts getting deployed as well. Instead, I want to deploy with broken tests, but not with broken build (on development deployment).

      Please note, that these options were also implemented in the other cucumber reports plugin in the "advanced" settings. Your plugin integrates much better inside Jenkins, so we really want to stay with you!

            Unassigned Unassigned
            ambition John Cunliffe
            0 Vote for this issue
            2 Start watching this issue