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

Age	Commit message (Collapse)	Author
2020-05-21	[vcpkg] Remove powershell from the 'run vcpkg ci' path to reduce hangs from ↵	Billy O'Neal
	msys components. (#11512) * [vcpkg] Remove powershell from the 'run vcpkg ci' path to reduce hangs from msys components. * The BatchScript task uses filename rather than filePath * cmd hates BOMs * cmd hates forward slashes
2020-05-19	[vcpkg] Harden file removals and clean directory contents in "CI" inside ↵	Billy O'Neal
	vcpkg itself. (#11432) `files.h/files.cpp`: * Add end and else comments to all macros. * Add "remove_all_inside" function which empties a directory without actually deleting the directory. This is necessary to handle the case where the directory is actually a directory symlink. * Change remove_all to use std::remove when VCPKG_USE_STD_FILESYSTEM is set; this will engage POSIX delete support available on current Win10. `commands.ci.cpp`: empty "installed". `/initialize_environment.`: No longer clean the directories outside the tool. `ci-step.ps1`: Remove unused console output tee-ing.
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.