Open tschaffter opened 11 months ago
Nx says when running the CI workflow:
NX No access token found
Nx will continue running, but nothing will be written or read from the remote cache. Run details will also not be available in the Nx Cloud UI.
This message is printed for a PR, which is normal as PRs don't have access to GitHub secrets. This message does not appear when the CI workflow runs on main
.
This item has been pushed from the CI workflow for main
: the item show that 2 CPU cores were available while other items show that 8 CPU cores are available (when run in my dev container).
But the branch name is not captured properly. Maybe this can be fixed with an env var passed to the dev container.
Added to Sprint 23.10
Is there an existing issue for this?
What projects are you seeing the problem on?
No response
Current behavior
There are a few issues/questions with Nx Cloud:
main
.Expected behavior
No response
Anything else?
No response
Commit ID
No response
Are you developing inside the dev container?
Code of Conduct