I want to enforce the "minimum successful builds" merge check not for the entire repo, but only for merges to develop branch. I do not see a way to do this in BBS.
Here it is described how to do this in Cloud:
Please advise if this is possible, and how to do it. THanks.
Hey @Tim Black we don't offer that feature in Bitbucket. I didn't manage to find any plugin on marketplace page that might help you. The only solution for you I have right now is trying to develop your own merge check plugin that is adding a missing feature:
- https://developer.atlassian.com/server/bitbucket/how-tos/hooks-merge-checks-guide/
- https://developer.atlassian.com/server/bitbucket/tutorials-and-examples/controlling-when-pull-requests-can-be-merged/
- https://developer.atlassian.com/server/bitbucket/reference/plugin-module-types/repository-merge-check-plugin-module/
You can raise a feature request ticket for us at https://jira.atlassian.com/browse/BSERV
Thanks,
Maciej
@Maciej Adamczak it looks like there is already a feature request for this:
https://jira.atlassian.com/browse/BSERV-11830
I can't believe that this hasn't been prioritized more. The fact that I am the only vote for this request tells me that either people really don't need this feature, or BSERV-11830 is poorly worded and people haven't found it.
I will comment there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for sharing the ticket and apologize for the missing feature. We will consider working on that once it gathers more votes. Stay tuned and please add yourself as a watcher of that ticket.
Thanks,
Maciej
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.