Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
master
343f9544 feat(core): add task and project count telemetry via performance lifecycle (#34821) ## Current Behavior Telemetry only reports event duration via the `measureAndTrack` helper, which uses a `[track] ` prefix convention. No task-level metrics (count, cache hits, project count) are reported. ## Expected Behavior - New event dimensions: `taskCount`, `projectCount`, `cachedTaskCount` available for telemetry events - `TaskTelemetryLifeCycle` reports task execution metrics (duration, task count, project count, cached task count) — only runs on the main CLI process, not on DTE agents - `performance.measure()` with `detail: { track: true, ... }` replaces the `measureAndTrack` / `[track] ` prefix pattern - Perf observer automatically forwards detail entries matching known GA4 dimension keys - `reportEvent` simplified to a pass-through — callers use `customDimensions` keys directly - `customDimensions` and `EventParameters` exported for use by callers
31 minutes ago by Jason Jean
Succeeded
master
0d2d7cb8 fix(core): batch hashing, topological cache walk, and TUI batch fixes (#34798) ## Current Behavior - `hashBatchTasks` hashes tasks one-by-one via `Promise.all` + `hashTask` (singular), making N separate native hasher calls. - Batch cache resolution rebuilds the entire remaining task graph each wave via `removeTasksFromTaskGraph`, which is O(tasks) per wave and can crash if `graph.dependencies[id]` is undefined. - `postRunSteps` for cached batch results is deferred until all cache resolution completes. - TUI batch groups appear below "Waiting for task..." placeholders because their status is based on nested task statuses, which may not have transitioned yet. ## Expected Behavior - `hashBatchTasks` uses `hashTasks` (plural) to batch all tasks into a single native hasher call. - Batch cache resolution uses a new `walkTaskGraph` util that walks topologically via in-degree counters — only visits direct dependents per wave instead of rebuilding the graph. - `postRunSteps` runs incrementally per wave during cache resolution. - TUI batch groups are treated as in-progress by existence (since `start_batch` was called), only moving to completed when all nested tasks are done. ## Related Issue(s) Fixes crash: `Cannot read properties of undefined (reading 'filter')` in `removeIdsFromTaskGraph` during batch cache resolution. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
1 hour ago by Jason Jean
Failed
master
343f9544 feat(core): add task and project count telemetry via performance lifecycle (#34821) ## Current Behavior Telemetry only reports event duration via the `measureAndTrack` helper, which uses a `[track] ` prefix convention. No task-level metrics (count, cache hits, project count) are reported. ## Expected Behavior - New event dimensions: `taskCount`, `projectCount`, `cachedTaskCount` available for telemetry events - `TaskTelemetryLifeCycle` reports task execution metrics (duration, task count, project count, cached task count) — only runs on the main CLI process, not on DTE agents - `performance.measure()` with `detail: { track: true, ... }` replaces the `measureAndTrack` / `[track] ` prefix pattern - Perf observer automatically forwards detail entries matching known GA4 dimension keys - `reportEvent` simplified to a pass-through — callers use `customDimensions` keys directly - `customDimensions` and `EventParameters` exported for use by callers
2 hours ago by Jason Jean
Succeeded
master
d6a7e109 fix(core): fix TUI help text layout (#34754) ## Current Behavior The TUI help text format is currently malformed. <img width="1181" height="191" alt="Screenshot 2026-03-07 at 11 13 40" src="https://github.com/user-attachments/assets/e66316eb-600d-4456-920e-c9538c10e7e7" /> - The links overlap the plaintext - Some of the plaintext has the link color - The bullet points are on the same line ## Expected Behavior Separation of links and plaintext with bullet points on separate lines. ### Changes The text output of the TUI help section looks like this: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-uiIf you would prefer to not use the TUI, you can disable it by: - Adding the `--no-tui` flag to your │ │ command.- Setting NX_TUI=false in your environment. │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` This PR corrects the layout to be more readable: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-ui │ │ │ │ If you would prefer to not use the TUI, you can disable it by: │ │ - Adding the `--no-tui` flag to your command. │ │ - Setting `NX_TUI=false` in your environment. │ │ │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` ### Notes The help link `https://nx.dev/terminal-ui` doesn't exist at the moment.
4 hours ago by Joel Lefko...
Succeeded
master
d6a7e109 fix(core): fix TUI help text layout (#34754) ## Current Behavior The TUI help text format is currently malformed. <img width="1181" height="191" alt="Screenshot 2026-03-07 at 11 13 40" src="https://github.com/user-attachments/assets/e66316eb-600d-4456-920e-c9538c10e7e7" /> - The links overlap the plaintext - Some of the plaintext has the link color - The bullet points are on the same line ## Expected Behavior Separation of links and plaintext with bullet points on separate lines. ### Changes The text output of the TUI help section looks like this: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-uiIf you would prefer to not use the TUI, you can disable it by: - Adding the `--no-tui` flag to your │ │ command.- Setting NX_TUI=false in your environment. │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` This PR corrects the layout to be more readable: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-ui │ │ │ │ If you would prefer to not use the TUI, you can disable it by: │ │ - Adding the `--no-tui` flag to your command. │ │ - Setting `NX_TUI=false` in your environment. │ │ │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` ### Notes The help link `https://nx.dev/terminal-ui` doesn't exist at the moment.
4 hours ago by Joel Lefko...
Succeeded
master
d6a7e109 fix(core): fix TUI help text layout (#34754) ## Current Behavior The TUI help text format is currently malformed. <img width="1181" height="191" alt="Screenshot 2026-03-07 at 11 13 40" src="https://github.com/user-attachments/assets/e66316eb-600d-4456-920e-c9538c10e7e7" /> - The links overlap the plaintext - Some of the plaintext has the link color - The bullet points are on the same line ## Expected Behavior Separation of links and plaintext with bullet points on separate lines. ### Changes The text output of the TUI help section looks like this: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-uiIf you would prefer to not use the TUI, you can disable it by: - Adding the `--no-tui` flag to your │ │ command.- Setting NX_TUI=false in your environment. │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` This PR corrects the layout to be more readable: ```txt │ │ │ Thanks for using Nx! To get the most out of this terminal UI, please check out the docs: https://nx.dev/terminal-ui │ │ │ │ If you would prefer to not use the TUI, you can disable it by: │ │ - Adding the `--no-tui` flag to your command. │ │ - Setting `NX_TUI=false` in your environment. │ │ │ │ If you are finding Nx useful, please consider giving it a star on GitHub, it means a lot: https://github.com/nrwl/nx │ │ │ ``` ### Notes The help link `https://nx.dev/terminal-ui` doesn't exist at the moment.
4 hours ago by Joel Lefko...
Succeeded
master
3d1b1ec6 feat(core): prompt for analytics preference during workspace creation (#34818) ## Current Behavior When a user creates a new workspace with `create-nx-workspace`, they are not asked about analytics. The analytics prompt only appears later on the first `nx` command run, or via the 22.6.0 migration. ## Expected Behavior Users are prompted to opt in or out of usage analytics during `create-nx-workspace`, so the preference is set from the start. The prompt matches the style of other prompts in the flow (autocomplete with Yes/No choices). - **Preset flow**: The `analytics` property is set via the workspace generator's `createNxJson`, so `nx.json` is properly formatted by prettier through `formatFiles(tree)` - **Template flow**: The `analytics` property is written directly to `nx.json` (matching the pattern used by `setNeverConnectToCloud`) - Supports `--analytics` CLI flag for non-interactive usage - Skips the prompt in CI and non-interactive environments (defaults to `false`)
5 hours ago by Jason Jean
Succeeded
master
3d1b1ec6 feat(core): prompt for analytics preference during workspace creation (#34818) ## Current Behavior When a user creates a new workspace with `create-nx-workspace`, they are not asked about analytics. The analytics prompt only appears later on the first `nx` command run, or via the 22.6.0 migration. ## Expected Behavior Users are prompted to opt in or out of usage analytics during `create-nx-workspace`, so the preference is set from the start. The prompt matches the style of other prompts in the flow (autocomplete with Yes/No choices). - **Preset flow**: The `analytics` property is set via the workspace generator's `createNxJson`, so `nx.json` is properly formatted by prettier through `formatFiles(tree)` - **Template flow**: The `analytics` property is written directly to `nx.json` (matching the pattern used by `setNeverConnectToCloud`) - Supports `--analytics` CLI flag for non-interactive usage - Skips the prompt in CI and non-interactive environments (defaults to `false`)
7 hours ago by Jason Jean
Succeeded
master
3d1b1ec6 feat(core): prompt for analytics preference during workspace creation (#34818) ## Current Behavior When a user creates a new workspace with `create-nx-workspace`, they are not asked about analytics. The analytics prompt only appears later on the first `nx` command run, or via the 22.6.0 migration. ## Expected Behavior Users are prompted to opt in or out of usage analytics during `create-nx-workspace`, so the preference is set from the start. The prompt matches the style of other prompts in the flow (autocomplete with Yes/No choices). - **Preset flow**: The `analytics` property is set via the workspace generator's `createNxJson`, so `nx.json` is properly formatted by prettier through `formatFiles(tree)` - **Template flow**: The `analytics` property is written directly to `nx.json` (matching the pattern used by `setNeverConnectToCloud`) - Supports `--analytics` CLI flag for non-interactive usage - Skips the prompt in CI and non-interactive environments (defaults to `false`)
7 hours ago by Jason Jean
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
8 hours ago by Jason Jean
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 hours ago by Steven Nance
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
10 hours ago by Jason Jean
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
10 hours ago by Jason Jean
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
11 hours ago by Jason Jean
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
11 hours ago by Jason Jean
Succeeded
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
11 hours ago by Jason Jean
Failed
master
9db241cb chore(repo): update nx to 22.6.0-beta.13 (#34812) Updating Nx from 22.6.0-beta.12 to 22.6.0-beta.13
11 hours ago by Jason Jean
Failed
master
74288752 docs(core): rewrite Nx vs Turborepo comparison page (#34792) ## Current Behavior The Nx vs Turborepo comparison doc mixed setup complexity with advanced features without a clear progression. Some sections were missing (code generation comparison, cross-repo coordination, project graph visualization). Images were in PNG format. ## Expected Behavior - Progressive structure: starts with basics (onboarding, running tasks) and moves to advanced capabilities (CI, AI, cross-repo); beats the misconception that starting with Nx is more complex or you need to go full in - Overview table at top for quick comparison with links to sections (we could collapse it if it gets too much 🤔) - New sections: Running tasks (to emphasize how simple it is to run tasks in an existing repo, again beating the misconceptions that are around), Cross-repo coordination, CI throughput, Project graph - Improved sections: Onboarding (incremental adoption story), Caching (real benchmark configs), Code generation (acknowledges turbo gen) - All images converted to AVIF - Migration doc updated: removed beta/Nx 21 language for continuous tasks New docs: - [comparison doc](https://deploy-preview-34792--nx-docs.netlify.app/docs/guides/adopting-nx/nx-vs-turborepo) - [migration doc (mostly untouched)](https://deploy-preview-34792--nx-docs.netlify.app/docs/guides/adopting-nx/from-turborepo) ## Related Issue(s) N/A - documentation improvement
12 hours ago by Juri Strum...
Succeeded
master
0d2d7cb8 fix(core): batch hashing, topological cache walk, and TUI batch fixes (#34798) ## Current Behavior - `hashBatchTasks` hashes tasks one-by-one via `Promise.all` + `hashTask` (singular), making N separate native hasher calls. - Batch cache resolution rebuilds the entire remaining task graph each wave via `removeTasksFromTaskGraph`, which is O(tasks) per wave and can crash if `graph.dependencies[id]` is undefined. - `postRunSteps` for cached batch results is deferred until all cache resolution completes. - TUI batch groups appear below "Waiting for task..." placeholders because their status is based on nested task statuses, which may not have transitioned yet. ## Expected Behavior - `hashBatchTasks` uses `hashTasks` (plural) to batch all tasks into a single native hasher call. - Batch cache resolution uses a new `walkTaskGraph` util that walks topologically via in-degree counters — only visits direct dependents per wave instead of rebuilding the graph. - `postRunSteps` runs incrementally per wave during cache resolution. - TUI batch groups are treated as in-progress by existence (since `start_batch` was called), only moving to completed when all nested tasks are done. ## Related Issue(s) Fixes crash: `Cannot read properties of undefined (reading 'filter')` in `removeIdsFromTaskGraph` during batch cache resolution. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
13 hours ago by Jason Jean
Failed
master
0d2d7cb8 fix(core): batch hashing, topological cache walk, and TUI batch fixes (#34798) ## Current Behavior - `hashBatchTasks` hashes tasks one-by-one via `Promise.all` + `hashTask` (singular), making N separate native hasher calls. - Batch cache resolution rebuilds the entire remaining task graph each wave via `removeTasksFromTaskGraph`, which is O(tasks) per wave and can crash if `graph.dependencies[id]` is undefined. - `postRunSteps` for cached batch results is deferred until all cache resolution completes. - TUI batch groups appear below "Waiting for task..." placeholders because their status is based on nested task statuses, which may not have transitioned yet. ## Expected Behavior - `hashBatchTasks` uses `hashTasks` (plural) to batch all tasks into a single native hasher call. - Batch cache resolution uses a new `walkTaskGraph` util that walks topologically via in-degree counters — only visits direct dependents per wave instead of rebuilding the graph. - `postRunSteps` runs incrementally per wave during cache resolution. - TUI batch groups are treated as in-progress by existence (since `start_batch` was called), only moving to completed when all nested tasks are done. ## Related Issue(s) Fixes crash: `Cannot read properties of undefined (reading 'filter')` in `removeIdsFromTaskGraph` during batch cache resolution. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
13 hours ago by Jason Jean