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

The maxConn parameter defaults to 0 in JobDSL and Jenkinsfile

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Jenkins 2.249.1 (aka LTS)
      Parameterized-Remote-Trigger plugin 3.1.4
      Debian 9 docker image from upstream

      When configuring a job or a pipeline through JobDSL or Jenkinsfile the default value for maxConn isn't 1 as per documentation but 0 which causes remote triggers to time out twice - which gives a 60 seconds delay before the remote build is actually triggered.

      When configuring the job in the GUI the default is 1.

      Also JobDSL doesn't support setting maxConn so you need to use a configure block for that.

      There's a PR to fix this issue: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/75

        1. image-2020-09-30-23-59-19-153.png
          81 kB
          KaiHsiang Chang
        2. image-2020-10-01-00-03-55-907.png
          22 kB
          KaiHsiang Chang
        3. image-2020-10-01-00-05-17-805.png
          44 kB
          KaiHsiang Chang
        4. Screenshot 2020-10-01 at 11.18.33.png
          65 kB
          Jonas Linde

            cashlalala KaiHsiang Chang
            krakan Jonas Linde
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: