-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
502 proxy error when accessing PR view for jenkinsci/jenkins #3029
502 proxy error when accessing PR view for jenkinsci/jenkins #3029
Comments
Thanks for reporting the issue. I see the same message as well. No idea why Jenkins core has that problem on that page when other projects in the same folder (like acceptance test harness) do not have the problem. |
502 happens when Jenkins takes too long processing the request. I just accessed the URL linked, and opened a thread dump at the same time, and there were two separate requests from two different IP addresses, both stack traces indicating the culprit is CoverageColumn being too expensive:
|
I'm not sure what should we do (I don't even know what is "Code Coverage Column"). Could one of you give us a pointer to the next steps so the infra team can do something about it? |
Afaik, that's added by https://github.com/jenkinsci/code-coverage-api-plugin and is part of the default pipeline library used for Jenkinsfiles as well. |
Otherwise, the whole coverage result XML will be loaded just for a single value. See jenkins-infra/helpdesk#3029 for details.
It would be helpful if someone would report such problems in the plugin, otherwise it's hard to know that we have a problem here 🤷 |
Otherwise, the whole coverage result XML will be loaded just for a single value. See jenkins-infra/helpdesk#3029 for details.
This might be what we experienced after the 3.0.0 upgrade to the Code Coverage API plugin (which we hadn't definitively traced to that plugin, so hadn't yet reported it as a bug, but suspected it): namely, a significant performance regression when viewing multibranch pipeline jobs (listing branches or PRs). For us, a display of ~100 PRs now takes over 60 seconds. |
Wow that was a tricky bug (at least from a Jenkins admin point of view). Many thanks @daniel-beck for the threaddump and analysis, many thanks @uhafner for the quick fix and many thanks @NotMyFault for the help and raising the issue! Latest Coverage plugin (and dependencies) had been applied to ci.jenkins.io: the page https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/ shows in less than 2s on my machine, so closing this issue. |
Otherwise, the whole coverage result XML will be loaded just for a single value. See jenkins-infra/helpdesk#3029 for details.
Service(s)
ci.jenkins.io
Summary
If I try to access the PR view of jenkinsci/jenkins on https://ci.jenkins.io/job/Core/job/jenkins/view/change-requests/, I get a 502 proxy error:
Does anyone else experience that too? Other views, folders and jobs are unaffected.
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: