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

Mark build as stable/unstable if there are no new warning compared to the last stable/unstable build.




      When setting the new threshold to 1, if there are new warnings, the plugin marks the build as failure. If the next build will not have any new warnings (even without any change to any file) the status will be change back because the last new warnings are not consider new anymore.
      There is another option to set the total threshold. The problem with this way is that whenever a warning is fixed, someone will need to change this threshold manually.

      Comparing the total number of warnings with the total number of warnings in the last stable/unstable build might not be enough because someone can commit a change which will fix a warning but will add a new one.


        Issue Links


            shimik shimik created issue -
            drulli Ulli Hafner made changes -
            Field Original Value New Value
            Component/s checkstyle [ 15512 ]
            Component/s dry [ 15591 ]
            Component/s findbugs [ 15496 ]
            Component/s tasks-plugin [ 15498 ]
            Component/s warnings [ 15513 ]
            drulli Ulli Hafner made changes -
            Link This issue is blocking JENKINS-5344 [ JENKINS-5344 ]
            drulli Ulli Hafner made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            scm_issue_link SCM/JIRA link daemon made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            abayer Andrew Bayer made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 135231 ] JNJira + In-Review [ 203346 ]


              drulli Ulli Hafner
              shimik shimik
              0 Vote for this issue
              0 Start watching this issue