The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to prevent a merge on a failed build but not require 1 to pass?

Alex Lancaster
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 11, 2019

I have added "Merge checks" to our code (we are on the premium plan) and one of the merge checks is making sure we have at least 1 successful build and 0 failed. This is all fine and dandy, however we attempt to optimize our build triggers so that it does path and branch filtering, so not all PRs require any builds (for example an update to the documentation). Because of this some PRs don't kick off any build policies and fail the "require at least 1 successful build" portion of the merge check. Is it possible to only check for 0 failed builds and not x number of successful builds? In reality I don't care if we pass 1 build policy or 100, the important thing is that all of them have finished and none of them failed. 

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

TAGS
AUG Leaders

Atlassian Community Events