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

add console log line for reason that the build is marked as unstable when thresholds are exceeded

XMLWordPrintable

      If the anaysis plugin has a threshold that is set to mark the build as unstable no entry is put in the build console log to show why the build is marked as unstable.

      This causes some confusion to users, but also means it is not simple to integrate with the "Build Failure Analyser" so that the reason for the unstable project is immediately obvious.

      It would be nice if the there was a line

      "[plugin] Build has more failures that the threshold amount - marking unstable."

          [JENKINS-18954] add console log line for reason that the build is marked as unstable when thresholds are exceeded

          James Nord added a comment -

          (obvserved behaviour with Maven2 project type - freesyle may exhibit different behaviour)

          James Nord added a comment - (obvserved behaviour with Maven2 project type - freesyle may exhibit different behaviour)

          Ulli Hafner added a comment -

          I moved that information to the user interface quite some time ago (due to another feature request). I can duplicate that information but I think it is better placed in the UI.

          Ulli Hafner added a comment - I moved that information to the user interface quite some time ago (due to another feature request). I can duplicate that information but I think it is better placed in the UI.

          James Nord added a comment -

          I believe it is useful in the console for 2 reasons

          1) makes a quick integration wit h the build failure analyser plug-in possible

          2) I often get just the consulconsole sent to me witthe question why is this unstable as there aunit test failures. So users are expecting to see why something is boore nott a success in the console output.

          Sorry for the horrendous typing on a mobile and jira is not mobile friendly

          James Nord added a comment - I believe it is useful in the console for 2 reasons 1) makes a quick integration wit h the build failure analyser plug-in possible 2) I often get just the consulconsole sent to me witthe question why is this unstable as there aunit test failures. So users are expecting to see why something is boore nott a success in the console output. Sorry for the horrendous typing on a mobile and jira is not mobile friendly

          Ulli Hafner added a comment - - edited

          I see. I'll append the status information to the console log.

          Ulli Hafner added a comment - - edited I see. I'll append the status information to the console log.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          src/main/java/hudson/plugins/analysis/core/BuildResult.java
          http://jenkins-ci.org/commit/analysis-core-plugin/57f114308ad6305985b595929d6634bae244b781
          Log:
          [FIXED JENKINS-18954] Show plug-in result in console log.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/BuildResult.java http://jenkins-ci.org/commit/analysis-core-plugin/57f114308ad6305985b595929d6634bae244b781 Log: [FIXED JENKINS-18954] Show plug-in result in console log.

          Ulli Hafner added a comment -

          Integrated in Jenkins Analysis Plug-ins (Compile) #609
          [FIXED JENKINS-18954] Show plug-in result in console log. (Revision 57f114308ad6305985b595929d6634bae244b781)

          Result = SUCCESS

          Ulli Hafner added a comment - Integrated in Jenkins Analysis Plug-ins (Compile) #609 [FIXED JENKINS-18954] Show plug-in result in console log. (Revision 57f114308ad6305985b595929d6634bae244b781) Result = SUCCESS

            drulli Ulli Hafner
            teilo James Nord
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: