Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36439
46032e17 cleanup(core): read nx.json once when starting analytics startAnalytics read it three times: isAnalyticsEnabled, the local nxJson, and generateWorkspaceId. Both now take the config the caller already has, so workspace-id does no file IO of its own.
by FrozenPandaz
Failed
36439
Environment issue→
32ffbac8 fix(core): normalize remote casing and trailing slashes in the repo key Hosts route case-insensitively and hold one canonical casing, so git@GitHub.com:NRWL/Nx.git and git@github.com:nrwl/nx.git are one repo and must produce one key - otherwise a hand-typed remote yields a record the claim flow can never match, since it derives keys from canonically-cased host API repo lists.
by FrozenPandaz
Canceled
36439
32ffbac8 fix(core): normalize remote casing and trailing slashes in the repo key Hosts route case-insensitively and hold one canonical casing, so git@GitHub.com:NRWL/Nx.git and git@github.com:nrwl/nx.git are one repo and must produce one key - otherwise a hand-typed remote yields a record the claim flow can never match, since it derives keys from canonically-cased host API repo lists.
by FrozenPandaz
Canceled
36439
32ffbac8 fix(core): normalize remote casing and trailing slashes in the repo key Hosts route case-insensitively and hold one canonical casing, so git@GitHub.com:NRWL/Nx.git and git@github.com:nrwl/nx.git are one repo and must produce one key - otherwise a hand-typed remote yields a record the claim flow can never match, since it derives keys from canonically-cased host API repo lists.
by FrozenPandaz
Canceled
36439
32ffbac8 fix(core): normalize remote casing and trailing slashes in the repo key Hosts route case-insensitively and hold one canonical casing, so git@GitHub.com:NRWL/Nx.git and git@github.com:nrwl/nx.git are one repo and must produce one key - otherwise a hand-typed remote yields a record the claim flow can never match, since it derives keys from canonically-cased host API repo lists.
by FrozenPandaz
Succeeded
36439
0a63ed46 fix(core): do not send an analytics user id from CI A CI fleet is not a user: runners built from one image share a baked /etc/machine-id, so machineId x workspaceId collapses the whole fleet into a single GA user - the source of GA's single-user-ID warning and of per-user daily collection caps silently discarding events. uid (and up.user_id) are now omitted when isCI(); GA's Blended identity falls back to cid = workspace, so CI activity still attributes to the repo.
by FrozenPandaz
Succeeded
36439
0a63ed46 fix(core): do not send an analytics user id from CI A CI fleet is not a user: runners built from one image share a baked /etc/machine-id, so machineId x workspaceId collapses the whole fleet into a single GA user - the source of GA's single-user-ID warning and of per-user daily collection caps silently discarding events. uid (and up.user_id) are now omitted when isCI(); GA's Blended identity falls back to cid = workspace, so CI activity still attributes to the repo.
by FrozenPandaz
Canceled
36439
7a997462 feat(core): derive stable repo key from normalized remote and relative path Adds deriveRepoKey: sha256(domain/slug + '#' + git-root-relative path), using getVcsRemoteInfo for protocol-independent remote normalization (ssh, https, and token URLs of one repo all yield the same key) and including the workspace's path inside the repo so nested workspaces get distinct keys. Falls back to the first-commit SHA when no remote exists (null for shallow clones - their truncated history has no stable root; sorted-first root when merged histories produce several). Not wired into any caller yet - this is the W1 foundation for the repoTelemetry registry.
by FrozenPandaz
Failed
36439
Flaky task→
7a997462 feat(core): derive stable repo key from normalized remote and relative path Adds deriveRepoKey: sha256(domain/slug + '#' + git-root-relative path), using getVcsRemoteInfo for protocol-independent remote normalization (ssh, https, and token URLs of one repo all yield the same key) and including the workspace's path inside the repo so nested workspaces get distinct keys. Falls back to the first-commit SHA when no remote exists (null for shallow clones - their truncated history has no stable root; sorted-first root when merged histories produce several). Not wired into any caller yet - this is the W1 foundation for the repoTelemetry registry.
by FrozenPandaz