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

Build Stats Plugin Returns so much data it hangs

    XMLWordPrintable

Details

    Description

      Using Global-Build-Stats 1.3 and Jenkins 1.470

      I've configured about 6 graphs in our Jenkins environment. Now when clicking the global build stats link from the manage jenkins options, I get the attached screenshot. See the chrome network details in the image, what appears to be happening is the request to the following URL:

      http://jenkins:8080/plugin/global-build-stats/api/json?depth=2

      Never stops returning data, it reaches roughly 536kb of JSON streams before the browser just hangs/crashes/gives up.

      The charts I have plotted are 3 build stats charts for fairly busy Continuous Integration jobs over the past 14 days (daily aggregated stats over 14 days for success/fail etc) And the same time interval for Average Build Time.

      The individual api's for each chart work fine if I request the specific JSON data for the chart, I get accurate and clear data. Such as:

      http://jenkins:8080/plugin/global-build-stats/api/json?depth=2&buildStatConfigId=qTJa$m7WnHjwPakLc7PLhaer$ze*zypA

      Due to this issue however, I cannot configure any new charts, or remove charts.

      So I need two solutions. First, I need to get access to the configuration screen, which means I need a way to delete a chart configuration manually without relying on the configuration screen in Jenkins.

      Second, I need to know if this limitation is by design, if I've done something wrong, is this a genuine bug, can I fix this?

      Attachments

        Activity

          grayaii Alex Gray added a comment -

          This is an old ticket, but just for the record, I'm seeing this too (global/build-stats/api/json?depth=2 returns insane amounts of data) :
          Jenkins ver. 1.596.2
          Global Stats Plugin version: 1.3
          I'm hesitant to delete my charts, but if that is the only way to make this plugin work, then I'll do it.

          grayaii Alex Gray added a comment - This is an old ticket, but just for the record, I'm seeing this too (global/build-stats/api/json?depth=2 returns insane amounts of data) : Jenkins ver. 1.596.2 Global Stats Plugin version: 1.3 I'm hesitant to delete my charts, but if that is the only way to make this plugin work, then I'll do it.

          I've encountered a similar issue, Jenkins ver. 1.588 and plugin ver. 1.3. It takes a long time to load the three charts I've created. There is a lot of duplication in global-build-stats.xml with thousands of lines like these...

              <bsc reference="../bsc[2]"/>
              <bsc reference="../bsc[6]"/>
              <bsc reference="../bsc[14]"/>
          

          And when I open the dev console in Firefox and view the network tab there are thousands of requests like this

          https://jenkins:8080/plugin/global-build-stats/showChart?buildStatId=RopHvBTaaKImO4exe1!cvEufZ*UUKLqM&time=1448053243783
          

          I can't seem to be able to purge the bad config. Something I'm wondering that could be related is that when I was first configuring the graphs I had auto-refresh enabled and it was making it difficult to save configuration. Is it possible that trying to save configuration with auto refresh enabled that the configuration was saved numerous times?

          jonnymcc Jonathan McCall added a comment - I've encountered a similar issue, Jenkins ver. 1.588 and plugin ver. 1.3. It takes a long time to load the three charts I've created. There is a lot of duplication in global-build-stats.xml with thousands of lines like these... <bsc reference= "../bsc[2]" /> <bsc reference= "../bsc[6]" /> <bsc reference= "../bsc[14]" /> And when I open the dev console in Firefox and view the network tab there are thousands of requests like this https: //jenkins:8080/plugin/global-build-stats/showChart?buildStatId=RopHvBTaaKImO4exe1!cvEufZ*UUKLqM&time=1448053243783 I can't seem to be able to purge the bad config. Something I'm wondering that could be related is that when I was first configuring the graphs I had auto-refresh enabled and it was making it difficult to save configuration. Is it possible that trying to save configuration with auto refresh enabled that the configuration was saved numerous times?

          Having the same Issue when I create a graph it mulitplies the configuration entries each time, I edit the graph.
          This caused about 2500 entries in a view minutes, which I can see here: /jenkins/plugin/global-build-stats/api/json?depth=2 .

          I am using Jenkins 1.642.3 and pluginversion 1.3.

          ludwig_richter Ludwig Richter added a comment - Having the same Issue when I create a graph it mulitplies the configuration entries each time, I edit the graph. This caused about 2500 entries in a view minutes, which I can see here: /jenkins/plugin/global-build-stats/api/json?depth=2 . I am using Jenkins 1.642.3 and pluginversion 1.3.
          saraswathi_sankar saraswathi sankar added a comment - - edited

          Jenkins Version: 1.509.2
          Global Build Stats Plugin Version: 1.3

          I hit this issue and followed the steps to delete the charts, but in vain. Any session that i open in Chrome / Firefox / IE in any machine simply hangs and does not load the charts.

          Any help would be much appreciated.

          saraswathi_sankar saraswathi sankar added a comment - - edited Jenkins Version: 1.509.2 Global Build Stats Plugin Version: 1.3 I hit this issue and followed the steps to delete the charts, but in vain. Any session that i open in Chrome / Firefox / IE in any machine simply hangs and does not load the charts. Any help would be much appreciated.

          Was able to resolve the issue in a very crude way - by deleting global-build-stats.xml file and restarting Jenkins master.
          Enabling auto refresh seemed to have been the culprit, i guess...

          saraswathi_sankar saraswathi sankar added a comment - Was able to resolve the issue in a very crude way - by deleting global-build-stats.xml file and restarting Jenkins master. Enabling auto refresh seemed to have been the culprit, i guess...

          People

            fcamblor Frédéric Camblor
            maxfields2000 Maxfield Stewart
            Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated: