Closed
Description
- Version: *
- Platform: Windows
- Subsystem: *
Tracking issue
Goal: get node
compiling with VS2017 and passing all tests
- bump
GYP
(tools: bump gyp to eb296f6 #12450)adjust build scripts (win: enable build with vs2017 #11852)pass all testscreate CI target
breakdown of CI task by @joaocgreis:
- adjust build scripts (win: enable build with vs2017 #11852)backport build scripts (tools: bump gyp to eb296f6 #12450 (comment))update npmcreate Ansible script ([WIP] win: add a "VS2017 Build Tools" playbook build#708)set up Jenkins slaves (Rackspace win2012r2 10, 11 and 12)add VS2017 to Jenkins jobs (done for node >= 8)
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
refack commentedon May 16, 2017
/cc @nodejs/lts is it a goal for porting? (re: #12450 (comment) and following comments)
joaocgreis commentedon May 16, 2017
I'm going to move forward with that.
I ran the tests with master when we started adding support and everything passed. Didn't try recently though. Re #12450 (comment), can you paste the errors you get here?
refack commentedon May 16, 2017
I guess there's something wonky with symlinks on my machine.
parallel\test-module-circular-symlinks
sequential\test-benchmark-http
addons/symlinked-module/test
joaocgreis commentedon May 23, 2017
Added VS2017 to
node-test-commit-windows-fanned
, but only for Node >= version 8 and onlly for the compiling stage (i.e., not for testing addons, that is blocked until npm is updated with a recent version of node-gyp).Current status:
GYP
(tools: bump gyp to eb296f6 #12450)refack commentedon May 23, 2017
@joaocgreis 👍
I copied your list into the first comment.
sam-github commentedon Sep 19, 2017
What is the specific question that is on the LTS agenda for this issue?
42 remaining items