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

JaCoCo plugin should say on build result page why build failed, if threshold is broken

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Critical Critical
    • jacoco-plugin
    • None

      When a build fails/is unstable because of a broken JaCoCo threshold, the build status/summary page doesn't contain a clue why the build failed.

      I would like some similar notification like the analysis plugins (FindBugs, Checkstyle, ...) do - i.e. 'plugin result' with a small build status icon next to it

        1. screenshot-1.png
          screenshot-1.png
          68 kB

          [JENKINS-19370] JaCoCo plugin should say on build result page why build failed, if threshold is broken

          kutzi created issue -

          kutzi added a comment -

          Likewise the console contains no information, either.
          The only way to find out why the build fails, is to open the coverage report and 'guess' that the orange background of e.g. 'branch coverage' means that the build has become unstable because of too low coverage

          kutzi added a comment - Likewise the console contains no information, either. The only way to find out why the build fails, is to open the coverage report and 'guess' that the orange background of e.g. 'branch coverage' means that the build has become unstable because of too low coverage

          Akos Kozak added a comment -

          I think i case it fails because of the threshold, should the job fail not only the colour/status of the job should be changed. If the coverage drops down, the build should fail, and delvelopers should implement some more Tests, or do something. No email notification will be send if because of coverage the build "fails".

          Akos Kozak added a comment - I think i case it fails because of the threshold, should the job fail not only the colour/status of the job should be changed. If the coverage drops down, the build should fail, and delvelopers should implement some more Tests, or do something. No email notification will be send if because of coverage the build "fails".

          centic added a comment -

          Merged via https://github.com/jenkinsci/jacoco-plugin/pull/61

          centic added a comment - Merged via https://github.com/jenkinsci/jacoco-plugin/pull/61
          centic made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          centic added a comment -

          wait a moment, this might not do all that is discussed here...

          centic added a comment - wait a moment, this might not do all that is discussed here...
          centic made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 150818 ] New: JNJira + In-Review [ 186150 ]
          Michael Kroll made changes -
          Attachment New: screenshot-1.png [ 51949 ]

          Michael Kroll added a comment -

          This is crucial. We have no easy way of knowing, why the build is marked 'UNSTABLE'. Only by memorizing the configured thresholds or reading the build log.

          Michael Kroll added a comment - This is crucial. We have no easy way of knowing, why the build is marked 'UNSTABLE'. Only by memorizing the configured thresholds or reading the build log.

            ognjenb Ognjen Bubalo
            kutzi kutzi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: