{"author":"Viktor Szakats","author_email":"commit@vsz.me","author_time":1745685459,"commit_time":1745948155,"committer":"Viktor Szakats","committer_email":"commit@vsz.me","hash":"fd4c342d8863b77bb82a5e12af6304a2865dbe45","message":"GHA: drop vcpkg cache and most vcpkg logic with it\n\nThe unplanned dropping of the granular vcpkg binary cache indeed fell\ninto the cracks between Microsoft's various departments. The old method\nis now official dropped, without replacement either on the vcpkg side or\nthe GitHub cache provider side.\n\nWithout a granular cache, vcpkg is impractical for builds larger than\na small dependency tree in CI, for performance reasons.\n\nA granular cache is critical for CI use. Building dependencies is not\na goal of this CI, so a more desirable option would be pre-built binary\ndownloads. This would also allow keeping job timeouts low, which is\nimportant for quick iteration in GHA when a flaky job requiring a manual\nretry needs all other jobs to finish first. (GHA often disregards\nstep timeouts, which is another contributing factor here.)\n\nWindows remains tested extensively with MSYS2, curl-for-win, and via\nAppVeyor CI with MSVC + OpenSSL, and also in GHA via scaled back vcpkg\njobs that perform well without caching. What's lost is the recently\nadded Android OpenSSL build tests.\n\nWe may consider building/cachine important dependencies manually as in\nGHA/linux-http3, and/or try integrating MSVC jobs with MSYS2 UCRT DLLs.\n\nRef: https://github.com/microsoft/vcpkg-tool/pull/1662\nRef: https://github.com/microsoft/vcpkg/issues/45073\n\nFollow-up to cd0ec4784c1c0f873939f33ec1a73c8739f276b9 #17089\nFollow-up to e3912f0f9fac06d37cd1ab93cef4f01f33809f0b #17086\nFollow-up to 15fb1dc7f86ad1832e0386ec7d92542f44ee9c44 #17069\n\nCloses #17200\n","parents":["9daca35b136d5036ea0e7d590f782847786cf83f"],"tree_hash":"35ea93102544b032307353cf32140b5fd6394a11"}