-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
pipeline-stage-view-2.16
There is an important performance issue in which instances with a large number of users are suffering.
We should disable by default the commit author resolution, because, as far as I know, at the end, the only difference I see is that in the GUI of the stage-view you don’t see the name of the user in Jenkins, but the e-mail address. I have never seen a developer even noticing that the Jenkins administrator disabled this hidden feature which will produce slowness until the user resolution does not happen in an asynchronous mode.
java.lang.Thread.State: RUNNABLE at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at java.io.File.isFile(File.java:882) at hudson.model.User$3.accept(User.java:690) at java.io.File.listFiles(File.java:1291) at hudson.model.User.getLegacyConfigFilesFor(User.java:687) at hudson.model.User.getOrCreate(User.java:431) at hudson.model.User.getById(User.java:529) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1071) at hudson.model.User.get(User.java:399) at hudson.model.User.get(User.java:368) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:379) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:448) at com.cloudbees.workflow.rest.external.ChangeSetExt.mapFields(ChangeSetExt.java:186) at com.cloudbees.workflow.rest.external.ChangeSetExt.create(ChangeSetExt.java:161)