miel.truyen/nx
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs(nx-cloud): add tip to check for non-unique NX_CI_EXECUTION_ID on DTE failures (#27573)

Browse Source 
I ran into this issue the other day with my CI pipeline when the build
number got reset

Co-authored-by: Altan Stalker <altan@nrwl.io>
This commit is contained in:
Michal Jez 2025-05-14 13:39:33 -04:00 committed by GitHub
parent f6d69baf14
commit 47b9b51dd3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/nx-cloud/troubleshooting/ci-execution-failed.md
View File

@ -20,6 +20,8 @@ Nx Cloud provides two commands to forcibly stop agents, [stop-all-agents and com
Once these commands are invoked, the current CI Pipeline Execution is closed and can no longer receive new work. Once these commands are invoked, the current CI Pipeline Execution is closed and can no longer receive new work.
If this error occurs at the beginning of a CI Pipeline Execution it could be caused by a non-unique [NX_CI_EXECUTION_ID](/ci/reference/env-vars#nxbranch-and-nxciexecutionid) that is causing Nx Cloud to associate this CIPE with a CIPE that has already concluded.
### Nx Cloud agents were stopped due to an error ### Nx Cloud agents were stopped due to an error
Nx Cloud detected a failed task in the current CI Pipeline Execution and has halted further execution. Nx Cloud detected a failed task in the current CI Pipeline Execution and has halted further execution.