-
Type:
Suggestion
-
Resolution: Timed out
-
None
-
Component/s: Dependencies
-
0
We gave a trigger reason applied to a build context, so if plan B is a child build of Plan A - plan B knows why it was triggered.
However, incase of multiple dependent builds (Plan A -> Plan B -> Plan C) - the Plan C knows that its a dependent build of Plan B, but Plan C doesn't realize/know that it was kicked off due to a code commit in Plan A.
- is incorporated by
-
BAM-2227 Dependencies should pass down meta data about the dependency chain
- Closed