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

1.357 broke the findbugs and warnings plugin output - no longer displays the detailed content in the sections / tabs

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None
    • Debian testing distribution hosting Hudson as delivered by hudson-labs.org

      I've just upgraded to Hudson 1.357 and the latest versions of the plugins I use (including findbugs , warnings, static analysis utilities) on my Debian machine.

      When I navigate to the findbugs warnings (http://192.168.0.2:8080/job/My-Job/55/findbugsResult/?) or the compiler warnings (http://192.168.0.2:8080/job/My-Job/55/warningsResult/), the Warnings Trend, Summary, and Details sections appear on the page. When I attempt to select one of the tabs in the Details section (like "New" or "Types" or "Files"), the usual output table does not appear below the tabs.

      I see the same behavior on Internet Explorer, Firefox, and Chrome.

      I see the same behavior on multiple jobs (not specific to a single job).

      I did not see those problems with 1.356, only when I upgraded to 1.357. Ulrich Haffner suggests on the mailing list that it was probably a change between 1.356 and 1.357.

          [JENKINS-6496] 1.357 broke the findbugs and warnings plugin output - no longer displays the detailed content in the sections / tabs

          Alan Harder added a comment -

          Any error messages in Hudson webserver log? Any javascript errors in your browser?

          Alan Harder added a comment - Any error messages in Hudson webserver log? Any javascript errors in your browser?

          MarkEWaite added a comment -

          No indication of a javascript error in IE, IE-64, Firefox, or Google Chrome. Unfortunately, I'm not a Javascript developer, so I am not confident I've enabled the correct options in the browser to show me all javascript errors.

          The Firefox "error console" reports:

          Warning: Error in parsing value for 'white-space'. Declaration dropped.
          Source File: http://192.168.0.2:8080/static/49429fab/css/style.css
          Line: 209

          I assume that is harmless, since it is a warning and not an error.

          The Hudson log (http://192.168.0.2:8080/log/all) shows lines like the following:

          May 11, 2010 9:39:03 AM hudson.plugins.analysis.core.BuildResult loadResult
          INFO: Loaded data file /var/lib/hudson/jobs/WM-Opt-Linux/builds/2010-05-10_23-53-11/findbugs-warnings.xml for build 55

          May 11, 2010 9:39:02 AM hudson.plugins.analysis.core.ParserResult populateFileNameCache
          INFO: Relative filename 'errors.h' found more than once: absolute filename resolving disabled for this file.

          I believe the second of those messages is reporting that I have more than one copy of the file "errors.h" in my workspace. That is correct, but I assume it is irrelevant to the problem.

          MarkEWaite added a comment - No indication of a javascript error in IE, IE-64, Firefox, or Google Chrome. Unfortunately, I'm not a Javascript developer, so I am not confident I've enabled the correct options in the browser to show me all javascript errors. The Firefox "error console" reports: Warning: Error in parsing value for 'white-space'. Declaration dropped. Source File: http://192.168.0.2:8080/static/49429fab/css/style.css Line: 209 I assume that is harmless, since it is a warning and not an error. The Hudson log ( http://192.168.0.2:8080/log/all ) shows lines like the following: May 11, 2010 9:39:03 AM hudson.plugins.analysis.core.BuildResult loadResult INFO: Loaded data file /var/lib/hudson/jobs/WM-Opt-Linux/builds/2010-05-10_23-53-11/findbugs-warnings.xml for build 55 May 11, 2010 9:39:02 AM hudson.plugins.analysis.core.ParserResult populateFileNameCache INFO: Relative filename 'errors.h' found more than once: absolute filename resolving disabled for this file. I believe the second of those messages is reporting that I have more than one copy of the file "errors.h" in my workspace. That is correct, but I assume it is irrelevant to the problem.

          Ulli Hafner added a comment -

          The second warning indeed just denotes that the source file could not be found. Does your findbugs file not contain the correct source path?

          Ulli Hafner added a comment - The second warning indeed just denotes that the source file could not be found. Does your findbugs file not contain the correct source path?

          Ulli Hafner added a comment - - edited

          Here is an Hudson instance that shows the problem:
          http://faktorlogik.de:8081/view/Hudson/job/Hudson Plug-ins/64/findbugsResult

          Ulli Hafner added a comment - - edited Here is an Hudson instance that shows the problem: http://faktorlogik.de:8081/view/Hudson/job/Hudson Plug-ins/64/findbugsResult

          Ulli Hafner added a comment -

          I'm using the following piece of JavaScript to fill a tab:

                  YAHOO.plugin.Dispatcher.delegate (new YAHOO.widget.Tab({
                      label: '${%Modules}',
                      dataSrc: 'tab.modules',
                      cacheData: true,
                      active: false
                  }), myTabs);
          

          And the jelly pages contain:

            <script type="text/javascript">
                    Behaviour.apply(document);
            </script>
          

          Ulli Hafner added a comment - I'm using the following piece of JavaScript to fill a tab: YAHOO.plugin.Dispatcher.delegate ( new YAHOO.widget.Tab({ label: '${%Modules}' , dataSrc: 'tab.modules' , cacheData: true , active: false }), myTabs); And the jelly pages contain: <script type= "text/javascript" > Behaviour.apply(document); </script>

          Ulli Hafner added a comment -

          Could this issue be related to the new feature: Add "LOADING" overlay on global and job config pages until form is ready for use.

          Ulli Hafner added a comment - Could this issue be related to the new feature: Add "LOADING" overlay on global and job config pages until form is ready for use.

          MarkEWaite added a comment -

          I don't think there is any way for me to tell the Warnings plugin the absolute path to my source files (the errors.h file), and I believe it has some heuristics in it which attempt to guess the location of the file based on relative paths and searching the file tree. I'm pretty sure the findbugs plugin is not attempting to do anything with errors.h, since that is a C source file, rather than a Java source file.

          MarkEWaite added a comment - I don't think there is any way for me to tell the Warnings plugin the absolute path to my source files (the errors.h file), and I believe it has some heuristics in it which attempt to guess the location of the file based on relative paths and searching the file tree. I'm pretty sure the findbugs plugin is not attempting to do anything with errors.h, since that is a C source file, rather than a Java source file.

          Ulli Hafner added a comment -

          markewaite: Ah, sorry. I didn't see the .h file suffix (BTW: The warnings plug-in tries to resolve relative paths by scanning the whole workspace...)

          Ulli Hafner added a comment - markewaite: Ah, sorry. I didn't see the .h file suffix (BTW: The warnings plug-in tries to resolve relative paths by scanning the whole workspace...)

          Alan Harder added a comment -

          sorry.. yes, I used too generic a class for the LOADING overlay.
          war/resources/css/style.css has a rule for .loading which conflicts with analysis-core.

          Alan Harder added a comment - sorry.. yes, I used too generic a class for the LOADING overlay. war/resources/css/style.css has a rule for .loading which conflicts with analysis-core.

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/src/main/resources/hudson/model/Hudson/configure.jelly
          trunk/hudson/main/core/src/main/resources/hudson/model/Job/configure.jelly
          trunk/hudson/main/war/resources/css/style.css
          trunk/hudson/main/war/resources/scripts/hudson-behavior.js
          trunk/www/changelog.html
          http://jenkins-ci.org/commit/30918
          Log:
          [FIXED JENKINS-6496] use more specific css class name.. "loading" conflicted with YUI,
          causing missing data display in analysis plugins, using yui tabview.

          SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/resources/hudson/model/Hudson/configure.jelly trunk/hudson/main/core/src/main/resources/hudson/model/Job/configure.jelly trunk/hudson/main/war/resources/css/style.css trunk/hudson/main/war/resources/scripts/hudson-behavior.js trunk/www/changelog.html http://jenkins-ci.org/commit/30918 Log: [FIXED JENKINS-6496] use more specific css class name.. "loading" conflicted with YUI, causing missing data display in analysis plugins, using yui tabview.

            mindless Alan Harder
            MarkEWaite MarkEWaite
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: