Skip to content
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

Environment details is empty and node is not found #1210

Open
2 of 5 tasks
ValentinVignal opened this issue Jan 30, 2025 · 2 comments
Open
2 of 5 tasks

Environment details is empty and node is not found #1210

ValentinVignal opened this issue Jan 30, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ValentinVignal
Copy link

Description:

It seems like node is not installed after using the action. Unfortunately, I cannot provide a reproductible example or a link as my company's repository is private.

After running

- uses: actions/checkout@v4
- uses: actions/setup-node@v4

when I try to use node, I get the error node: command not found.

Also, the logs about environment details seem empty:

Environment details
  node: 
  npm: 
  yarn:

I might be missing something or it might be because of my company's repos rules/set up.

What could it be ?

Action version:
v4

Platform:
I'm not sure as I don't have access to the details of the image but I think it would be Ubuntu

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:

Repro steps:
A description with steps to reproduce the issue. If you have a public example or repo to share, please provide the link.

Expected behavior:
A description of what you expected to happen.

Actual behavior:

The logs seems empty (look at Environment details)

Run actions/setup-node@v4
  with:
    always-auth: false
    check-latest: false
    token: ***
  env:
    PATH: ***
Run '/home/runner/k8s/index.js'
  shell: /home/runner/externals/node {0}
Environment details
  node: 
  npm: 
  yarn:

I get the error

node: command not found

@ValentinVignal ValentinVignal added bug Something isn't working needs triage labels Jan 30, 2025
@mahabaleshwars
Copy link

Hi @ValentinVignal,
Thank you for creating this issue. We will investigate it and provide feedback as soon as we have some updates.

@gowridurgad gowridurgad self-assigned this Jan 31, 2025
@gowridurgad
Copy link

Hi @ValentinVignal, We were unable to reproduce the issue on the provided workflow. The environment fields are populated correctly. Please see the screenshot below for reference.
Here are some troubleshooting steps you can follow:

  1. Verify Node.js Version: Ensure that the node-version parameter is specified correctly in the workflow file.
- uses: actions/setup-node@v4
  with:
      node-version: '21' 
  1. Check PATH Configuration: Ensure the PATH environment variable includes the path to the node binary. Add a step to print the PATH variable:

- run: echo $PATH

If the issue persists and you are unable to provide a reproducible link, please share your workflow file with the relevant configuration for further assistance.

Additionally, could you please confirm whether you are using a GitHub-hosted or self-hosted runner? If you are using a GitHub-hosted runner, even if you do not pass the node version, you will get the default values.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants