-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Chrome
Within the Jenkin Pipeline View, any build that contains
cbwf-controller
, is causing a HTTP GET request to https://example.com/job/project/job/BRANCH_NAME/3/wfapi/changesets?_=1476824899808.
Each branch of a project on initial load will make a request to that endpoint. That will then cause the Jenkins process spike because it is trying to fulfill all of the requests.
An example of the element which has that controller is
<div class="changeset-box cbwf-widget cbwf-controller-applied run-changesets" cbwf-controller="run-changesets" objecturl="/job/ssw/job/theater-client/job/SSW-416/4/wfapi/changesets"><div><div class="run-changesets">
Build #10 will cause a GET request while build #9 wouldn't
- duplicates
-
JENKINS-35493 severe performance regression after SECURITY-243
-
- Resolved
-
dchau The cause is a Jenkins core change to fix SECURITY-243, which makes user lookup extremely expensive – this is now fixed, please see
JENKINS-35493and upgrade to Jenkins 2.7.3 or later.There's a workaround for people not yet able to update, and documented on the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Stage+View+Plugin#PipelineStageViewPlugin-ConfigurableProperties%3A
Set property com.cloudbees.workflow.rest.external.ChangeSetExt.resolveCommitAuthors to "false" to disable user lookup for changesets. This can be set at runtime to test the impact and should make your problem go away nearly immediately.