-
Notifications
You must be signed in to change notification settings - Fork 12k
Setup Windows CI #92
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
Comments
I successfully configured the Windows CI. /cc @hansl |
Good job! It's really nice to see this. Look at the results, there's absolute no reason why we should run both x86b and x64 versions of the CLI tests. Also, we could be more severe with Windows and not run the tests on Node 4, telling people they need node 5 or above for better support. Let's chat on Slack for the next steps with this (ie. submitting it to the repo and making it required for PRs to get green). |
I can close this now. This was done with PR #275. Thanks jkuri! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
We should setup appveyor or something similar to run an e2e test on windows. Travis does not support windows VMs.
http://www.appveyor.com/docs/lang/nodejs-iojs
Once setup we should use it to run end-to-end test suite: #90
The text was updated successfully, but these errors were encountered: