nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Nx
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Failed
main
8bd4c182 fix(maven): use require for tree-kill to avoid esModuleInterop mismatch between lib and spec configs
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
83d98f78 fix(nextjs): use cached project graph in withNx (#35475) ## Current Behavior `@nx/next/plugins/with-nx.ts` calls `createProjectGraphAsync()` from inside `next.config.js` evaluation. This has two negative effects: 1. **Sandbox violations.** Calling `createProjectGraphAsync` inside the build re-runs every registered Nx plugin's `createNodesV2`. For example, on `nx-dev:next:build` this generates 562 unexpected reads — including 548 files from `packages/nx/dist/**/*.js` (Nx core internals loaded by the graph machinery) plus sibling project files like `nx-dev/nx-dev-e2e/playwright.config.ts`, spec files, and `eslint.config.mjs` files that are read by `@nx/playwright/plugin` and `@nx/eslint/plugin` while inferring targets. None of these are real input dependencies of the Next.js build — they are an implementation detail of graph creation. 2. **Daemon socket leak (workaround in #34518).** The same call also opens a daemon client socket that keeps the Node event loop alive. PR #34518 patched this with `resetDaemonClient: true` after Jest started hanging in #32880. The socket exists only because we are talking to the daemon to (re)build the graph at all. Both problems share a root cause: graph creation is being run inside the build, when the graph has already been built and cached by the Nx task runner before `next build` ever starts. ## Expected Behavior `withNx` reads the already-cached graph instead of rebuilding it. This matches the pattern used by `@nx/webpack` (`packages/webpack/src/plugins/nx-webpack-plugin/lib/normalize-options.ts`) and `@nx/rspack` (`packages/rspack/src/plugins/utils/plugins/normalize-options.ts`), both of which call `readCachedProjectGraph()` with the comment _"Since this is invoked by the executor, the graph has already been created and cached."_ The early-return guard already in `withNx` (no `NX_TASK_TARGET_TARGET` env var) ensures we only reach the graph-reading branch when running inside an Nx task, which is exactly when the cached graph is guaranteed to exist. This change: - Eliminates the 562 sandbox violations on `nx-dev:next:build` (verified locally by patching `node_modules/@nx/next/plugins/with-nx.js` and re-running the build). - Removes the need for `resetDaemonClient: true` since no daemon connection is opened in the first place — also obviating the original Jest hang. - Speeds up `next build` slightly by skipping a full graph re-creation pass. ## Related Issue(s) Follow-up to #34518 / #32880 — fixes the underlying cause that the daemon-reset workaround was treating.
by Jason Jean
J
Failed
main
83d98f78 fix(nextjs): use cached project graph in withNx (#35475) ## Current Behavior `@nx/next/plugins/with-nx.ts` calls `createProjectGraphAsync()` from inside `next.config.js` evaluation. This has two negative effects: 1. **Sandbox violations.** Calling `createProjectGraphAsync` inside the build re-runs every registered Nx plugin's `createNodesV2`. For example, on `nx-dev:next:build` this generates 562 unexpected reads — including 548 files from `packages/nx/dist/**/*.js` (Nx core internals loaded by the graph machinery) plus sibling project files like `nx-dev/nx-dev-e2e/playwright.config.ts`, spec files, and `eslint.config.mjs` files that are read by `@nx/playwright/plugin` and `@nx/eslint/plugin` while inferring targets. None of these are real input dependencies of the Next.js build — they are an implementation detail of graph creation. 2. **Daemon socket leak (workaround in #34518).** The same call also opens a daemon client socket that keeps the Node event loop alive. PR #34518 patched this with `resetDaemonClient: true` after Jest started hanging in #32880. The socket exists only because we are talking to the daemon to (re)build the graph at all. Both problems share a root cause: graph creation is being run inside the build, when the graph has already been built and cached by the Nx task runner before `next build` ever starts. ## Expected Behavior `withNx` reads the already-cached graph instead of rebuilding it. This matches the pattern used by `@nx/webpack` (`packages/webpack/src/plugins/nx-webpack-plugin/lib/normalize-options.ts`) and `@nx/rspack` (`packages/rspack/src/plugins/utils/plugins/normalize-options.ts`), both of which call `readCachedProjectGraph()` with the comment _"Since this is invoked by the executor, the graph has already been created and cached."_ The early-return guard already in `withNx` (no `NX_TASK_TARGET_TARGET` env var) ensures we only reach the graph-reading branch when running inside an Nx task, which is exactly when the cached graph is guaranteed to exist. This change: - Eliminates the 562 sandbox violations on `nx-dev:next:build` (verified locally by patching `node_modules/@nx/next/plugins/with-nx.js` and re-running the build). - Removes the need for `resetDaemonClient: true` since no daemon connection is opened in the first place — also obviating the original Jest hang. - Speeds up `next build` slightly by skipping a full graph re-creation pass. ## Related Issue(s) Follow-up to #34518 / #32880 — fixes the underlying cause that the daemon-reset workaround was treating.
by Jason Jean
J
Failed
main
83d98f78 fix(nextjs): use cached project graph in withNx (#35475) ## Current Behavior `@nx/next/plugins/with-nx.ts` calls `createProjectGraphAsync()` from inside `next.config.js` evaluation. This has two negative effects: 1. **Sandbox violations.** Calling `createProjectGraphAsync` inside the build re-runs every registered Nx plugin's `createNodesV2`. For example, on `nx-dev:next:build` this generates 562 unexpected reads — including 548 files from `packages/nx/dist/**/*.js` (Nx core internals loaded by the graph machinery) plus sibling project files like `nx-dev/nx-dev-e2e/playwright.config.ts`, spec files, and `eslint.config.mjs` files that are read by `@nx/playwright/plugin` and `@nx/eslint/plugin` while inferring targets. None of these are real input dependencies of the Next.js build — they are an implementation detail of graph creation. 2. **Daemon socket leak (workaround in #34518).** The same call also opens a daemon client socket that keeps the Node event loop alive. PR #34518 patched this with `resetDaemonClient: true` after Jest started hanging in #32880. The socket exists only because we are talking to the daemon to (re)build the graph at all. Both problems share a root cause: graph creation is being run inside the build, when the graph has already been built and cached by the Nx task runner before `next build` ever starts. ## Expected Behavior `withNx` reads the already-cached graph instead of rebuilding it. This matches the pattern used by `@nx/webpack` (`packages/webpack/src/plugins/nx-webpack-plugin/lib/normalize-options.ts`) and `@nx/rspack` (`packages/rspack/src/plugins/utils/plugins/normalize-options.ts`), both of which call `readCachedProjectGraph()` with the comment _"Since this is invoked by the executor, the graph has already been created and cached."_ The early-return guard already in `withNx` (no `NX_TASK_TARGET_TARGET` env var) ensures we only reach the graph-reading branch when running inside an Nx task, which is exactly when the cached graph is guaranteed to exist. This change: - Eliminates the 562 sandbox violations on `nx-dev:next:build` (verified locally by patching `node_modules/@nx/next/plugins/with-nx.js` and re-running the build). - Removes the need for `resetDaemonClient: true` since no daemon connection is opened in the first place — also obviating the original Jest hang. - Speeds up `next build` slightly by skipping a full graph re-creation pass. ## Related Issue(s) Follow-up to #34518 / #32880 — fixes the underlying cause that the daemon-reset workaround was treating.
by Jason Jean
J
Failed
main
8bd4c182 fix(maven): use require for tree-kill to avoid esModuleInterop mismatch between lib and spec configs
by Jason Jean
J
Failed
main
8bd4c182 fix(maven): use require for tree-kill to avoid esModuleInterop mismatch between lib and spec configs
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a4299724 Revert "feat(core): add NX_PROJECT_ROOT environment variable to runti… (#32736) …me cache inputs (#31428)" This reverts commit 5679b3ea <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> This commit caused a major perf regression. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> This commit is reverted for now. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
by Jason Jean
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Previous
Next