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
Izymes
++ we remove boring from work ++
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.