[JIRA] (JENKINS-47518) ~30-35 second queue when using Run as User who Triggered Build

[rene.scheibe@gmail.com (JIRA)]

René Scheibe commented on JENKINS-47518

Re: ~30-35 second queue when using Run as User who Triggered Build Michael Gerhart is this still relevant? You mentioned the LDAP authentication. The chance is quite high that the long query time is due to a slow LDAP system. Do you also face slow login times as user? Do you know about the caching feature in the LDAP plugin? I suggest to have a look at it. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[rene.scheibe@gmail.com (JIRA)]

René Scheibe edited a comment on JENKINS-47518

Re: ~30-35 second queue when using Run as User who Triggered Build

[~michaelgg13] is this still relevant? You mentioned the LDAP authentication. The chance is quite high that the long query time is due to a slow LDAP system. Do you also face slow login times as user? There is also an [article|https://support.cloudbees.com/hc/en-us/articles/235216188-The-log-in-with-LDAP-plugin-is-very-slow] on this . Do you know about the [caching feature|https://wiki.jenkins.io/display/JENKINS/LDAP+Plugin#LDAPPlugin-Enablecache] in the LDAP plugin? I suggest to have a look at it.

Add Comment

[graham_mcgregor@trendmicro.com (JIRA)]

Graham McGregor commented on JENKINS-47518

Re: ~30-35 second queue when using Run as User who Triggered Build

Enabling caching solved this for me

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)