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
fix(ci): stop fanning out the whole cockpit e2e matrix for unrelated changes
PR #932 changed three files under apps/website/src and ran 41 `Cockpit — e2e`
lanes. Two independent scoping defects stacked up.
1. apps/cockpit carried `scope:cockpit-e2e`. The cockpit-e2e matrix dispatches
`nx e2e` for the standalone Angular cap apps under cockpit/**; none of the
40 caps depends on the apps/cockpit Next.js shell, and no workflow runs the
shell's own `e2e` target. The tag could never select real work — only
over-select. And it did: apps/cockpit statically depends on apps/website, so
a website-only PR made the shell nx-affected and flipped cockpit_e2e true.
2. cockpit-matrix matched affected projects on `cap.angular` only. A cap is two
unlinked nx projects (Angular app + python backend), so a python-only cap
change attributed nothing, which main() reads as "nx found no cap" and
answers with the full fleet — 40 lanes to cover one cap.
Measured on this checkout, before → after:
website-only (PR #932 base..head) 41 lanes → 0 (job gate is now false)
python-only cap change 40 lanes → 1 (the cap that changed)
libs/chat change 40 lanes → 40 (unchanged; no coverage lost)
The python sibling's nx name is read from its own project.json rather than
derived from the path, because a wrong guess fails open to the full fleet
without ever reporting that it guessed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments