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

Creating pull requests through the commit id's

      Hello All,

      In the source code management for git, we were able to see Refspec for the pull requests including the branch specifier. Where as, we were not able to see the same for Bitbucket. Is there a way that we can do the same for Bitbucket?. Please do let me know

       

      Thanks,

      Chennakeshwar Neravetla

          [JENKINS-65309] Creating pull requests through the commit id's

          Tzach Solomon added a comment -

          cneravetla the correct plugin is atlassian-bitbucket-server-integration and not bitbucket

          Tzach Solomon added a comment - cneravetla  the correct plugin is atlassian-bitbucket-server-integration and not bitbucket

          Josh Mueller added a comment -

          Bitbucket Server as of v 7.x no longer generates the pull-requests/<pr>/merge branch: https://jira.atlassian.com/browse/BSERV-12284?focusedCommentId=2389584&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2389584

          The workaround I use (as it is most similar to before we upgraded Bitbucket Server) is to trigger with the Stash pull request builder plugin and to use ${sourceBranch} as the "Branches to build" in the Bitbucket Server SCM and add a "Merge before build" additional behavior with the "Branch to merge to" of ${targetBranch}. Note that the "Name of repository" is actually the name of the remote in the SCM, so the repo name for BItbucket Server Integration.

          Josh Mueller added a comment - Bitbucket Server as of v 7.x no longer generates the pull-requests/<pr>/merge branch: https://jira.atlassian.com/browse/BSERV-12284?focusedCommentId=2389584&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-2389584 The workaround I use (as it is most similar to before we upgraded Bitbucket Server) is to trigger with the Stash pull request builder plugin and to use ${sourceBranch} as the "Branches to build" in the Bitbucket Server SCM and add a "Merge before build" additional behavior with the "Branch to merge to" of ${targetBranch}. Note that the "Name of repository" is actually the name of the remote in the SCM, so the repo name for BItbucket Server Integration.

            Unassigned Unassigned
            cneravetla Chennakeshwar Reddy
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: