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

Include support to BitBucket Pull Request

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Include support to BitBucket Pull Request events in plugin

        Attachments

          Issue Links

            Activity

            Hide
            macdrega Joerg Schwaerzler added a comment -

            Probably efforts can be combined?
            Bitbucket branch source plugin has support for PRs but is lacking some features for supporting the latest Bitbucket releases - while the Bitbucket server plugin does not support PRs...
            Plus, the Bitbucket Branch Source plugin currently is searching for a new maintainer.

            Show
            macdrega Joerg Schwaerzler added a comment - Probably efforts can be combined? Bitbucket branch source plugin has support for PRs but is lacking some features for supporting the latest Bitbucket releases - while the Bitbucket server plugin does not support PRs... Plus, the Bitbucket Branch Source plugin currently is searching for a new maintainer.
            Hide
            michalgawlik Michal added a comment -

            Is any ETA for implementing it?

            Show
            michalgawlik Michal added a comment - Is any ETA for implementing it?
            Hide
            wide0s Vladimir added a comment -

            Hi,

            This is hot feature for us as well. It would be great to see it early next year. Please bump up its priority.


            Regards,
            Vladimir

            Show
            wide0s Vladimir added a comment - Hi, This is hot feature for us as well. It would be great to see it early next year. Please bump up its priority. – Regards, Vladimir
            Hide
            jonathand131 Jonathan Delizy added a comment -

            The Bitbucket Branch Source plugin works very well and is perfectly integrated with Jenkins.
            It supports:

            • job triggering by webhook
            • automatic creation of webhook
            • build of branches
            • build of PRs (with/without automatic local merging on target branch)
            • notification of build status back to the Bitbucket server
            • entire project organization
            • ...

            I don't see the point in developing a new plugin which will take time to reach functional parity (missing build of PR is a deal-breaker for many of us) whereas Atlassian could have contributed to the existing one and even become the official maintainers since the Bitbucket Branch Source plugin is up for adoption.

            Mikaël Geljić: The Bitbucket Branch Source plugin is perfectly functional (even for PR build) with recent Bitbucket server releases but you need to tick the "Call Changes api" option for your Bitbucket endpoint in Jenkins global configuration.

            Niket Joshi: The Bitbucket Branch Source plugin sends the notification of build status to the Bitbucket server and it doesn't need to be combined with multiple other plugins (except the Git plugin) to get a working pipeline.

            Show
            jonathand131 Jonathan Delizy added a comment - The Bitbucket Branch Source plugin works very well and is perfectly integrated with Jenkins. It supports: job triggering by webhook automatic creation of webhook build of branches build of PRs (with/without automatic local merging on target branch) notification of build status back to the Bitbucket server entire project organization ... I don't see the point in developing a new plugin which will take time to reach functional parity (missing build of PR is a deal-breaker for many of us) whereas Atlassian could have contributed to the existing one and even become the official maintainers since the Bitbucket Branch Source plugin is up for adoption. Mikaël Geljić : The Bitbucket Branch Source plugin is perfectly functional (even for PR build) with recent Bitbucket server releases but you need to tick the "Call Changes api" option for your Bitbucket endpoint in Jenkins global configuration. Niket Joshi : The Bitbucket Branch Source plugin sends the notification of build status to the Bitbucket server and it doesn't need to be combined with multiple other plugins (except the Git plugin) to get a working pipeline.
            Hide
            macdrega Joerg Schwaerzler added a comment -

            Jonathan Delizy I totally agree that one plugin will be sufficient.
            However, please note that

            • Cloudbees is currently searching for a new maintainer of the Bitbucket Branch Source Plugin (see https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/288)
            • The plugin is NOT perfectly functional - at least not when using Bitbucket 7.x:
              • Lightweight checkouts + testing the merge commit (PR target branch -> PR source branch) are no longer possible - this is a feature we are already missing since we have some repositories that will take a long time for cloning and eat up the Jenkins master disk space in those cases (see https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/409)
              • The 'Call changes API' feature does not work properly. In fact it happens quite often that the first PR build will start before the PR reference actually has been created in Bitbucket. I suppose the plugin would need a fix to wait until the reference actually is available

            I propose that Atlassian takes over the ownership of the Bitbucket Branch Source plugin and ensures that the issues described will be fixed - or they continue maintaining their own plugin (and add the missing PR support).

            Show
            macdrega Joerg Schwaerzler added a comment - Jonathan Delizy I totally agree that one plugin will be sufficient. However, please note that Cloudbees is currently searching for a new maintainer of the Bitbucket Branch Source Plugin (see https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/288 ) The plugin is NOT perfectly functional - at least not when using Bitbucket 7.x: Lightweight checkouts + testing the merge commit (PR target branch -> PR source branch) are no longer possible - this is a feature we are already missing since we have some repositories that will take a long time for cloning and eat up the Jenkins master disk space in those cases (see https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/409 ) The 'Call changes API' feature does not work properly. In fact it happens quite often that the first PR build will start before the PR reference actually has been created in Bitbucket. I suppose the plugin would need a fix to wait until the reference actually is available I propose that Atlassian takes over the ownership of the Bitbucket Branch Source plugin and ensures that the issues described will be fixed - or they continue maintaining their own plugin (and add the missing PR support).

              People

              Assignee:
              mhenschke_atlassian Martin Henschke
              Reporter:
              javier_rodriguez Javier Rodríguez
              Votes:
              57 Vote for this issue
              Watchers:
              64 Start watching this issue

                Dates

                Created:
                Updated: