CPT uses CONAN_LOGIN_USERNAME as conan user, rather than defined variable CONAN_USERNAME or Conanfile.user
I believe this leads to a reference mismatch, making the upload of artifacts not executed (the process stops after running test_package, without a log). See runner.py#171.
I'm not sure why the user used by cpt is not the one defined either with CONAN_USERNAME or Conanfile.user, but it happened when upgrading conan from 1.45 to 1.52.0. So it might be a conan API thing.
The workaround, we use for now is to define directly the user in ConanMultiPackager(user=my_package_user)
Description of Problem
CPT uses
CONAN_LOGIN_USERNAME
as conan user, rather than defined variableCONAN_USERNAME
orConanfile.user
I believe this leads to a reference mismatch, making the upload of artifacts not executed (the process stops after running test_package, without a log). See runner.py#171.I'm not sure why the user used by cpt is not the one defined either with CONAN_USERNAME or Conanfile.user, but it happened when upgrading conan from 1.45 to 1.52.0. So it might be a conan API thing.
The workaround, we use for now is to define directly the user in
ConanMultiPackager(user=my_package_user)
Environment Details
Steps to reproduce (Include if Applicable)
The following recipe :
The following build.py :
Setting the following in environment :
Running
python ./build.py
Build logs (Include if Available)
Notice the mismatch between CPT user in configuration and the actual user of the package.