-
Hello, I am migrating CI from travis to actions and I am having problems using nvm.
My action and script look like this: workflow.yml:
.build.sh:
What am I doing wrong here, how do I use the image provided nvm in my script? Edit: The version (as of making this edit [16 April 2020]) is old, there have been 3 tagged newer releases. |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
I have reported this ticket to the appropriate engineering team for further investigation and evaluation. If they have any progress, I will notify you in time, and sometimes the appropriate engineers may directly reply you here. |
Beta Was this translation helpful? Give feedback.
-
Hello, We have confirmed the issue. New image with NVM was not deployed to some VM machines / pools. Looking at it |
Beta Was this translation helpful? Give feedback.
-
Thanks @brightran I have updated my original post with some more details. Is there anything I can do other than wait for updates to be rolled out - is there anywhere I can see progress and/or what possible versions my action could be run on |
Beta Was this translation helpful? Give feedback.
-
Hello, |
Beta Was this translation helpful? Give feedback.
-
The engineering team has fixed this issue. I checked with the following scripts, and I can confirm the nvm command can work fine on the GitHub-hosted runners now.
Could you please also check this on your side? Any progress, feel free to tell us. |
Beta Was this translation helpful? Give feedback.
-
Thanks, nvm is now working! |
Beta Was this translation helpful? Give feedback.
-
Thanks, nvm is now working for me |
Beta Was this translation helpful? Give feedback.
-
Gh-hosted runners have nvm now? Thank you! I can finally get rid of the |
Beta Was this translation helpful? Give feedback.
-
Hi! Please, is it still working for you? It’s available according to the list of sw: https://github.com/actions/virtual-environments/blob/ubuntu18/20200604.1/images/linux/Ubuntu1804-README.md However, I’m getting I looked at the HOME directory and
However it doesn’t recognize all the available Node versions according to the list of sw:
Thanks in advance! |
Beta Was this translation helpful? Give feedback.
@lidbetter ,
The engineering team has fixed this issue.
I checked with the following scripts, and I can confirm the nvm command can work fine on the GitHub-hosted runners now.
Could you please also check this on your side? Any progress, feel free to tell us.