You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
Notice the mismatch between CPT user in configuration and the actual user of the package.
+--------------------+-----------------------------------------------------------------+
| Configuration | value |
|--------------------+-----------------------------------------------------------------|
| name | my-recipe |
| version | 0.0.0 |
| user | my_login_user |
| channel | stable |
| build_modes | |
| require_overrides | |
| profile_name | C:\Windows\TEMP\tmprm11l096conan_package_tools_profiles\profile |
| profile_build_name | |
+--------------------+-----------------------------------------------------------------+
Exporting package recipe
my-recipe/0.0.0@my_package_user/stable exports_sources: Copied 1 file: .gitignore
my-recipe/0.0.0@my_package_user/stable: A new conanfile.py version was exported
my-recipe/0.0.0@my_package_user/stable: Folder: K:\.c.p\2099_\.conan\data\my-recipe\0.0.0\my_package_user\stable\export
my-recipe/0.0.0@my_package_user/stable: Using the exported files summary hash as the recipe revision: f92738ed1a316ed685e7135a7dd73a2f
my-recipe/0.0.0@my_package_user/stable: Exported revision: f92738ed1a316ed685e7135a7dd73a2f
The text was updated successfully, but these errors were encountered:
NokiDev
changed the title
No upload when CONAN_LOGIN_USERNAME, CONAN_USERNAME and Conanfile.user are defined and different
No upload when CONAN_LOGIN_USERNAME, CONAN_USERNAME or Conanfile.user are defined and different
Sep 15, 2022
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.
The text was updated successfully, but these errors were encountered: