-
Notifications
You must be signed in to change notification settings - Fork 41
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
Evaluate using Travis for Windows builds #204
Comments
To Do:
|
Seems to be working in beautifier-eslint: |
Awesome 🎉 The eslint Windows builds seem to be red, but only because of the CRLF situation. |
It's red on the PR build, not the branch build. |
What's different between them? The commit hash is the same. |
I'll try pushing everything as one commit and see if that makes a difference. Otherwise I think one is a standard commit while the other is a merge commit. |
The outcome seems to be the same :/ I just had a weird incident too, where something worked in Travis in a branch but not in a PR: Unibeautify/beautifier-clang-format#81 |
BTW, should Code Climate be run separately for each platform, or is it enough to run it on Linux only? |
It shouldn't matter. All it does it reports the coverage results of |
Ah, that makes sense. For reference, the Code Climate reporter is not available (pre-built) for Windows, only Linux and OSX: https://docs.codeclimate.com/v1.0/docs/configuring-test-coverage#section-locations-of-pre-built-binaries |
Yep, that's the second checkmark #204 (comment) |
Sorry, missed that one. |
👍I would greatly prefer Travis CI to AppVeyor. Let me know if you need anything from me. Sounds like you already have a plan and are making this a reality 🎉 ! Thanks! |
From the Travis CI blog: Windows is Available (Early Release) Oct 11, 2018
Found by @stevenzeck
The text was updated successfully, but these errors were encountered: