Use preview queues for internal build

[pranavkm]

The preview queue has VS 16.7 p5 which allows builds in master to run successfully.

[Pilchie]

Can we kick off an internal build on this branch to ensure that it actually works?

[pranavkm]

Already done and verified that it works: https://dev.azure.com/dnceng/internal/_build/results?buildId=761862&view=logs&j=1b89928a-2219-5ef9-602f-f95beb3da4dc&t=b8e57a46-4a1c-5752-600e-7a395fe90fb9

[pranavkm]

For future reference, the Prerelease Server queues were removed to save capacity. We can \ should switch back to Server once 16.7 or newer is available in the non-PRE queues.

[dougbu]

We shouldn’t check this in. Intent was to confirm 16.7 was new enough

________________________________ From: Pranav K <[email protected]> Sent: Friday, August 7, 2020 13:34 To: dotnet/aspnetcore <[email protected]> Cc: Doug Bunting <[email protected]>; Review requested <[email protected]> Subject: Re: [dotnet/aspnetcore] Use preview queues for internal build (#24683) @pranavkm commented on this pull request.

________________________________ In .azure/pipelines/jobs/default-build.yml<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.8713187.xyz%2Fdotnet%2Faspnetcore%2Fpull%2F24683%23discussion_r467256301&data=02%7C01%7CDouglas.R.Bunting%40microsoft.com%7C95b8e1f80ded461d4a2c08d83b114159%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637324292579881698&sdata=EenHrubvQy4KreDU1ZNYu1gBHYNn2IeMj3uBVKYQuDo%3D&reserved=0>:

@@ -115,7 +115,7 @@ jobs:

${{ if eq(variables['System.TeamProject'], 'internal') }}: name: NetCoreInternal-Pool # Visual Studio Enterprise - contains some stuff, like SQL Server and IIS Express, that we use for testing - queue: BuildPool.Server.Amd64.VS2019 + queue: BuildPool.Windows.10.Amd64.VS2019.Pre For future reference, the Prerelease Server queues were removed to save capacity. We can \ should switch back to Server once 16.7 or newer is available in the non-PRE queues. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.8713187.xyz%2Fdotnet%2Faspnetcore%2Fpull%2F24683%23pullrequestreview-463595002&data=02%7C01%7CDouglas.R.Bunting%40microsoft.com%7C95b8e1f80ded461d4a2c08d83b114159%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637324292579881698&sdata=Vxs6lg4tC5LSgM6GIwBvn6SKwIqY01DgSyR5rmipKFQ%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.8713187.xyz%2Fnotifications%2Funsubscribe-auth%2FABRCFPP7YJ5FYD3CWAPVQ2DR7RQMRANCNFSM4PX6GM2A&data=02%7C01%7CDouglas.R.Bunting%40microsoft.com%7C95b8e1f80ded461d4a2c08d83b114159%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637324292579891698&sdata=eCSdWTcuHHukbE1G8wCBvnnsDuH6%2BbtkAAW5AzvxRas%3D&reserved=0>.

[pranavkm]

@dougbu is there a reason to not use this until such a queue becomes available? The build appears to pass.

[pranavkm]

I spoke to @MattGal offline and he recommends using this as long as it works for us. We should of course work to switch to a more appropriate queue once available.