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
Provide an option to the conan_build_info --v2 publish subcommand to be able to specify an artifactory project with a dedicated buildinfo repository where the buildinfo should be stored.
Thanks a lot for the suggestion. I have been briefly checking the Artifactory API docs and looks like it would be possible as the API supports setting the project. Right now we are focusing in Conan 2.0 and also the build_info is going to change for 2.0, so I'm marking this for the 2.0 milestone as a feature to have into account for 2.0 implementation of the build_info.
Provide an option to the conan_build_info --v2 publish subcommand to be able to specify an artifactory project with a dedicated buildinfo repository where the buildinfo should be stored.
Currently one can only perform this with the jfrog CLI build upload command (see https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-BuildUpload) but this requires an additional tool in the CI pipeline (including setup and authentication) though the principal functionality is already contained in the conan_build_info tool (see also czoido/conan-build-info-example#1).
The text was updated successfully, but these errors were encountered: