• 3.0.0

      Include support to BitBucket Pull Request events in plugin

          [JENKINS-60342] Include support to BitBucket Pull Request

          Javier Rodríguez created issue -

          Hi khughes,

          Can you please tell me when can we expect pull request event features in Bitbucket server integration plugin?

          We have started using this plugin but unfortunately pull request events is not working.

          Kindly check and revert back ASAP.

          Thanks in advance

          SHIVAKUMAR B M added a comment - Hi khughes , Can you please tell me when can we expect pull request event features in Bitbucket server integration plugin? We have started using this plugin but unfortunately pull request events is not working. Kindly check and revert back ASAP. Thanks in advance

          Fabian Bosch added a comment -

          +1 for this featureRequest.
          please consider to increase priority on this one. seems to me like this would be the biggest benefit compared to other 3rd party plugins and reason to use it.

          Fabian Bosch added a comment - +1 for this featureRequest. please consider to increase priority on this one. seems to me like this would be the biggest benefit compared to other 3rd party plugins and reason to use it.

          The older Bitbucket Branch Source plugin already supports the pr:opened, pr:merged, pr:declined, pr:deleted, and pr:reviewer:approved events from Bitbucket Server webhooks (HookEventType.java, NativeServerPullRequestHookProcessor.java), so this is necessary for feature parity.

          Kalle Niemitalo added a comment - The older Bitbucket Branch Source plugin already supports the pr:opened , pr:merged , pr:declined , pr:deleted , and pr:reviewer:approved events from Bitbucket Server webhooks ( HookEventType.java , NativeServerPullRequestHookProcessor.java ), so this is necessary for feature parity.
          Daniel Kjellin made changes -
          Assignee Original: Kristy Hughes [ khughes ]

          Omer Kattan added a comment -

          +1 for this feature from me aswell.

          For my team, this plugin is not usable without it (and i really want us to use it).
          Our pipeline takes a lot of time to run, and we can't afford to run it for every push.

          The ability to run it only for pull requests (opened and updated at least) is critical.

          Omer Kattan added a comment - +1 for this feature from me aswell. For my team, this plugin is not usable without it (and i really want us to use it). Our pipeline takes a lot of time to run, and we can't afford to run it for every push. The ability to run it only for pull requests (opened and updated at least) is critical.

          Omer Kattan added a comment -

          Another thought, while i know this is better implemented on bitbucket's side, there is no webhook for when commits are added to an existing PR. A cool thing to check if there is an open PR when handling a push webhook request.

          Omer Kattan added a comment - Another thought, while i know this is better implemented on bitbucket's side, there is no webhook for when commits are added to an existing PR. A cool thing to check if there is an open PR when handling a push webhook request.

          Thanks for offering an alternative plugin dedicated to Bitbucket Server; we gave it a try and like the webhooks-based approach and guidance; however PR builds are a critical part of our workflow.

          So far we have been using the bitbucket-branch-source plugin, which suddenly stopped working with Bitbucket 7.
          —internal PR refs are no longer reliably updated (well, they were never really guaranteed, more details at BSERV-12198); meanwhile, fixing PRs originating from forks in branch-source plugin is wildly uncertain, since that plugin is mostly ref-based. So far we're a bit helpless.

          Mikaël Geljić added a comment - Thanks for offering an alternative plugin dedicated to Bitbucket Server; we gave it a try and like the webhooks-based approach and guidance; however PR builds are a critical part of our workflow. So far we have been using the bitbucket-branch-source plugin, which suddenly stopped working with Bitbucket 7. —internal PR refs are no longer reliably updated (well, they were never really guaranteed, more details at BSERV-12198 ); meanwhile, fixing PRs originating from forks in branch-source plugin is wildly uncertain, since that plugin is mostly ref-based. So far we're a bit helpless.
          Martin Belley-Charbonneau made changes -
          Priority Original: Minor [ 4 ] New: Blocker [ 1 ]
          Martin Henschke made changes -
          Assignee New: Martin Henschke [ mhenschke_atlassian ]

            mhenschke_atlassian Martin Henschke
            javier_rodriguez Javier Rodríguez
            Votes:
            69 Vote for this issue
            Watchers:
            83 Start watching this issue

              Created:
              Updated:
              Resolved: