Ci issues resolution#4381
Conversation
|
Cursor Agent can help with this pull request. Just |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ad763a4d1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - name: Run condition check script | ||
| id: check-ci | ||
| continue-on-error: true |
There was a problem hiding this comment.
Surface affected-project detection failures
Setting continue-on-error: true here means any non-zero exit from ci-is-affected.mjs is treated as non-fatal, and the next gate (if: steps.check-ci.outcome == 'success') will just skip E2E. Because the script returns non-zero not only for "unaffected" apps but also when npx nx show projects --affected ... fails (for example, bad SHAs or an Nx execution error), this change can turn real CI failures into green jobs where tests never ran.
Useful? React with 👍 / 👎.
Description
Fixes an issue where the
tools/scripts/ci-is-affected.mjsscript was incorrectly determining affected projects, leading to all e2e CI jobs running unnecessarily. This was due to:--baseand--headarguments tonpx nx show projects --affected.if (isAffected)check always truthy.This PR updates the script to correctly pass
base/head(prioritizingNX_BASE/NX_HEADenvironment variables) to thenxcommand and properly parse its output to derive a true booleanisAffectedvalue. This ensures that e2e CI jobs are only triggered when relevant projects are actually affected.Related Issue
Types of changes
Checklist