When settings CONAN_UPLOAD_DEPENDENCIES to "all", I expect that all dependencies of my conan package will be uploaded. In reality only the built packages are uploaded.
I was expecting this setting to be similar to conan's --build=missing or --build=all settings. In the case of conan, missing means that all missing packages are built and all will rebuild every package (even it is already exists).
I was assuming that CONAN_UPLOAD_DEPENDENCIES behaves the same way: all will upload all dependencies (those that were built and those that were not built). Instead, CONAN_UPLOAD_DEPENDENCIES behaves like conan's --build=missing option and will only upload dependencies that were built just now.
This is an issue for me in these cases:
header-only dependencies are never built and never uploaded to the remote specified in CONAN_UPLOAD: this is only necessary, if the header-only library is part of my public interface, otherwise header-only libraries are no runtime-dependencies of my package and can be handled as build-dependency
dependencies, which were already built during previous builds and thus already exist in my local conan cache, will not be built again during a release build (which has CONAN_UPLOAD and CONAN_UPLOAD_DEPENDENCIES set) and thus are not uploaded (could be workarounded by building the release with conan's --build=all settings)
If I am using an internal remote for resolving my dependencies during my own builds (remote A), which already contains binary builds for my dependencies. If I am uploading my dependencies to a different remote (remote B, specified in CONAN_UPLOAD), which does not contain my required dependencies yet, they will never be present in remote B, as they were never built during the cpt build.
I wonder if it possible to add another setting for CONAN_UPLOAD_DEPENDENCIES, which will upload ALL dependencies (not just dependencies, which were built during the conan install phase)
When settings CONAN_UPLOAD_DEPENDENCIES to "all", I expect that all dependencies of my conan package will be uploaded. In reality only the built packages are uploaded.
I was expecting this setting to be similar to conan's --build=missing or --build=all settings. In the case of conan, missing means that all missing packages are built and all will rebuild every package (even it is already exists). I was assuming that CONAN_UPLOAD_DEPENDENCIES behaves the same way: all will upload all dependencies (those that were built and those that were not built). Instead, CONAN_UPLOAD_DEPENDENCIES behaves like conan's --build=missing option and will only upload dependencies that were built just now.
This is an issue for me in these cases:
I wonder if it possible to add another setting for CONAN_UPLOAD_DEPENDENCIES, which will upload ALL dependencies (not just dependencies, which were built during the conan install phase)
Environment Details