vcpkg - Forked from https://github.com/microsoft/vcpkg

Age	Commit message (Collapse)	Author
2020-05-06	[vcpkg] Add tombstone deletion scripts. (#11189)	Billy O'Neal

2020-05-04	[vcpkg] Add disk space report on Linux and MacOS. (#11166)	Billy O'Neal

2020-04-30	[OpenBLAS] Upgrade to 0.3.9 + a patch to fix AVX512 (which is now present on ↵	Billy Robert O'Neal III
	the VMs)
2020-04-30	[vcpkg] Onboard Linux to VMSS, open 'git' port, and switch back to Azure Spot	Billy Robert O'Neal III
	* Adds scripts to generate scale sets for testing Linux. * Note workaround for https://github.com/microsoft/azure-pipelines-agent/pull/2929 * Switches Windows validation to 'Spot' VMs. * Opens the git port 9418. * Removes provisioning of the no longer used 'logs' file share. * Changes Azure region to 'westus2', which is cheaper. * Adds +x to all the scripts in scripts/azure-pipelines. * Use 'xml-results' for all platforms instead of 'raw xml results' on Windows.
2020-04-29	Bump macos build timeouts. (#11090)	Billy O'Neal

2020-04-28	[vcpkg] Copy macos pipelines into azure-pipelines.yml	Billy O'Neal

2020-04-22	WIP	Billy Robert O'Neal III

2020-04-21	Change supporting infrastructure to use Azure Virtual Machine Scale Sets for ↵	Billy Robert O'Neal III
	vcpkg's PR builds, which should both improve our PR build times and reduce Azure spending by shutting down machines when they aren't being used. Included is a script that sets up all vcpkg's Azure infrastructure for Windows PR tests, and several updates to baselines. The baseline updates are generally caused by an updated copy of the MSVC++ compiler caused by updating the VMs, but some are caused by missed failures only detected now because this did a cleared out archives directory first. Some of the build infrastructure isn't what I'd call 'pretty' (e.g. we're split into more scripts and such than I'd like) but this mirrors how our existing PR system works. It is expected that the existing vcpkg Windows PR system will hate these baseline updates so we'll need to merge this, then remove that (duplicate) workflow immediately afterwards, then delete all the Windows VMs powering the old infrastructure.