Terrapin onboarding

[danieljurek]

Onboard packages (probably):

abseil
azure-c-shared-utility
azure-macro-utils-c
curl
nlohmann-json
openssl
opentelemetry-cpp
umock-c
vcpkg-cmake-config
vcpkg-cmake-get-vars
vcpkg-cmake
wil
zlib

Instructinos for terrapin onboarding tool to run from dev context: https://eng.ms/docs/coreai/devdiv/one-engineering-system-1es/1es-docs/secure-supply-chain/oss-supply-chain-security/vcpkg

[antkmsft]

The instructions that I used and suggest are:

For every error such as below during the "cmake generate" step,

error: Not a transient network error, won't retry download from https://vcpkg.storage.devpackages.microsoft.io/artifacts/{SHA512}
error: there were no asset cache hits, and x-block-origin blocks trying the authoritative source {URL}

Go to https://devpackages.microsoft.io/vcpkg, and enter {URL} and {SHA512} into the form, (probably ignore the "oops, something went wrong" error - it doesn't seem to mean there will be a problem), then wait until https://vcpkg.storage.devpackages.microsoft.io/artifacts/{SHA512} gives you a successful download, then restart the CI failed build to get the next error, and keep going like this until all the cache misses are fixed. We don't have that many dependencies, especially those that won't be in the devpackages.microsoft.io cache already, probably should be 2-3 libraries you need to update this way.

It is not the most technological solution, but you can do it in background while doing someting else, and you don't need to install anything on your dev machine. The instructions that Terrapin tool has do not directly translate into the type of project that we have, not to go to much into details, so I found it easier to update via the page. If someone figures out a better way of doing this per Terrapin instructions, or at least a way they prefer more, that's great - I wouldn't insist that the way I did it is the only and the right way. Or, if at some point we have so many cache misses, that manual update on iterative basis does not really work, then sure, Terrapin tool could be the right way of doing this.

This will be needed only when adding new dependencies for the C++ repo (typically happened once every 1-3 years), as well as when updating vcpkg baseline.
It is possible there won't be any misses at all. We do typically update vcpkg baseline every 1-3 months.

[antkmsft]

Daniel Jurek (@danieljurek), I have updated Terrapin's vcpkg cache. I've ran 9 pipelines for #7214 - for all the services that we have, and as of now, there isn't a pipeline that fails on a "cmake generate" step as before, due to a Terrapin cache miss. All the pipelines that fail (be it Linux, Windows_libcurl, Windows_WinHTTP, or Mac), they fail after the "cmake generate" step due to subsequent reasons - i.e. error fetcing nuget when testing AMQP. You're working with Larry Osterman (@LarryOsterman) on that. This issue is fixed.