You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use Build Matrix Trimming in (at least) nightly PR validation #7023
In PRs that only change a couple of images, we waste a ton of compute running build legs that ultimately do nothing. In the nightly repo, I think we can better optimize for PR validation speed by turning on Build matrix trimming.
Open question: should we should turn it on for any other pipelines?
[Triage] Trimming the pipelines make sense. However, we need to ensure that if tests or pipelines are changed, we validate all images. This could involve updating imageBuilder.PathArgs in the no-cache pipelines to have different paths depending on which paths were changed. Example:
Activity
lbussell commentedon Feb 2, 2026
[Triage] Trimming the pipelines make sense. However, we need to ensure that if tests or pipelines are changed, we validate all images. This could involve updating imageBuilder.PathArgs in the no-cache pipelines to have different paths depending on which paths were changed. Example: