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

Bitbucket Branch Source Plugin should build merged branches in Multibranch Pipeline

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Just updated the Bitbucket Branch Source Plugin within a multibranch pipeline to the latest version, and it is full of welcome changes (thank you!). I'm using a webhook to send events to Jenkins from Bitbucket private instance. 

      One thing that appears to be missing, is a feature that we commonly use in our workflow, which is to build `dev` or `master` whenever the PR is merged. So with this plugin, we have the following outcome

      Branch Push -> Build

      PR Open -> Build

      PR Updated (via pushing code) -> Build

      PR Merged into Dev -> *Dev NOT built (*I would like `dev` to be built here.)

       

      I am seeing the hook in the pipeline events, but `dev` does not build unless I do a manual scan (or a timed scan, but that defeats the purpose of build triggers) 

      Am I doing something wrong, or is this a feature request?

        Attachments

          Activity

          chadmott chad mott created issue -
          chadmott chad mott made changes -
          Field Original Value New Value
          Description Just updated the Bitbucket Branch Source Plugin to the latest version, and it is full of welcome changes (thank you!). I'm using a webhook to send events to Jenkins from Bitbucket private instance. 

          One thing that appears to be missing, is a feature that we commonly use in our workflow, which is to build `dev` or `master` whenever the PR is merged. So with this plugin, we have the following outcome

          Branch Push -> Build

          PR Open -> Build

          PR Updated (via pushing code) -> Build

          PR Merged into Dev -> *{color:#ff0000}Dev NOT built ({color}*I would like `dev` to be built here.)

           

          I am seeing the hook in the pipeline events, but `dev` does not build unless I do a manual scan (or a timed scan, but that defeats the purpose of build triggers) 

          Am I doing something wrong, or is this a feature request?
          Just updated the Bitbucket Branch Source Plugin within a multibranch pipeline to the latest version, and it is full of welcome changes (thank you!). I'm using a webhook to send events to Jenkins from Bitbucket private instance. 

          One thing that appears to be missing, is a feature that we commonly use in our workflow, which is to build `dev` or `master` whenever the PR is merged. So with this plugin, we have the following outcome

          Branch Push -> Build

          PR Open -> Build

          PR Updated (via pushing code) -> Build

          PR Merged into Dev -> *{color:#ff0000}Dev NOT built ({color}*I would like `dev` to be built here.)

           

          I am seeing the hook in the pipeline events, but `dev` does not build unless I do a manual scan (or a timed scan, but that defeats the purpose of build triggers) 

          Am I doing something wrong, or is this a feature request?
          Summary Bitbucket Branch Source Plugin should build merged branches Bitbucket Branch Source Plugin should build merged branches in Multibranch Pipeline
          maniacmouse Andréas Berg made changes -
          Priority Minor [ 4 ] Major [ 3 ]
          maniacmouse Andréas Berg made changes -
          Issue Type Improvement [ 4 ] Bug [ 1 ]
          vivek Vivek Pandey made changes -
          Labels bitbucket bitbucket triaged-2018-11

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            chadmott chad mott
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated: