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

            Activity

            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 ]
            Hide
            drulli Ulli Hafner added a comment - - edited

            This is related to JENKINS-732. The FindBugs team currently develops something similar: http://findbugs.cs.umd.edu/cloud/.

            Show
            drulli Ulli Hafner added a comment - - edited This is related to JENKINS-732 . The FindBugs team currently develops something similar: http://findbugs.cs.umd.edu/cloud/ .
            Hide
            jasperlj jasperlj added a comment -

            Thanks for your information.

            I had a look at JENKINS-732. I suggest not to suppress warning in source code, as we have to modify all parsers. I advise that, false positive warnings could be marked false in UI, and later warnings could be compared to it. So false ones could go away in later build.

            Show
            jasperlj jasperlj added a comment - Thanks for your information. I had a look at JENKINS-732 . I suggest not to suppress warning in source code, as we have to modify all parsers. I advise that, false positive warnings could be marked false in UI, and later warnings could be compared to it. So false ones could go away in later build.
            Hide
            jasperlj jasperlj added a comment -

            Could the feature come to analysis-core or plug-ins based on analysis-core?
            And could you predict the time? Thanks!

            Show
            jasperlj jasperlj added a comment - Could the feature come to analysis-core or plug-ins based on analysis-core? And could you predict the time? Thanks!
            Hide
            drulli Ulli Hafner added a comment -

            This makes definitely sense in the core, as all plug-ins could benefit.

            I don't think that I have time to implement such a feature. Are you interested in providing a patch?

            Show
            drulli Ulli Hafner added a comment - This makes definitely sense in the core, as all plug-ins could benefit. I don't think that I have time to implement such a feature. Are you interested in providing a patch?
            drulli Ulli Hafner made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            Hide
            jasperlj jasperlj added a comment -

            Sorry, I don't have much experience on developing such kind of complicated plug-in.
            I even don't know where to start. But as you said, this feature could benefit all analysis tools.
            Could any body help to implement it? Or do you have any idea in mind how to implement it?

            Thanks!

            Show
            jasperlj jasperlj added a comment - Sorry, I don't have much experience on developing such kind of complicated plug-in. I even don't know where to start. But as you said, this feature could benefit all analysis tools. Could any body help to implement it? Or do you have any idea in mind how to implement it? Thanks!
            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: