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

Wrong merge order of pull request build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • bitbucket-branch-source-plugin
    • None
    • CentOS 7, Jenkins 2.138.3, bitbucket-branch-source-plugin 2.2.16, Bitbucket Server 5.16.0, Bitbucket Server Jenkins Webhook Plugin

      When building pull requests in a multibranch pipeline with the Bitbucket branch source plugin, IMO the merge order is wrong.

      The PR in Bitbucket is set up to merge a task branch into the master branch. The jenkins build console says:

      Merging remotes/upstream/master commit 49055790acff662de787b04ac7b253140be04b81 into PR head commit 5ea5ad23180c6b9b3c0876fc21f8238a293eb4a0

      The problem is that because of the wrong merge order, the commits of the actual task branch aren't shown in the changes "view" (<jenkins-url>/job/<jobname>/view/change-requests/job/<PR-ID>/changes). Only the latest master commits are shown.
      Because of this, the wrong changes are notified to the PR within the Bitbucket server.

      Can anyone help or am I just configuring something wrong?

            amuniz Antonio Muñiz
            tkucorporate Thomas Kuchel
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: