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

Test Result Trend keep loading unless logged in to Jenkins

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • junit-plugin
    • None
    • Jenkins 2.263.1

    Description

      [Not sure which component this actually belongs to].

      Not sure when this occurred, but likely in the process of updating Jenkins to 2.263.1 (as well as all compatible plugins). If I visit a job in Jenkins without being logged in, the Test Result Trend graph never completes loading. See attached image.

      If I login, the graph loads immediately. Seems to be the same issue with all jobs. I can see no errors in the Jenkins log related to this.

      Global security settings, authorization are set to "Logged in-users can do anything" + "Allow anonymous access". I tried to temporarily change this to "Anyone can do anything" but that didn't make any difference.

      Attachments

        Activity

          sscjni Johan created issue -
          tgr Tobias Gruetzmacher made changes -
          Field Original Value New Value
          Component/s junit-plugin [ 15499 ]
          Component/s dashboard-view-plugin [ 15679 ]
          Component/s xunit-plugin [ 15636 ]
          tgr Tobias Gruetzmacher made changes -
          Assignee Tobias Gruetzmacher [ tgr ]

          That graph is provided by the junit plugin.

          tgr Tobias Gruetzmacher added a comment - That graph is provided by the junit plugin.

          Do you have other plugins installed which use the ECharts framework? They might influence each other...

          tgr Tobias Gruetzmacher added a comment - Do you have other plugins installed which use the ECharts framework? They might influence each other...
          sscjni Johan added a comment - - edited

          I have no other plugins using ECharts, as I'm aware of. I'm also using the FitNesse plugin, which is indirectly dependent on ECharts (through JUnit) but that graph seems not to have the problem. As ECharts isn't listed as an immediate dependency of the FitNesse plugin I'm not sure if it's relevant.

          sscjni Johan added a comment - - edited I have no other plugins using ECharts, as I'm aware of. I'm also using the FitNesse plugin, which is indirectly dependent on ECharts (through JUnit) but that graph seems not to have the problem. As ECharts isn't listed as an immediate dependency of the FitNesse plugin I'm not sure if it's relevant.

          Probably not relevant, since FitNesse uses classic, server-side rendered charts. It does seem to package a pretty old jquery version, which shouldn't be a problem, since the Jenkins jQuery3 plugin tries hard to not conflict with other jQuery versions in the same page... Do you see errors in the browser console?

          tgr Tobias Gruetzmacher added a comment - Probably not relevant, since FitNesse uses classic, server-side rendered charts. It does seem to package a pretty old jquery version, which shouldn't be a problem, since the Jenkins jQuery3 plugin tries hard to not conflict with other jQuery versions in the same page... Do you see errors in the browser console?
          sscjni Johan added a comment -

          Ah. Yes, I do. This is what is logged when I load the job page without being authenticated:

          prototype.js:1585 POST http://*hostname*/$stapler/bound/4ac03fb0-2f03-48eb-8406-ceb3a905e608/getBuildTrendModel 403 (Forbidden)
          request @ prototype.js:1585
          initialize @ prototype.js:1550
          (anonymous) @ prototype.js:452
          klass @ prototype.js:101
          proxy.<computed> @ bind.js:48
          EChartsJenkinsApi.renderTrendChart @ trend-chart.js:118
          (anonymous) @ (index):88

          prototype.js:1585 POST http://*hostname*/view/5%20-%20Unstable/job/*jobname*/buildHistory/ajax 403 (Forbidden)
          request @ prototype.js:1585
          initialize @ prototype.js:1550
          (anonymous) @ prototype.js:452
          klass @ prototype.js:101
          updateBuilds @ hudson-behavior.js:2084
          setTimeout (async)
          createRefreshTimeout @ hudson-behavior.js:2137
          updateBuildHistory @ hudson-behavior.js:2146
          (anonymous) @ (index):75

          sscjni Johan added a comment - Ah. Yes, I do. This is what is logged when I load the job page without being authenticated: — prototype.js:1585 POST http://*hostname*/$stapler/bound/4ac03fb0-2f03-48eb-8406-ceb3a905e608/getBuildTrendModel 403 (Forbidden) request @ prototype.js:1585 initialize @ prototype.js:1550 (anonymous) @ prototype.js:452 klass @ prototype.js:101 proxy.<computed> @ bind.js:48 EChartsJenkinsApi.renderTrendChart @ trend-chart.js:118 (anonymous) @ (index):88 prototype.js:1585 POST http://*hostname*/view/5%20-%20Unstable/job/*jobname*/buildHistory/ajax 403 (Forbidden) request @ prototype.js:1585 initialize @ prototype.js:1550 (anonymous) @ prototype.js:452 klass @ prototype.js:101 updateBuilds @ hudson-behavior.js:2084 setTimeout (async) createRefreshTimeout @ hudson-behavior.js:2137 updateBuildHistory @ hudson-behavior.js:2146 (anonymous) @ (index):75

          That just looks like a basic "access denied" error. Which authentication plugin are you using and how is it configured?

          tgr Tobias Gruetzmacher added a comment - That just looks like a basic "access denied" error. Which authentication plugin are you using and how is it configured?
          sscjni Johan added a comment -

          Using Crowd 2. Nothing special with the plugin configuration, as far as I can see. Also, see the note on Global Security settings above in the issue. 

          I know viewing the trends used to work without being logged in, and I'm decently sure it worked up until upgrading to 2.263.1 + performing plugin updates. However I'm not sure what the versions were before upgrading.

          sscjni Johan added a comment - Using Crowd 2. Nothing special with the plugin configuration, as far as I can see. Also, see the note on Global Security settings above in the issue.  I know viewing the trends used to work without being logged in, and I'm decently sure it worked up until upgrading to 2.263.1 + performing plugin updates. However I'm not sure what the versions were before upgrading.

          People

            Unassigned Unassigned
            sscjni Johan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: