Node.js build fails with no obvious error


I have a build using Node.js on Windows and it errors out immediately after nvs use but there’s no obvious error.

Current known issues — Please read this before posting a new topic

@michaelmior I had the same exact issue. Same as you I had an secure environment variable defined in settings:

Once I deleted the env var in my settings then the build went on as usual.
Of course I’m unable to deploy to Github but at least it’s documented now.
I’m able to set a non-secure env var though.

Hopefully Travis team is tracking these threads?


Thanks @hunterlester! I didn’t think to check any connection with the environment variables. In my case, testing on Windows isn’t really critical so I just set allow_failures for now and I’m hoping I’ll see it go green in the future :slight_smile:


I am getting the same error:
Is there any way I can fix it? I can’t get rid of the GH-Token variable because it is required to upload the builds to Github.


We are all sharing the same pain :crazy_face:


Have you tried to place the variable before the command that requires it?
Because that did the trick for me :wink:


@tibovanheule secure environment variables are set from the build settings on the UI.
Are you sure, you are using secure variables?


Hey guys

I am experiencing the exact same issue and can confirm, removal of the secure environment variable from the settings fixes the build however as @JannisX11mentioned this prevents automatically uploading builds to Github.

Can anyone on the Windows team comment on timeframe for a fix for this as its a real blocker in my opinion.


First thanks for starting Windows support on Travis!

I tried language: node_js but immediatelly running into an issue with nvs even before my first script command.

My .travis.yml looks like this

os: windows
language: node_js
services: docker

  - docker version
  - docker images
  - npm install -g rebase-docker-image
  - rebase-docker-image -h


Same problem :frowning: No fixes yet?