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

Pipeline is failed, but is shown as SUCCESSful and green

      I geht an error in one step in my pipeline. But the view stay green.

      In console log (last step in the pipeline) I see FAILURE.

      [Pipeline] echo
      Fehler Fitnesse failed
      [Pipeline] mail
      [Pipeline] }
      [Pipeline] // withMaven
      [Pipeline] deleteDir
      [Pipeline] dir
      Running in /home/jenkins/jenkins-as-slave/m2.repository/brm-parent_master
      [Pipeline] {
      [Pipeline] deleteDir
      [Pipeline] }
      [Pipeline] // dir
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] }
      [Pipeline] // throttle
      [Pipeline] End of Pipeline
      [Checks API] No suitable checks publisher found.
      Finished: FAILURE

      But the Stage View say: SUCCESS.

          [JENKINS-63907] Pipeline is failed, but is shown as SUCCESSful and green

          Davis Ford added a comment - - edited

          I am getting the same thing.  I think it is the Checks API plugin.  It is super annoying.  Many of my builds now show failure status even though they are green.

           

          I have updated all plugins, and installed the Github Checks API plugin, but that has not fixed it.

           

          I am now getting this message:

          ```
          [GitHub Checks] Causes for no suitable publisher found:
          [GitHub Checks] Trying to resolve checks parameters from GitHub SCM...
          [GitHub Checks] No GitHub app credentials found: 'github'
          [GitHub Checks] See:
          https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc
          [GitHub Checks] Trying to resolve checks parameters from Git SCM...
          [GitHub Checks] No GitHub app credentials found: 'github'
          [GitHub Checks] See:
          https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc
          [Checks API] No suitable checks publisher found.

          GitHub has been notified of this commit’s build result
          ```

           

          I took a look at the link, but honestly, I am still getting notified in Github of the build status, and this always worked before, so I really don't want to install some Github APP or whatever....I just want this to stop failing my builds.

          Davis Ford added a comment - - edited I am getting the same thing.  I think it is the Checks API plugin.  It is super annoying.  Many of my builds now show failure status even though they are green.   I have updated all plugins, and installed the Github Checks API plugin, but that has not fixed it.   I am now getting this message: ``` [GitHub Checks] Causes for no suitable publisher found: [GitHub Checks] Trying to resolve checks parameters from GitHub SCM... [GitHub Checks] No GitHub app credentials found: 'github' [GitHub Checks] See: https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc [GitHub Checks] Trying to resolve checks parameters from Git SCM... [GitHub Checks] No GitHub app credentials found: 'github' [GitHub Checks] See: https://github.com/jenkinsci/github-branch-source-plugin/blob/master/docs/github-app.adoc [Checks API] No suitable checks publisher found. GitHub has been notified of this commit’s build result ```   I took a look at the link, but honestly, I am still getting notified in Github of the build status, and this always worked before, so I really don't want to install some Github APP or whatever....I just want this to stop failing my builds.

          George Bloggs added a comment -

          The issue for me was:

          1. I use Bitbucket and not giithub.
          2. I was unable to unplug any of the checks/github plugins due to dependencies
          3. My build was being marked as failed as no [Checks API] No suitable checks publisher found.
          4. the junit plugin (https://plugins.jenkins.io/junit/) enables the Checks API. Not convinced this is the correct approach
            (And not this plugins fault, but adding comment here as this is where google brought me)
          5. On the JUnit plugin page it states to add skipPublishingChecks, e.g.:
            junit skipPublishingChecks: true, testResults: '*/target/reports/TEST*.xml'

          George Bloggs added a comment - The issue for me was: I use Bitbucket and not giithub. I was unable to unplug any of the checks/github plugins due to dependencies My build was being marked as failed as no [Checks API] No suitable checks publisher found. the junit plugin ( https://plugins.jenkins.io/junit/) enables the Checks API. Not convinced this is the correct approach (And not this plugins fault, but adding comment here as this is where google brought me) On the JUnit plugin page it states to add skipPublishingChecks, e.g.: junit skipPublishingChecks : true , testResults : '* /target/ reports/TEST *.xml'

          oicfar the behaviour of the plugin changed it now shows the difference in individual stages (if the stage itself was successful) and the status of the overall build. 

          In screenshot 2, build 21, every stage block passed but something after(outside the stage block) caused and error and caused the build to fail.

          Raihaan Shouhell added a comment - oicfar the behaviour of the plugin changed it now shows the difference in individual stages (if the stage itself was successful) and the status of the overall build.  In screenshot 2, build 21, every stage block passed but something after(outside the stage block) caused and error and caused the build to fail.

          trident job added a comment -

          Also Happened when a child job is executed and failed. 

          trident job added a comment - Also Happened when a child job is executed and failed. 

            Unassigned Unassigned
            oicfar Rafal Kedziorski
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: