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

jobs get stuck in queue from time to time

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: build-blocker-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.611 - 1.617 => ... , BuildBlockerPlugin 1.6
    • Similar Issues:

      Description

      We┬┤re using the build blocker plugin to prevent certain jobs to be processed at the same time. There jobs are triggered indepenently by time or commits to the scm. From time to time, jobs get stuck in the queue.

      What I noticed is, that jobs get stuck in the queue, in case more than one job gets queued up, eg. because one job is currently processed, which blocks the second job, and now the third one gets triggered. In case only one job gets queued up, everything looks fine.

      Let me know if I can add more information which help working on this issue.

      Help is greatly appreciated...

        Attachments

          Issue Links

            Activity

            dvh_yxlon Dirk von Husen created issue -
            dvh_yxlon Dirk von Husen made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-27708 [ JENKINS-27708 ]
            dvh_yxlon Dirk von Husen made changes -
            Description We´re using the build blocker plugin to prevent certain jobs to be processed at the same time. There jobs are triggered indepenently by time or commits to the scm. From time to time, jobs get stuck in the queue.

            What I noticed is, that jobs get stuck in the queue, in case more than one job gets queued up, eg. because one job is currently processed, which blocks the second job, and now the third one gets triggered. In case only one job gets queued up, everything looks fine.

            Help is greatly appreciated...
            We´re using the build blocker plugin to prevent certain jobs to be processed at the same time. There jobs are triggered indepenently by time or commits to the scm. From time to time, jobs get stuck in the queue.

            What I noticed is, that jobs get stuck in the queue, in case more than one job gets queued up, eg. because one job is currently processed, which blocks the second job, and now the third one gets triggered. In case only one job gets queued up, everything looks fine.

            Let me know if I can add more information which help working on this issue.

            Help is greatly appreciated...
            costescuandrei Andrei Costescu made changes -
            Link This issue is related to JENKINS-27708 [ JENKINS-27708 ]
            costescuandrei Andrei Costescu made changes -
            Link This issue is related to JENKINS-27708 [ JENKINS-27708 ]
            dvh_yxlon Dirk von Husen made changes -
            Environment Jenkins 1.613, BuildBlockerPlugin 1.6 Jenkins 1.611 - 1.614 =>, ..., BuildBlockerPlugin 1.6
            dvh_yxlon Dirk von Husen made changes -
            Environment Jenkins 1.611 - 1.614 =>, ..., BuildBlockerPlugin 1.6 Jenkins 1.611 - 1.614 => ... , BuildBlockerPlugin 1.6
            dvh_yxlon Dirk von Husen made changes -
            Environment Jenkins 1.611 - 1.614 => ... , BuildBlockerPlugin 1.6 Jenkins 1.611 - 1.617 => ... , BuildBlockerPlugin 1.6
            dvh_yxlon Dirk von Husen made changes -
            Link This issue is related to JENKINS-28926 [ JENKINS-28926 ]
            dvh_yxlon Dirk von Husen made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 163214 ] JNJira + In-Review [ 197138 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                dvh_yxlon Dirk von Husen
              • Votes:
                4 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: