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

Update findbugs-plugin to use SpotBugs since FindBugs is dead

    Details

    • Similar Issues:

      Attachments

        Activity

        Hide
        marco_rothe Marco Rothe added a comment -

        We are using the "good, old" ™ maven job type ... Is there a chance that spotbugs files are processed in this type of job too in the nearer future?

        Show
        marco_rothe Marco Rothe added a comment - We are using the "good, old" ™ maven job type ... Is there a chance that spotbugs files are processed in this type of job too in the nearer future?
        Hide
        drulli Ulli Hafner added a comment -

        The findbugs/spotbugs parsers are already included in the warnings plugin development branch, the findbugs plugin will silently die soon. Every minute I spend in the old sources is a kind of lost time.   

        When the new release of the warnings plug-in is ready you will get a new Publisher, that can be used in Maven projects as well. It can handle findbugs and spotbugs files. If you do not want to wait you can provide a PR that adapts the FindBugsReporter class to handle the spotbugs goal and files pattern. 

        Show
        drulli Ulli Hafner added a comment - The findbugs/spotbugs parsers are already included in the warnings plugin development branch, the findbugs plugin will silently die soon. Every minute I spend in the old sources is a kind of lost time.    When the new release of the warnings plug-in is ready you will get a new Publisher, that can be used in Maven projects as well. It can handle findbugs and spotbugs files. If you do not want to wait you can provide a PR that adapts the FindBugsReporter class to handle the spotbugs goal and files pattern. 
        Hide
        marco_rothe Marco Rothe added a comment -

        Thank you for the information.

        I think you are right not to spend time on a dying plugin.

        So we wait for the new release of the warnings plugin  and switch the maven projects to the new publisher afterwards.

        In the meantime we stay with findbugs and the findbugs plugin on CI and use spotbugs only on the developer machines.

        Show
        marco_rothe Marco Rothe added a comment - Thank you for the information. I think you are right not to spend time on a dying plugin. So we wait for the new release of the warnings plugin  and switch the maven projects to the new publisher afterwards. In the meantime we stay with findbugs and the findbugs plugin on CI and use spotbugs only on the developer machines.
        Hide
        marco_rothe Marco Rothe added a comment -

        Hello,

        is the "new release of the warnings plug-in" ready? I upgraded our jenkins instance to 2.124 but can not find the publisher to use with maven projects   ...

        Show
        marco_rothe Marco Rothe added a comment - Hello, is the "new release of the warnings plug-in" ready? I upgraded our jenkins instance to 2.124 but can not find the publisher to use with maven projects   ...
        Hide
        drulli Ulli Hafner added a comment -

        Well, if all issues have been resolved. This still requires some time, since this release contains a large number of changes. My plan is to get everything fixed by the end of July. I think that there will be some beta releases in June. (Snapshots are available for analysis-core and warnings, use at your own risk).

        Show
        drulli Ulli Hafner added a comment - Well, if all issues have been resolved. This still requires some time, since this release contains a large number of changes. My plan is to get everything fixed by the end of July. I think that there will be some beta releases in June. (Snapshots are available for analysis-core and warnings , use at your own risk).

          People

          • Assignee:
            drulli Ulli Hafner
            Reporter:
            javaguy201 Java Guy
          • Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: