Issue Summary

For a Bitbucket Server pull request event, Bamboo should build on each pull request merge. This should be limited to the Bitbucket Server development and production branches.

This might Extend the Bitbucket Server repository trigger to build regardless of the timers in a special case that meets the following criteria:

1. Bitbucket is hosting a repository and has a Application Link to Bamboo.
2. The event is a Bitbucket pull request event type.
3. The branch is defined on Bitbucket for the repository as Production or Development branching model.

This special event should bypass all of the triggers and wait periods to be put in the build queue.

Steps to Reproduce

1. Install Bamboo. Create one linked repository and one build plan.
2. Add two more Local Agents for a total of three or more.
3. For the build, use the default Source Code Checkout.
4. Add one script task with the following script:

   • #!/bin/bash
     sleep 60
     

1. Run build as a test to make sure it runs. Confirm in Bitbucket that the commit shows a build.
2. Run the following command in a clone of the git repository listed in step one in the default branch:

   • for (( i=1 ; i <=3 ; i++)) do \
     	echo "$i" >> text ; \
     	git add . ; \
     	git commit -m "This is commit $i" ; \
     	git push ;
     	sleep 5 ; \
     done
     

Expected Results

All three pull requests should have builds.

Actual Results

First and last pull request have builds.