Plan builds can occur by either commit or completion of another plan (and likely additional triggers as well). Currently, if a plan builds due to a PlanRepo Trigger, there is no visibility in Plans UI that displays which Plan triggered another Plan's build. Instead, the most recent commit is still displayed. In situations where a repo is dependent on changes from an upstread repo, only having the commit of the current repo and not the upstream repo and/or not the knowledge of what caused the build makes it difficult to trace back things like test failure root causes.
Workaround recommended by @davidmreed
- Assuming the change results in an upstream package beta build, using package versions in the created org is one way to link a build with an upstream repo's trigger.
Plan builds can occur by either commit or completion of another plan (and likely additional triggers as well). Currently, if a plan builds due to a PlanRepo Trigger, there is no visibility in Plans UI that displays which Plan triggered another Plan's build. Instead, the most recent commit is still displayed. In situations where a repo is dependent on changes from an upstread repo, only having the commit of the current repo and not the upstream repo and/or not the knowledge of what caused the build makes it difficult to trace back things like test failure root causes.
Workaround recommended by @davidmreed