Skip to content

Conversation

kangas
Copy link
Contributor

@kangas kangas commented Sep 3, 2015

Tested here:
https://evergreen.mongodb.com/version/55e7d1683ff122654400006f_0

Windows log says:

 [2015/09/03 00:51:49.286] npm --version
 [2015/09/03 00:51:49.676] 3.3.1

OS X log says:

 [2015/09/03 00:56:59.158] npm --version
 [2015/09/03 00:56:59.385] 2.11.3

Windows build fails only because installer_filename is still wrong in this branch; fix is in fix-windows. EDIT: I added the fix here and reverted .evergreen.yml changes in fix-windows.

I tried using the npm-windows-upgrade module from Microsoft but that requires an administrative shell; we don't have that during our build runs.

npm-windows-upgrade seems to be the optimal approach to incorporate into the builder images.

@kangas
Copy link
Contributor Author

kangas commented Sep 3, 2015

Test build with installer_filename fix:
https://evergreen.mongodb.com/version/55e849463ff1226544000152_0

imlucas added a commit that referenced this pull request Sep 5, 2015
INT-582 fix(windows) Evergreen upgrade npm on Windows
@imlucas imlucas merged commit 1b2ca92 into master Sep 5, 2015
@imlucas imlucas deleted the evergreen-npm-3 branch September 5, 2015 06:49
gribnoysup pushed a commit that referenced this pull request Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants