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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • authorize-project-plugin
    • None
    • Jenkins ver. 2.60.2, Authorize Project 1.3.0. Users login via LDAP

      When setting up Run as User who Triggered Build Authorization Strategy on a build job, it creates a ~30-35 second queue every single time a build is run, even when all slave nodes are sitting idle.

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

          René Scheibe added a comment - - edited

          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 on this .

          Do you know about the caching feature in the LDAP plugin? I suggest to have a look at it.

          René Scheibe added a comment - - edited 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 on this . Do you know about the  caching feature in the LDAP plugin? I suggest to have a look at it.

          Graham McGregor added a comment -

          Enabling caching solved this for me

          Graham McGregor added a comment - Enabling caching solved this for me

            Unassigned Unassigned
            michaelgg13 Michael Gerhart
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: