-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NX Cloud agent: dotnet is not installed - setup-dotnet action is ignored #27558
Comments
can concur, this happens to me as well: https://github.com/EelcoLos/nx-tinkering/actions/runs/10520973969/job/29150814666 and |
@EelcoLos I'm pretty sure it's currently just not supported. I did see a topic there about Docker, which could solve the problem, but that's Enterprise only at the moment. |
if we look at https://github.com/nx-dotnet/nx-dotnet/blob/master/.github/workflows/pr.yml & https://github.com/nx-dotnet/nx-dotnet/blob/master/.github/workflows/main.yml, we can see which workflows are used there and are possible now. Still, the question remains. Edit: Also, a while ago on a stream, there was mention of Launch Templates: https://nx.dev/ci/reference/launch-templates @roldengarm |
@EelcoLos ah, didn't see the nx-dotnet templates! This is not documented I believe. /edit: @EelcoLos that works indeed! I had to swap dotnet install and npm install but that's fine. |
Correct! You'll need to define your own custom launch templates to use dotnet in Nx Agents. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
My repo depends on .NET as we're using nx-dotnet.
I'm starting a ci-run on 8 linux-medium-js and then have below two actions
Then, npm ci fails, as dotnet is not installed on the runner:
Expected Behavior
It installs dotnet on the agent before running npm ci
GitHub Repo
No response
Steps to Reproduce
npm ci
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
I guess another workflow action has to be added to this repo?
Or alternatively, can we customise the docker image used for the runner?
The text was updated successfully, but these errors were encountered: