JenkinsIcon indicating the project type

Jenkins

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

Mark warnings with an inspection status

    Details

    • Similar Issues:

      Description

      I think it would be perfect that if users could handle warnings. Warnings could be defaultly uninspected status. After users inspectation, user could mark it bug, intentional, or false positive.

      If some warnings are not bug, the next build will not identify them as errors.

        Attachments

          Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-732 Classification of findbug issues

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-732 Classification of findbug issues

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Resolved

            Activity

            Ascending order - Click to sort in descending order
            jasperlj jasperlj created issue -
            drulli Ulli Hafner made changes -
            Field Original Value New Value
            Summary Hope users could handle outstanding warnings. Mark warnings with an inspection status
            Description It's nice that the warnings plug-in could parse kinds of warnings.

            I think it would be perfect that if users could handle warnings. Warnings could be defaultly uninspected status. After users inspectation, uesr could mark it bug, intentional, or false positive.

            If some warnings are not bug, the next build will not identify them as errors.

            In current solution, some false positive are always re-identified to annoy users.
            Could it be a new feature in future? Thanks!             		I think it would be perfect that if users could handle warnings. Warnings could be defaultly uninspected status. After users inspectation, user could mark it bug, intentional, or false positive.

            If some warnings are not bug, the next build will not identify them as errors.
            drulli Ulli Hafner made changes -
            Component/s analysis-core [ 15709 ]
            drulli Ulli Hafner made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            drulli Ulli Hafner made changes -
            Link This issue is related to JENKINS-732 [ JENKINS-732 ]
            drulli Ulli Hafner made changes -
            Link This issue duplicates JENKINS-732 [ JENKINS-732 ]
            drulli Ulli Hafner made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            drulli Ulli Hafner made changes -
            Resolution Duplicate [ 3 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            drulli Ulli Hafner made changes -
            Status Reopened [ 4 ] Open [ 1 ]
            drulli Ulli Hafner made changes -
            Component/s warnings [ 15513 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 137241 ] JNJira + In-Review [ 174662 ]
            drulli Ulli Hafner made changes -
            Component/s warnings-ng-plugin [ 24526 ]
            Component/s analysis-core-plugin [ 15709 ]
            drulli Ulli Hafner made changes -
            Rank Ranked lower
            drulli Ulli Hafner made changes -
            Rank Ranked lower
            drulli Ulli Hafner made changes -
            Rank Ranked lower

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                jasperlj jasperlj
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: