Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-10844

In progress builds and cancelled builds should be ignored for the Merge check

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 7
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Scenario 1: The build merge check says "If there are more builds than specified above, they are all required to be successful in order to merge the pull request." however it actually blocks merges to wait for in-progress builds. Either the messaging should be updated to make this clear or the implementation should be updated to ignore in-progress builds.

      Via Community

      Scenario 2: When we have configured the minimum number of required builds to a value like 1 0r more, the UI says, "You cannot merge this pull request while it has cancelled builds. You still need a minimum of 1 successful build before this pull request can be merged." when one of the recent builds is cancelled and blocks the user from merging the pull requests.

            [BSERV-10844] In progress builds and cancelled builds should be ignored for the Merge check

            Nitin Sharma added a comment - https://getsupport.atlassian.com/browse/SSP-60317

            Any updates about this?

            Sagy Drucker added a comment - Any updates about this?

              Unassigned Unassigned
              lbain Lucy
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: