Skip to content
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

test: Try msvs-version: [2016, 2019, 2022] #2700

Merged
merged 3 commits into from
Jul 13, 2022

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Jul 13, 2022

Try testing on all MSVS_VERSIONs available in the GitHub Actions runner.

NOTE: I am not a Windows person so I might be doing this all wrong. ;-)

It is unclear to me what GYP_MSVS_OVERRIDE_PATH=C:\\Dummy' >> $Env:GITHUB_ENV does.

How can we prove that MSVS_VERSION is being used in the testing?

Checklist
  • npm install && npm test passes
  • tests are included
  • documentation is changed or added
  • commit message follows commit guidelines
Description of change

@cclauss
Copy link
Contributor Author

cclauss commented Jul 13, 2022

It is unclear to me what GYP_MSVS_OVERRIDE_PATH=C:\Dummy' >> $Env:GITHUB_ENV does.

How can we prove that MSVS_VERSION is being used in the testing?

@cclauss cclauss merged commit 68b5b5b into main Jul 13, 2022
@cclauss cclauss deleted the Try_msvs-version_2016,2019,2022 branch July 13, 2022 08:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants