Windows CI Setup

[jfdm]

Currently we use travis to provide CI testing for Idris on Linux boxes, this has the nice side effect of CI for Mac OS X. It would be nice if we can provide CI testing for Windows machines.

This is not my idea @david-christiansen has mentioned it a few times, and I am in full agreement. AppVeyor seems to be a suitable candidate and a cursory glance implies that the Build Instructions and Scripts for Windows can be adapted accordingly. Whether AppVeyor is the best (or maybe only) Windows CI service is another matter.

[david-christiansen]

AppVeyor seems to be what the F# folks use, in any case, and it seemed the most Travis-like when I looked at it before.

[jfdm]

Actually, I agree with AppVeyor but you know devils advocate...

[Cynede]

Also it will be glad to repair make test_c , related issue: #1936

[LeifW]

There's also http://win-builds.org. Maybe it's focused more on packaging than CI?

[enolan]

I'm working on this. Stuck on commercialhaskell/stack#1482

[ahmadsalim]

@enolan Thanks for the effort so far, is there any way one could try to work around the bug you are stuck on?

[enolan]

I'm actually past that and stuck on a different bug :) I've been stubbornly
trying to fix a problem with Stack where it intermittently hangs for a long
time now. Turning off concurrent builds might be a workaround. If so, I'm
all but done. I'll look into it.

On Tue, Apr 12, 2016, 1:17 PM Ahmad Salim Al-Sibahi <
notifications@github.com> wrote:

@enolan https://github.com/enolan Thanks for the effort so far, is
there any way one could try to work around the bug you are stuck on?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1948 (comment)