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

throttle current build not working when 2 or more build starts at same time with same parameter

    XMLWordPrintable

Details

    Description

      Dear Team,

      We have implemented a throttle concurrent build plugin in our prod Jenkins environment and are facing issues due to that. We are using the project category with prevent parameter option.

      In this, when 3build are coming at the same time with the same parameter it's not able to throttle the build. all builds are started same time and creating issues.

       

      Observation is when the first job is yet to clone on master other jobs are started running. If the first job is a clone on master then other jobs are get queued.

      For e.g: I have 3 jobs that started on the same time 12:00 with parameter name defaulttenantname and the value is dep011test-one-dev-ee. then while 1st job is getting clone the rest of the other jobs are started working.

      Here, If 1st job is cloned then the rest of the other jobs are getting queued.

       

      One more bug is if 1 job is in the queue and we trigger another job with the same parameter then that job does not get queued and even it does not show in Jenkins and never gets triggered.

      Please help me to solve this issue. As we are blocked due to this.

       

      Thanks,

      Jayesh Mahajan

       

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          jayesh007 Jayesh Mahajan added a comment -

          Team

          Please update.

          jayesh007 Jayesh Mahajan added a comment - Team Please update.
          marco_jacob Marco Jacob added a comment -

          We encountered a similar behaviour only with pipeline jobs.

          Until yesterday we had 10 maven build jobs with throttle of 0 for the same category. Only one job should run because they use the same resource.

          Now we switched from maven jobs to pipeline jobs with inline script and use the same configuration at the job configuration and in the pipeline script itself.

          The result is, that 2 jobs starting at the same time not blocked.
          In this case the server started should only be used by one of the two jobs.

          One of the jobs will now fail.

          The same example with maven jobs worked and there was no concurrent run.

          marco_jacob Marco Jacob added a comment - We encountered a similar behaviour only with pipeline jobs. Until yesterday we had 10 maven build jobs with throttle of 0 for the same category. Only one job should run because they use the same resource. Now we switched from maven jobs to pipeline jobs with inline script and use the same configuration at the job configuration and in the pipeline script itself. The result is, that 2 jobs starting at the same time not blocked. In this case the server started should only be used by one of the two jobs. One of the jobs will now fail. The same example with maven jobs worked and there was no concurrent run.
          marco_jacob Marco Jacob added a comment -

          This seems only to happen when the jobs are scheduled by cron at the same time, not when I start them manually after each other.

          marco_jacob Marco Jacob added a comment - This seems only to happen when the jobs are scheduled by cron at the same time, not when I start them manually after each other.

          People

            Unassigned Unassigned
            jayesh007 Jayesh Mahajan
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: