-
Notifications
You must be signed in to change notification settings - Fork 341
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
Get up and running on Appveyor #174
Comments
Despite this being closed, AppVeyor builds do not pass tests right now due to several issues. After a break, I just wanted to continue working on this again, but I realized @xtreme-vikram-yadav removed the So, what's the plan going forward to support CI on Windows? If the plan is to exclusively use Concourse in the future, does that support Windows? |
Concourse does support windows. Not sure what @kdykeman and team are planning for here, but I'd like to refactor the concourse setup to use https://github.com/flavorjones/concourse-gem and a windows worker like the pipelines at https://ci.nokogiri.org. |
Interesting. From what I understand, Concourse requires self-hosting, and there's no public service for OSS projects like for Travis / AppVeyor, correct? In any case, I'll submit my fixes to make tests pass on Windows in general. |
Also correct. The tradeoff, though, is that you get a ton of flexibility in how and what you run in the pipelines. I'll point again at https://ci.nokogiri.org/ in which Nokogiri is tested under a wide range of situations, including under valgrind; on windows; and (not publicly visible) on OSX. This flexiblity is occasionally necessary and useful. For example, on LicenseFinder, we found it extraordinarily difficult to set up a working erlang/elixir environment on Travis to support merging #261. That path is now open to us with Concourse. |
There is a story to stand up a windows concourse worker, but we haven't gotten to it yet. I have to admit, I was somewhat hoping to see a PR come in from others for that. |
@kdykeman I can PR a windows test task into the pipeline. It's on my TODO list. |
More Windows test fixes are in #294. I believe there's only one more issue on Windows, but I'll double-check one Concourse is running on Windows. BTW, I have some local improvements to |
If you have changes to But Appveyor is limited in the same ways that Travis is, and so we may have to run an abbreviated test suite on those platforms once we pull in additional support (like erlang/elixir above). |
The "problem" with my |
@sschuberth we finally got around to adding a windows worker to our concourse deployment - sorry for the delay. The tests are currently failing so we're not yet gating pull-requests on that job passing. I'm guessing the failures are mostly around shelling out and shell brace expansion. Not being terribly windows savvy, I'm wondering if you'd be interested in helping out with getting that job to go green? You can see the output for a recent run at https://osl.ci.cf-app.com/teams/main/pipelines/LicenseFinder/jobs/ruby-2.3-windows/builds/3 |
Excellent! Very much appreciated! |
@kdykeman, I've figured out why the Bower feature test fails on Windows, but I'm unsure how to solve it. On Windows I get
So |
@kdykeman Any comment on my |
@sschuberth Sorry, I missed your |
Appveyor allows us to test for Windows support, to avoid problems like the one solved by #173.
The text was updated successfully, but these errors were encountered: