Vcpkg and integrating BullseyeCoverage in CI

[Jeremyvp]

Hi all!

I am trying to set up a test coverage pipeline in our CI but I'm having some problems with how vcpkg integrates into this. We want to use BullseyeCoverage to determine our test coverage and we have been using vcpkg in our VS project in manifest mode for a while now. Bullseye intercepts the call to the MSBuild which makes vcpkg detect a different compiler.

This would be fine if all the dependencies built out of the box with this setup. We would just store the additional binaries in the binary cache in the cloud and there would be no problem. One of our dependencies in vcpkg depends on Python and fails to build it only when Bullseye is active.

I'm looking for advice on how to proceed now since I'm stuck on this. I have already tried the following things:

• Use the VCPKG_DISABLE_COMPILER_TRACKING triplet variable to try and disable compiler information. This wouldn't be a bad solution for us, but even with this on it still seems to want to rebuild dependencies instead of getting them from the binary cache. Either it's not doing what I think it would, it I'm using it incorrectly.
• Use classic mode. This doesn't seem to work very easily when we're already using manifest mode for all other builds. It would mean maintaining another configuration and manually exporting and updating the built binaries.

Does anyone have any ideas or experience with this kind of issue?

[Osyotr]

Use the VCPKG_DISABLE_COMPILER_TRACKING triplet variable to try and disable compiler information. This wouldn't be a bad solution for us, but even with this on it still seems to want to rebuild dependencies instead of getting them from the binary cache. Either it's not doing what I think it would, it I'm using it incorrectly.

This should work. Although setting VCPKG_DISABLE_COMPILER_TRACKING for the first time will invalidate your binary cache.