History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-526
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: AlSt
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Allow to propagate changes from a dependent build (in)to the depending build for complete/aggregated notifications

Created: 05/Feb/10 07:50 AM   Updated: 05/Feb/10 01:34 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
Build A depends on build B (or in fact on artifacts published by build B), and while build B was successful, build A failed. The failure is caused by changes in the sources checked out by build B and handed over in some shape to build A via the published artifacts. As a result, the actual culprit was not notified, since the failure-causing sources were not checked out by build A, but only in build B; and the notification was obviously sent from build A.

Add a flag (most probably in either the repository specification of build B, or in the repository's corresponding checkout step of build B?) that optionally allows to propagate changes to dependent builds -- so that the actual culprit is notified (too).

 All   Comments   Work Log   Change History      Sort Order:
No changes have yet been made on this issue.