Currently, the connection retry limit (connectionRetryLimit) is hardcoded to be 5 times, however that can be problematic. For example, in my case, 5 attempts with an invalid API key results in my being locked out of my LDAP account.

          [JENKINS-26562] Allow connectionRetryLimit to be changed

          Hatter added a comment -

          We've faced a similar issue with the random connection failure.

          I think it's a good option to let the user set the "connectionRetryLimit" if the user intends to do so.

          Not sure why there is no response in this ticket.

           

          Hatter added a comment - We've faced a similar issue with the random connection failure. I think it's a good option to let the user set the "connectionRetryLimit" if the user intends to do so. Not sure why there is no response in this ticket.  

          Hatter added a comment -

          cashlalala, sorry about the inconvenience here, but could you take a look at this?

          In our work we do think it's helpful if we can set the connectionRetryLimit value ourselves.

          Hatter added a comment - cashlalala , sorry about the inconvenience here, but could you take a look at this? In our work we do think it's helpful if we can set the connectionRetryLimit value ourselves.

            morficus Maurice W.
            aaronmaxlevy Aaron Levy
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: