The tests at one same repository are split a per below in TeamCity.
Test set (showstopper)
Test set (critical)
Test set (major)
Test set (minor)
For the merge condition, Minimum successful builds - requires at least the specified number of successful builds before merging:
I don't think prioritizing build results is possible out of the box with Bitbucket.
Could you create a scenario where the main src changes and each test set create a separate pull request? If so - then you can use Organizr for Bitbucket to create dependencies between the test set pull requests and the main pull requests in a way that each test set pull request must be merged (with build result condition) before the main pull request can be merged.
.. or write a custom app that prioritises build results for your team workflow.
Hope that helps,
Kind regards, Ulrich
++ we remove boring from work ++
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events