I have a build plan to run unit tests and integration tests, after all builds succeed, the dev branch only can be merged into master once the pull request is approved in Bitbucket. What I need to realize now is:
Once there is a dev branch submitted the unit tests and integration tests plan started to run, whenever there is other changes in master branch, merge master branch into this dev branch and trigger unit tests and integration tests to re-run......until pull request is approved, dev branch can be merged into master.
I thought this could be achieved by using branch updater, but just have no idea how to implement this. Anyone have some suggestion?
Thank you SO MUCH!
Thanks for responding Yogesh, but that didn't answer my question...
After several days of tests, I found that a change in master branch will not be merged into the dev branch in Bamboo automatically at all. As introduced by Bamboo official documents:
"The Branch Updater should be used when you want to:
whenever I pushed a new commit to master branch in REPO, it does successfully trigger a build on master branch in BAMBOO build plan, but neither the change in master nor the successful build on master branch will trigger what "branch updater" promised to do, in expectation, the change in master or the successful build on master branch should "trigger a merge from master branch to dev branch in bamboo, then push it back to repo dev branch after a successful build."
Whoever has related experiences, please give me some hints... I am struggling...
Hi @Ian Chen
When to use Branch Updater and Gatekeeper you can find docs here.
click on the particular plan (plan Configuration) page there you will find Branches tab and you have to select Branch merging enabled and there you will get two options ie Branch Updater and Gatekeeper and you can choose anyone of them.
Note: if your repository type is Subversion then Subversion', which does not support automatic merging.
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs