Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35389
ee84b943 chore(misc): drop redundant comments on init/connect telemetry Remove 5 PR-added comments that restated the code they sat above: - configure-plugins.ts "Invoke the nx wrapper..." (try/catch makes it obvious) - utils.ts "stderr piped so the error carries it..." - utils.ts readErrorStderr JSDoc (self-describing) - utils.ts extractErrorName JSDoc (self-describing) - init-v2.ts "Structured code for bucketing..." (restates extractErrorName) Kept the genuine "why" comments (selfRecord rationale, PII-stack drop, toErrorString edge-case JSDoc, cursor-restore AI-agent caveat).
by Jack Hsu
Canceled
35389
8e2d4213 chore(misc): drop redundant comments on init/connect telemetry Remove 5 PR-added comments that restated the code they sat above: - configure-plugins.ts "Invoke the nx wrapper..." (try/catch makes it obvious) - utils.ts "stderr piped so the error carries it..." - utils.ts readErrorStderr JSDoc (self-describing) - utils.ts extractErrorName JSDoc (self-describing) - init-v2.ts "Structured code for bucketing..." (restates extractErrorName) Kept the genuine "why" comments (selfRecord rationale, PII-stack drop, toErrorString edge-case JSDoc, cursor-restore AI-agent caveat).
by Jack Hsu
Succeeded
35389
70ec093f chore(misc): move init telemetry into init-v2 handler Addresses PR review: command-object.ts should not pull in ab-testing, native (isAiAgent), utils helpers etc. at module load time — those run for every nx command. Move the start/error telemetry and AI-mode error output into the init-v2 outer handler, guarded by the `!inner` flag so the downloaded-latest nx re-invocation does not double-record. command-object.ts is now minimal again (yargs wiring only). v1 path left untouched; slated for deletion in a follow-up.
by Jack Hsu
Canceled
35389
bab467ac chore(init): format command files Co-authored-by: jaysoo <jaysoo@users.noreply.github.com>
by nx-cloud[bot]
Failed
35389
Fix applied→
503dbf61 chore(misc): richer telemetry for init and connect commands `nx init` error telemetry is largely opaque: ~22% of starts land in a bare `Command failed: npm install` bucket, and ~5% record an empty `errorMessage`. We can't tell what's actually going wrong. `nx connect` has no start/error events at all — failures (missing remote, auth, network) go untracked. Telemetry-only change. Child-process calls in init pipe stderr so the captured output reaches the error payload; error events now include `errorName` (from Node `e.code` or an extracted `E…`/`ERR_…` token like `E404`, `ERESOLVE`, `EINTEGRITY`, `ERR_PNPM_*`) and the same env context (`nodeVersion`, `os`, `packageManager`, `isCI`, `aiAgent`) as start events. `toErrorString` fixes the empty-message bucket. `nx connect` gains proper start/complete/error events. No behavioral fixes — once the enriched data comes in we'll prioritize real fixes by actual failure distribution. Fixes NXC-4262
by Jack Hsu
Failed
35389
Fix ready→
07e4de37 docs(misc): add back Cloud CNW CTA in the CI tutorial
by Jack Hsu
Canceled
35389
96543dcc chore(core): format init and connect files Co-authored-by: jaysoo <jaysoo@users.noreply.github.com>
by nx-cloud[bot]
Failed
35389
Fix ready→
bda86606 chore(misc): richer telemetry for init and connect commands ## Current Behavior `nx init` error telemetry is largely opaque: ~22% of starts land in a bare `Command failed: npm install` bucket, and ~5% record an empty `errorMessage`. We can't tell what's actually going wrong. `nx connect` has no start/error events at all — failures (missing remote, auth, network) go untracked. ## Expected Behavior Telemetry-only change. Child-process calls in init pipe stderr so the captured output reaches the error payload; error events now include `errorName` (from Node `e.code` or an extracted `E…`/`ERR_…` token like `E404`, `ERESOLVE`, `EINTEGRITY`, `ERR_PNPM_*`) and the same env context (`nodeVersion`, `os`, `packageManager`, `isCI`, `aiAgent`) as start events. `toErrorString` fixes the empty-message bucket. `nx connect` gains proper start/complete/error events. No behavioral fixes — once the enriched data comes in we'll prioritize real fixes by actual failure distribution. ## Related Issue(s) Fixes NXC-4262
by Jack Hsu
Failed
35389
Fix applied→
d9f818f6 chore(misc): richer telemetry for init and connect commands ## Current Behavior `nx init` error telemetry is largely opaque: ~22% of starts land in a bare `Command failed: npm install` bucket, and ~5% record an empty `errorMessage`. We can't tell what's actually going wrong. `nx connect` has no start/error events at all — failures (missing remote, auth, network) go untracked. ## Expected Behavior Telemetry-only change. Child-process calls in init pipe stderr so the captured output reaches the error payload; error events now include `errorName` (from Node `e.code` or an extracted `E…`/`ERR_…` token like `E404`, `ERESOLVE`, `EINTEGRITY`, `ERR_PNPM_*`) and the same env context (`nodeVersion`, `os`, `packageManager`, `isCI`, `aiAgent`) as start events. `toErrorString` fixes the empty-message bucket. `nx connect` gains proper start/complete/error events. No behavioral fixes — once the enriched data comes in we'll prioritize real fixes by actual failure distribution. ## Related Issue(s) Fixes NXC-4262
by Jack Hsu