Add support for building on Mac about msbuild HOT 9 CLOSED

TravisCI has a waiting list for mac build runners; I'd go ahead and contact them to get on the list. Took us about 45 days to get our repo(s) activated for mac tests.

from msbuild.

@nathanaeljones the existing Jenkins CI already has mac and linux workers.

from msbuild.

Nice! Does it build pull requests automatically?

from msbuild.

Yes: http://dotnet-ci.cloudapp.net/job/microsoft_msbuild_prtest/ (it's just not hooked up to the mac and linux workers yet)

from msbuild.

Is there a guide for people who want to run CI against their own fork?

from msbuild.

@nathanaeljones I don't understand? You can do whatever you want in your fork, including setting up your own CI.

from msbuild.

Of course, but in practice it can be difficult to get a CI server set up to mirror the official version. The beauty of supporting Travis and AppVeyor is that the user only needs to flip a switch on their accounts, and their fork is automatically building. While my company could use a dedicated CI server, our users are better served by us maintaining .travis.yml and appveyor.yml files, as they can fork and experiment without losing the crucial benefit of CI. Of course, all of our projects are public OSS, so there aren't many downsides.

from msbuild.

Hmm, yeah that's a valid point, but in practice I think it's not that difficult to set up your own CI as this repo has very few dependencies (i.e. cloning the repo and running build.cmd should be enough).

from msbuild.

MSBuild team triage: Closing because Mac support is now in. Eventually we'd like to get Mac CI support, but Linux will come first.

from msbuild.