Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Done
Fix Version/s: 7.14.0
Component/s: Integration – Build Status
Labels:
None

UIS:
34

At the moment when bamboo send a build result to stash, stash will take that result into account (for the number of required green builds before a merge) whether it comes from a plan that is relevant or not.

This means that copying a build plan in Bamboo (which notifies Stash) and having red builds from the coup will prevent PR-merges in Stash. Even though that copy of a plan isn't relevant.

It would be nicer to be able to specify from Stash which Bamboo plans are relevant to block or not a merge.

is duplicated by

BSERV-8298 Bitbucket keeps outdated Bamboo build information

Closed

BSERV-7820 As a Stash user, I need contextualized build status so that a pull request could be merged even if builds not relative to the pull request are failing.

Closed

BSERV-8805 More flexibility when configuring required green builds on PR merge

Closed

BSERV-10213 Require pull request successful build count for specific branches

Closed

BSERV-10458 Pull-Requests with Target-Merging

Closed

relates to

BSERV-12605 Allow merge checks based on target / master branch build status

Gathering Interest

BUILDENG-5785 Loading...

SSP-14879 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(3 relates to, 8 mentioned in)

Assignee:: Unassigned
Reporter:: Colin (Inactive)
Votes:: 46 Vote for this issue
Watchers:: 38 Start watching this issue

Created:: 17/Jun/2014 1:05 AM
Updated:: 08/Sep/2021 5:49 AM
Resolved:: 08/Sep/2021 5:49 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates