Problem with different values for checkoutVariantId on Windows

[sbixl]

Hi,

i currently facing a problem that packages built on a Jenkins-Agent (Windows Server 2022) have a different checkoutVariantId than those building on a Windows 11 System.

For example this recipe is affected by this. If I uncomment the checkoutScript, the buildVariantId as well as the packageVariantId are identical between the Windows 10 and Windows 11 system.

I would like to narrow down the error, but I can't really get any further.
How exactly is the checkoutVariantId calculated and may it possible that there are a (breaking) dependency between Windows 10 and 11? Is it possible to activate an extended debug output?

PS:

• I use two Jenkins-Agents which are configured using Ansible so both are therefore identical. The Windows 11 system (updated previously from Windows 10 to Windows 11) is my Notebook.
• Symlinks are enabled (Building all packages on the Jenkins Agents works perfect)

bob: 1.0.0
python: 3.13.3

[jkloetzke]

IIRC there should be nothing that is platform dependent with respect to the Variant-Id. Issues like symlinks are only affecting the Build-Id.

But I see your recipe includes a patch. The content of this patch will affect the checkout variant id! Now, there are a number of options in git that affect the handling of line endings on Windows. There is a chance that these settings differ between the systems and that the same patch has a different checksum between them.

In basement, the line endings are set explicitly by the repository via gitattributes to prevent such possible problems. Even if it is another problem, I would recommend doing this.

[sbixl]

That was exactly the problem. Many thanks for the quick reply.