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

Build Current Patches Only aborts builds after triggered by patchset with no code change

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: gerrit-trigger-plugin
    • Labels:
      None
    • Environment:
      OS: Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-147-generic x86_64)
      Jenkins: 2.107.3
      Gerrit: 2.11.10
      gerrit-trigger: 2.27.5
    • Similar Issues:

      Description

      When Build Current Patches Only is selected and Exclude No Code Change is selected in a build, a change to the commit message will do the following:

      • creates a new patchset and won't trigger a new build (this is expected)
      • aborts the previous patchset's build (this is not expected)

      The expected behaviour is the previous patch should be allowed to complete its build. This was the behaviour we saw previously, but in the past 2-3 months we've only noticed this defect. Unfortunately it's hard to pinpoint any specific change that may have caused this - however, we have upgraded Jenkins and the Gerrit Trigger plugin within that time frame.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              rsandell rsandell
              Reporter:
              tvanderkooi Tim van der Kooi
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: