Configure CI build for xplat

[AndyGerlicher]

CI build on xplat branch should:

1. Run unit tests.
2. Run on Linux.

Right now it's the same as on master which builds (using retail msbuild) and then rebuilds (using OSS msbuild).

@AndyGerlicher, will xplat and master always remain two separate branches or will there be reconciliation at some point? What about the feature disparity?

[AndyGerlicher]

For now we're not planning on merging platform specific changes back into master for shipping. And some features (like multi-proc) use Windows specific features (named pipes) that we don't have a plan to address right now. That's not to say we won't ever, we're in the planning phases for the MSBuild vNext project and cross platform / .NET Core won't be overlooked.

[mmitche]

@AndyGerlicher the build.pl doesnt' seem to work:

/home/ubuntu-vm/msbuild/src/MSBuild.sln: warning : /home/ubuntu-vm/msbuild/src/XMakeTasks/Microsoft.Build.Tasks.csproj: Expected a property at position 3 in condition "!$(Configuration.EndsWith('MONO'))". Missing closing parantheses'.

Am I missing some instructions?

Will it be configured on TravisCI?
There are many projects already hosted on TravisCI from Microsoft org on GitHub:
https://travis-ci.org/microsoft/
copy @akoeplinger

[mmitche]

I already configured builds of the xplat branch for windows on the .NET Jenkins instance (see comment above regarding the build.pl issue)
http://dotnet-ci.cloudapp.net/job/microsoft_msbuild_xplat/

[akoeplinger]

@mmitche build.pl works fine for me on Ubuntu.

[mmitche]

@akoeplinger okay it's been a while since I checked it out, so I'll take a look now.

[mmitche]

@akoeplinger Still getting the same issue. Do you have a special version of mono installed?

[akoeplinger]

@mmitche I'm running Mono 4.0.1 (the latest released version). The line in your error seems to be Microsoft.Build.Tasks.csproj#L3-L5, so maybe try removing it?

[mmitche]

@akoeplinger Okay it builds okay with 4.0.1 (but not with 3.2). Just verifying, do you get failures when you specify -all or -tests?

[akoeplinger]

@mmitche -verify works on Mono 4.1 which is currently in development (unfortunately there's a regression in 4.0 that affects Roslyn, so MSBuild fails to build itself). -tests shows a bunch of failed unit tests, I believe I've seen work happening to fix those.