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

Start using travis for windows CI builds instead of AppVeyor #795

Open
eteran opened this issue Dec 21, 2020 · 6 comments
Open

Start using travis for windows CI builds instead of AppVeyor #795

eteran opened this issue Dec 21, 2020 · 6 comments

Comments

@eteran
Copy link
Owner

eteran commented Dec 21, 2020

Travis CI has robust windows support, and better Github integrations. Would be nice to have it all in one place to keep things simple.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@eteran
Copy link
Owner Author

eteran commented Dec 31, 2020

Looks like Windows support in Travis CI is still "beta", so we'll hold off on this until it's ready on their end.

@10110111
Copy link
Contributor

If only to use one service for all, maybe switch to AppVeyor for all platforms?

@eteran
Copy link
Owner Author

eteran commented Dec 31, 2020

Maybe, to be honest, I like Travis's integrations with GitHub a little better. It's generally a smooth experience. But I'll definitely look at AppVeyor again to see if it's worth just switching to that exclusively.

@ped7g
Copy link

ped7g commented Jan 1, 2021

If you are going to research CI services, I would somewhat-recommend https://cirrus-ci.org/
(although I'm fighting with their windows images containing different set of things every now and then, and as I don't have any windows machine around, it's always kinda pain to understand what went wrong, and especially what is the correct way to fix things and which binaries are now missing or have different path.. also it doesn't help I rely on the regular GNU/POSIX stuff and take all of that for granted ... and my overall lack of knowledge how to work with these cloud VM systems effectively)

I'm using it to build sjasmplus, with the main config looking like this:
https://github.com/z00m128/sjasmplus/blob/master/.cirrus.yml
Particular build details on Cirrus side:
https://cirrus-ci.com/build/4770338804334592
corresponding Github commit (the results are under the red-X failure icon):
z00m128/sjasmplus@7f65674

(I hope you will consider this rather informal than spam/promo of other project :) )

@eteran
Copy link
Owner Author

eteran commented Jan 1, 2021

Thanks for the heads up :-)

@eteran
Copy link
Owner Author

eteran commented Jan 1, 2021

@ped7g I quick look and one thing I can say is that I like that I can just pick what kind of docker container to run the CI script in... that's a feature I've wanted from travis for while (you can do it.. technically with travis, but it isn't easy and has quirks).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants