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

Custom findbugs detector detail description is not shown in Hudson results

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • findbugs-plugin
    • None

      We have developed our own FindBugs detectors which is deployed as a plugin to the findbugs framework, all work fine potential bugs are detected also by the plugin run through Hudson, but the priority and description are ignored completely. All High prio bugs are marked as low, and description is not displayed at all. The only description which is being displayed is 'No description available.' This is not true it is present in the plugin.jar file which is provided throught the messages.xml file but the Hudson FB framework seems to ignore this.

          [JENKINS-15660] Custom findbugs detector detail description is not shown in Hudson results

          Jan Stolze created issue -
          Ulli Hafner made changes -
          Component/s New: findbugs [ 15496 ]
          Component/s Original: analysis-collector [ 15710 ]
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Ulli Hafner made changes -
          Link New: This issue duplicates JENKINS-1528 [ JENKINS-1528 ]

          Ulli Hafner added a comment -

          Please have a look at the comments of JENKINS-1528 to make at least the short description visible.

          Ulli Hafner added a comment - Please have a look at the comments of JENKINS-1528 to make at least the short description visible.
          Ulli Hafner made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 146416 ] New: JNJira + In-Review [ 191925 ]

            drulli Ulli Hafner
            jstolze Jan Stolze
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: