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

Multiple queued PR builds trigger one build

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      rAt some recent point (after 1.31.4, maybe after 1.32.1), if a job building a PR was queued, then a job was triggered for the same job via a different PR, a new build would not be queued. Instead a single job would be triggered with multiple triggers. For example:

      The resulting build builds only one of the PR's merged codebases. I'm not sure if which one is even determinate.

        Attachments

          Activity

          oeuftete oeuftete created issue -
          Show
          oeuftete oeuftete added a comment - See also https://github.com/jenkinsci/ghprb-plugin/issues/354 .
          oeuftete oeuftete made changes -
          Field Original Value New Value
          Description At some recent point (after 1.31.4, maybe after 1.32.1), if a job building a PR was queued, then a job was triggered for the same job via a different PR, a new build would not be queued. Instead a single job would be triggered with multiple triggers.

          The resulting build builds only one of the PR's merged codebases. I'm not sure if which one is even determinate.
          At some recent point (after 1.31.4, maybe after 1.32.1), if a job building a PR was queued, then a job was triggered for the same job via a different PR, a new build would not be queued. Instead a single job would be triggered with multiple triggers. For example:

          !https://cloud.githubusercontent.com/assets/170730/15618532/8d95c2ec-241c-11e6-8b95-4bb8b2081bac.png!

          The resulting build builds only one of the PR's merged codebases. I'm not sure if which one is even determinate.
          oeuftete oeuftete made changes -
          Link This issue is related to SECURITY-170 [ SECURITY-170 ]
          oeuftete oeuftete made changes -
          Description At some recent point (after 1.31.4, maybe after 1.32.1), if a job building a PR was queued, then a job was triggered for the same job via a different PR, a new build would not be queued. Instead a single job would be triggered with multiple triggers. For example:

          !https://cloud.githubusercontent.com/assets/170730/15618532/8d95c2ec-241c-11e6-8b95-4bb8b2081bac.png!

          The resulting build builds only one of the PR's merged codebases. I'm not sure if which one is even determinate.
          rAt some recent point (after 1.31.4, maybe after 1.32.1), if a job building a PR was queued, then a job was triggered for the same job via a different PR, a new build would not be queued. Instead a single job would be triggered with multiple triggers. For example:

          !https://cloud.githubusercontent.com/assets/170730/15618532/8d95c2ec-241c-11e6-8b95-4bb8b2081bac.png!

          The resulting build builds only one of the PR's merged codebases. I'm not sure if which one is even determinate.
          Hide
          oeuftete oeuftete added a comment -

          This works again in recent releases.

          Show
          oeuftete oeuftete added a comment - This works again in recent releases.
          oeuftete oeuftete made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 171470 ] JNJira + In-Review [ 210101 ]
          kadam Adam Kapos made changes -
          Hide
          kadam Adam Kapos added a comment -

          Happens using Jenkins 2.41 and plugin version 1.34.0 and 1.33.4:

          Show
          kadam Adam Kapos added a comment - Happens using Jenkins 2.41 and plugin version 1.34.0 and 1.33.4:

            People

            Assignee:
            janinko Honza Brázdil
            Reporter:
            oeuftete oeuftete
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: