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

Key: QB-3668
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Robin Shen
Reporter: Robin Shen
Votes: 0
Watchers: 0

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

Config notifications: include "committers" from the entire upstream pipeline

Created: 20/Feb/21 12:06 AM   Updated: 11/Mar/21 05:44 AM
Component/s: None
Affects Version/s: 10.0.32
Fix Version/s: 11.0.0

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

 Description  « Hide
There is a feature that's currently missing in the QB version we use (10.0.25, 2020-10-13):
We have a simple pipeline: upstream->multiple configs each builds their own source code; downstream->all those builds come together as a "whole package".
So the downstream config checks out the upstream configs in forms of Quickbuild repositories for the artifacts published.
The thing is, the upstream configs show their committers just fine, and since they are all triggered automatically by commits, the "trigger by" is scheduler. Now is where the problem came, the downstream config considers the scheduler as the "committers since the previous build". You can see from the down stream "SCM changes" (this build happens to only have one upstream config that had a new build, and others are the old newest successful builds):
Screenshot 2021-02-19 122122.png

Can you implement a new feature where the downstream config will go scan all the builds from dependencies, get all the newest committers from each of those upstream builds, and finally include them in the down stream notification settings so there will be Emails sent to all the original committers all the way from the source? And even though some upstream builds are "old' latest successful builds, the latest committers should still be included.
Right now the settings has "committers since previous build", but it (in downstream) doesn't do what we need here

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.