[Mono-dev] Windows builds

[David Nelson]

I'm with you. I have been quite disheartened by the state of CI (or lack thereof) for Mono, and especially the seemingly constantly broken state of the Windows build. I haven't wanted to put much effort into fixing the build because there hasn't seemed to be much of a commitment to keeping it working. But lately there seems to be more awareness of the problem, so maybe now is the time.

> On Oct 16, 2014, at 2:33 PM, Bryan Crotaz <bryan.crotaz at silvercurve.co.uk> wrote:
> 
> I have a Windows CI cloud service running (Elastic Bamboo). If it helps get Windows development going so that I can get in and fix mono bugs when I find them, I'd be happy to sponsor running a nightly build and test of mono on a clean Windows box. Let's say for 12 months to start with and see where we go.
> 
> However... I don't have time (or experience - I've tried and failed) to get the build running in the first place.
> 
> If someone can get the repo to a point where there's a build script that runs as a single step and a separate test script which runs the (nunit?) tests, then I can get that set up as a nightly build and get it publishing the results out to the web somewhere. It can do all the usual "which tests broke" stuff and report whose changes broke it. If we feel flash with cash we can run it against pull requests too.
> 
> Who's with me?
> 
> Bryan
> 
> -- 
> Bryan Crotaz
> Managing Director
> Silver Curve
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list