My organization has different groups that contribute to our source repository, and they have two different sets of needs for their pull requests. For one group, I'd like to a merge check that requires a successful build and gives a default set of reviewers. For the other group, they won't require a build and they'll enter their own reviewers. I know for setting the default reviewers I could just have the different groups use different branch names that I could recognize as a pattern. But for the successful build, I don't see a way to make the distinction.
Any help would be appreciated
We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...
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