Repository navigation
Setup Windows CI #92
Description
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
Activity
jkuri commentedon Mar 4, 2016
I successfully configured the Windows CI.
I must say that appveyor works fine, the only problem is that builds are not running concurrently and the build time exceeds 20min as I configured x86 and amd64 arch for both node versions. Otherwise appveyor really is a Travis CI for Windows environment as they are saying on their webpage. If we use their plan then 2 concurrent jobs are guaranteed, I think, and then build time will be similar to the one we now have in Travis CI.
Here is the history of my test builds and here is the configuration I used.
/cc @hansl
hansl commentedon Mar 4, 2016
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).
hansl commentedon Mar 10, 2016
I can close this now. This was done with PR #275. Thanks jkuri!
angular-automatic-lock-bot commentedon Sep 5, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.