Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-21253

Manual Pipeline trigger doesn't have Pull Requests built-in variables

XMLWordPrintable

    • 2

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      A manually triggered Pipeline on a Pull request won't have variables related to Pull Requests (such as the PR destination BITBUCKET_PR_DESTINATION_BRANCH), as these are only populated when the pipeline is triggered automatically off of a branch update.

      Steps to Reproduce

      1. Manually trigger a Pipeline on a Pull request and have an echo $BITBUCKET_PR_DESTINATION_BRANCH command in the build
      2. Observe the value of BITBUCKET_PR_DESTINATION_BRANCH variable printed in the build

      Expected Results

      BITBUCKET_PR_DESTINATION_BRANCH variable should print the Pull request destination branch name

      Actual Results

      BITBUCKET_PR_DESTINATION_BRANCH variable should print the Pull request destination branch name

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              skhandelwal@atlassian.com Sandeep K
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: