Re-enable FreeBSD builds once core-setup is building for FreeBSD again

[dsplaisted]

See #246 (comment)

We will disable FreeBSD builds for now, and need to re-enable them once we have FreeBSD builds from core-setup.

[dagood]

I added the FreeBSD leg back to core-setup and got this official build: https://dev.azure.com/dnceng/internal/_build/results?buildId=70295&_a=summary.

However, after this issue was filed, the public pool of FreeBSD agents was removed, so you might not want to take action on this issue yet. /cc @livarcocc

Edit: Core-Setup FreeBSD legs are currently disabled. (2019-2-4)

[am11]

Any news on this? The preview5 FreeBSD builds would help in order to make progress on issues such as https://github.com/dotnet/corefx/issues/2046 (currently we are stuck with old build: 009812).

the public pool of FreeBSD agents was removed

@dagood, related to that, there is a new~ish public CIaaS offering for FreeBSD by CirrusCI (since Dec 2018), that runs on Google Cloud Platform, which supports FreeBSD public agents (since May 2018). Would be rad if Azure Pipeline also add FreeBSD (and other BSDs) agents to fill the gaps.

[dagood]

Not really. 😞

Maybe you should track https://github.com/dotnet/core-setup/issues/5083 if Core-Setup builds are enough to make progress. In Core-Setup I think we're more ok with adding a leg that can only be tested in internal builds to get things unblocked and keep the effort alive. In Core-SDK there's a stronger desire to have public PR validation for FreeBSD if the platform were added.

Just to be sure, you're only mentioning CirrusCI FreeBSD as a comparison, right? There's a ton of infra behind what AzDO can provide, so while that's definitely something we want, it's not easy to get.

[davidchisnall]

Any updates on this? There are a number of open FreeBSD-related issues, but it's really hard for anyone to contribute to them until they can at least build locally.

[Thefrank]

Any news on this or should I be asking this over at dotnet/runtime#3443 ?

[dagood]

I think dotnet/runtime#14537 is the biggest thread about this, and most likely to be active/up to date. Based on the title, it tracks getting actual support, not just builds out the door, but I think this is mostly a technicality and the status of both will probably be found/discussed there.

(dotnet/runtime#3443 is about a smallish piece of infra and I doubt anyone subscribed to it will necessarily have new info, even though it technically tracks the work to produce the shared framework builds.)

/cc @NikolaMilosavljevic @dleeapho

[marcpopMSFT]

Old issue triage: we believe that source build already covers this.

[marcpopMSFT]

dotnet/source-build#1139