You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Currently, we have our system setup for Bamboo branch creation (for-new-branch) when a branch is created in Bitbucket. We would prefer to have Bamboo plan branch creation when the Pull Request is created but I want to be sure of the impact of changing it.
A) Is the "for-pull-request" setting correct in the YAML for "When pull request is created"?
B) Will the mainline branch (i.e. master) still auto-build when the PR is merged?
Any input would be appreciated...
Thank you for the reply Alexey. Our Bitbucket is setup essentially as a mono-repo. The "master" branch is one version, then we have branches that represent other versions and releases off those versions. What we wish to have happen are the following steps.
1) A developer creates a branch in Bitbucket off a mainline branch.
2) No builds automatically start in Bamboo (i.e. for-pull-request).
3) The developer can make multiple pushes to the remote branch without it triggering a build.
4) Merge is not allowed until at least one clean build is finished (currently configured this way)
5) The developer creates a PR and a build is triggered on the remote branch.
6) When the build finishes clean, the Developer merges into the mainline branch (may or may not be 'master', it could be any of our mainline branches.
7) When the merge occurs to the mainline branch, a build is triggered.
Currently, we are set up with linked repositories and the Bamboo trigger is a default "Bitbucket Server repository triggered"