Background:
In my company we are in the process of introducing a development pipeline whereby stash is acting as an initial gatekeeper into the mainline git branch. We have configured stash to allow a pull request to be merged only if a peer review has taken place and a bamboo build has passed.

Problem:
The current solution which is suggested in order for new branches to be tested by bamboo is to use the automatically manage branches feature in bamboo. However this feature has two limitations.

• The time between scans for new branches is currently configurable only by using a command line parameter for the jvm. Its setting applies globally to all projects. Its default is 5 minutes. This default is too long when considering the feedback chain. "The earlier a bug is found, the cheaper it costs"
• The feature appears at least from the surface as inefficient and un-scaleable. I am willing to be corrected. I come to this conclusion as performing regular git operations (to check for branches) on a mounting number of git repositories seems wasteful when stash already knows about every individual change to the git repository.

Suggested Solution:
Stash introduces a repository post receive hook which

• Calls the bamboo api to create a new plan branch if it does not already exist. (/chain/admin/createPlanBranch.action)
• Instructs bamboo to build the plan branch