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

PRs are not rebuilt after their target branch is updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • bitbucket-branch-source-plugin
    • None
    • Jenkins ver. 2.89.4, BlueOcean plug-ins 1.5.0, BitBucket branch source plug-in version 2.2.11

      GitHub and Bitbucket show different behavior w.r.t. re-evaluation of pull requests:

      1. GitHub PRs are rebuilt after their target branch is updated;
      2. Bitbucket PRs are not rebuilt after their target branch is updated.

      I find the GitHub behavior quite useful for early detection of incompatibilities between work of multiple developers.

      Although I am aware of the controversy around this behavior, I would really appreciate if Jenkins multi-branch pipelines behave in the same way for major git server vendors.

        1. screenshot-1.png
          screenshot-1.png
          6 kB

          [JENKINS-51765] PRs are not rebuilt after their target branch is updated

          Alexei Sintotski created issue -
          Michael Kriese made changes -
          Attachment New: screenshot-1.png [ 46223 ]
          Kalle Niemitalo made changes -
          Link New: This issue duplicates JENKINS-35674 [ JENKINS-35674 ]
          Kalle Niemitalo made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            alexei_sintotski Alexei Sintotski
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: