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

Quality Gate failure doesn't fail the step.

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • warnings-ng-plugin
    • None
    • 5.2.0

      Running with warnings-ng-plugin 1.0.0beta1 and using quality gate settings to trigger a build failure I am not seeing any visual indicators as to why the pipeline failed in Blue ocean.

      However I see everything show up as "green" and no clue as to why build failed unless I exit out of Blue Ocean UI.

      I'll attach some images to show what I mean.

        1. quality-gate-not-failing.jpg
          quality-gate-not-failing.jpg
          224 kB
        2. warnings-log1.PNG
          warnings-log1.PNG
          7 kB
        3. warnings-step1.PNG
          warnings-step1.PNG
          4 kB

          [JENKINS-54373] Quality Gate failure doesn't fail the step.

          Ulli Hafner added a comment -

          This seems to be the same as for unit tests failures.

          Ulli Hafner added a comment - This seems to be the same as for unit tests failures .

          mirza zeyrek added a comment -

          Same issue here. Please check the screenshot.

          mirza zeyrek added a comment - Same issue here. Please check the screenshot.

          Arno Moonen added a comment -

          I'm also facing this issue. It is unclear to me what the status of this issue is. It was blocked by JENKINS-43995, but that issue appears to be resolved.
          Right now, not having the stage fail immediately prevents us from moving to pipelines.

          In the end the build fails, but in blue ocean nor in the normal view it is not clear where it actually failed, because it just keeps on going.

          Arno Moonen added a comment - I'm also facing this issue. It is unclear to me what the status of this issue is. It was blocked by JENKINS-43995 , but that issue appears to be resolved. Right now, not having the stage fail immediately prevents us from moving to pipelines. In the end the build fails, but in blue ocean nor in the normal view it is not clear where it actually failed, because it just keeps on going.

          Ulli Hafner added a comment -

          The status is in progress, see https://github.com/jenkinsci/warnings-ng-plugin/pull/58

          Ulli Hafner added a comment - The status is in progress, see https://github.com/jenkinsci/warnings-ng-plugin/pull/58

            drulli Ulli Hafner
            gena01 Gennady Feldman
            Votes:
            5 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: