This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      We currently have the option enabled to build both PR head as well as the PR merge. I would prefer the PR merge to not do anything if merging the target branch into the PR doesn't create a new commit because the PR was already built on top of the latest commit from the target branch.

      This way if developers create a branch from master, and then add commits, only a single build is run, rather than two.

            Assignee:
            Unassigned
            Reporter:
            Bert JW Regeer
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: