title: Bitbucket Build Status of Pull Request showing failed builds, instead of latest build status
body: <p>I integrated Bitbucket with Cloudbees, having the following workflow: everytime an user creates a Pull Request, having as target <strong>develop</strong> branch, a multi-branch pipeline in cloudbees will cluster the pull request (e.g. PR-34) and it will trigger the first build (#1). If it passes, then everything is ok and bitbucket will show the build status as &quot;passed&quot;. <br>
  However, if the build fails, it means that the user should trigger another one on the same pull request (PR-34 #2). If the second build passes, I expect to have the build status as &quot;passed&quot; but I get &quot;1 build failed&quot;, due to the first build and no matter how many passed builds I will have in the future, the status will always remain as failed if at least one of the builds failed. <br>
  So, in order to resume the problem I need help on those following topics: <br></p>
  <ol>
  <li>How should I configure bitbucket pull request status to show me the result of the <strong>latest</strong> build? <br></li>
  <li>How should I constrain the merge checks so that users will be able to merge a pull request only if the latest build passed? <em>Note: the check &quot;Minimum successful builds&quot; will not work since the behavior is the following: &quot;If there are more builds than specified, they are all required to be successful in order to merge the pull request.&quot;</em></li>
  </ol>