-
Notifications
You must be signed in to change notification settings - Fork 167
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
Windows Updates #2099
Windows Updates #2099
Conversation
@@ -34,6 +37,9 @@ Supported versions for building Node.js from source. | |||
| v9 | 2015, VCBT2015, 2017 | | |||
| v10 | 2017 <sup>[5]</sup> | | |||
| v11 | 2017 | | |||
| v12 | 2017, 2019 (flag) <sup>[8]</sup> | | |||
| v13 | 2017, 2019 <sup>[9]</sup> | | |||
| v13 | 2017, 2019 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this line supposed to be v14
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, fixed, thanks!
Following Azure security recommendations.
Specific commit and floating PRs known to work.
e8669b1
to
88c5ec6
Compare
Added a commit to install CMake (#2097) and rebased. |
It's not part of the Native Desktop Workload for Visual Studio? We have https://ci.nodejs.org/job/libuv-test-commit-windows-cmake/ already running in the CI. |
As I understand it, using CMake from VS is a bit of an hack. Needs to be accessed by full path, so location will change with VS version. Also, it's not present in VS2015. Having it from Chocolatey should be a better option, more so if we start using it to build Node at some point. |
|
||
# Retry once | ||
git archive --format=tar --remote="$TEMP_REPO" $TEMP_BRANCH src/node_version.h -o node_version.h.tar || | ||
git archive --format=tar --remote="$TEMP_REPO" $TEMP_BRANCH src/node_version.h -o node_version.h.tar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is interesting, fetching a single file from a remote repo? I get protocol problems trying this out locally so can't seem to replicate this behaviour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also had issues with http repos, but this works for our temp repo (ssh). This is already being used by node-test-commit-windows-fanned (running in jenkins-workspace).
[ /vs2019-x86$/, testType, lt(14) ], | ||
// VS versions supported to build add-ons | ||
[ /vs2013-COMPILED_BY/, testType, gte(9) ], | ||
[ /vs2015-COMPILED_BY/, testType, noVer ], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 good idea to include these with noVer
for completeness and documentation purposes, I like
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hard to grok too much of this without better knowledge of windows & ansible+windows and a bunch of other stuff in here so this is mostly a rubber-stamp. Some comments inline, nothing major blocking, except maybe the pip2 vs pip3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very impressive work! Thanks much!
# TODO: Ensure no other versions are installed | ||
- name: install Visual Studio 2013 | ||
include_tasks: "partials/vs2013.yml" | ||
- name: install Visual Studio 2013 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still want to test and support 2013? https://docs.microsoft.com/en-us/visualstudio/releases/2019/servicing#support-for-older-versions-of-visual-studio
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
VS2013 is used to test add-ons for Node.js v8. We should keep the machines available for some time after a Node version goes EOL, but anyway I'd like this to be in the commit history for documentation (we might need to test an old issue or something).
Thanks for the reviews! This needs some work to land, iojs+release needs to have the same changes as the test release job, and the jobs in CI need to be changed to point at master. I'll do it later this week. |
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
Following Azure security recommendations. PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
Specific commit and floating PRs known to work. PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
PR-URL: #2099 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Christian Clauss <cclauss@me.com>
Thanks! Adapted the jobs on both Jenkins instances. Landed in 1dd97fa...36202a2 |
This is all already in use by CI, but not yet by the release Jenkins. The release job need to be adjusted while landing this.
Notable changes:
Re-created all Windows machines to balance available versions optimizing for current master.
Refs: #1996