Skip to content

respect args passed through cli conan cmds#3378

Open
reshmifrog wants to merge 3 commits intojfrog:masterfrom
reshmifrog:fix/conan-recipe-not-in-root-dir
Open

respect args passed through cli conan cmds#3378
reshmifrog wants to merge 3 commits intojfrog:masterfrom
reshmifrog:fix/conan-recipe-not-in-root-dir

Conversation

@reshmifrog
Copy link
Contributor

  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • The pull request is targeting the master branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....

Problem:
When running conan install --requires zlib/1.2.11 (without a conanfile.py or conanfile.txt), the JFrog CLI fails with the error "no conanfile.py or conanfile.txt found" because the build-info collection logic always expects a recipe file to exist, even though Conan 2.x officially supports installing dependencies directly via --requires and --tool-requires without any conanfile.
Solution:
Modified loadConanfile() in build-info-go to gracefully set default project metadata (name from directory, empty version, default user/channel) instead of failing when no conanfile is found. Updated buildGraphInfoArgs() to pass --requires and --tool-requires flags directly to conan graph info when no conanfile exists, and wired CLI overrides (--name, --version, --user, --channel) through jfrog-cli-artifactory so the build-info module ID can still be customized.

@reshmifrog reshmifrog added improvement Automatically generated release notes safe to test Approve running integration tests on a pull request labels Mar 3, 2026
@reshmifrog reshmifrog added safe to test Approve running integration tests on a pull request and removed safe to test Approve running integration tests on a pull request labels Mar 3, 2026
@reshmifrog reshmifrog added safe to test Approve running integration tests on a pull request and removed safe to test Approve running integration tests on a pull request labels Mar 3, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 3, 2026

👍 Frogbot scanned this pull request and did not find any new security issues.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Automatically generated release notes safe to test Approve running integration tests on a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant