It may make more sense to add the Craft Windows job instead of the Windows CI job because the latter doesn't use Craft, so that everything you did for Craft doesn't help with the Windows CI.

In rLIBKLEO6be67ced16872c2510b6a425bcbda04f2596c671#81774, @ikloecker wrote:

It may make more sense to add the Craft Windows job instead of the Windows CI job because the latter doesn't use Craft, so that everything you did for Craft doesn't help with the Windows CI.

Are you sure? As far as I can see the Windows CI job are using this definition https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/windows.yml?ref_type=heads#L14 which then setup craft to download all the base dependencies (including gpgme) here: https://invent.kde.org/sysadmin/ci-images/-/blob/master/windows-msvc2019-qt515/Dockerfile?ref_type=heads#L12

And the same with the Qt6.6 image: https://invent.kde.org/sysadmin/ci-images/-/blob/master/windows-msvc2022-qt66/Dockerfile?ref_type=heads

You are right. Forget what I wrote. I had forgotten that the Windows CI images use Craft to install the non-KDE dependencies.