Include dependency metadata in build-info for Android#828
Merged
nitinp19 merged 3 commits intojfrog:masterfrom Sep 16, 2025
Merged
Include dependency metadata in build-info for Android#828nitinp19 merged 3 commits intojfrog:masterfrom
nitinp19 merged 3 commits intojfrog:masterfrom
Conversation
fluxxBot
requested changes
Sep 3, 2025
| void apply(Project project) { | ||
| if ("buildSrc".equals(project.name)) { | ||
| log.debug("Artifactory Plugin disabled for ${project.path}") | ||
| log.info("Artifactory Plugin disabled for ${project.path}") |
Contributor
There was a problem hiding this comment.
why did we changed log level here?
Contributor
Author
There was a problem hiding this comment.
When we are enabling the debug log level. It becomes too hard to filter the actual log from the gradle task logs.
...ctor-gradle/src/main/groovy/org/jfrog/gradle/plugin/artifactory/ArtifactoryPluginBase.groovy
Outdated
Show resolved
Hide resolved
...ctor-gradle/src/main/groovy/org/jfrog/gradle/plugin/artifactory/ArtifactoryPluginBase.groovy
Outdated
Show resolved
Hide resolved
...org/jfrog/gradle/plugin/artifactory/extractor/listener/ProjectsEvaluatedBuildListener.groovy
Show resolved
Hide resolved
agrasth
approved these changes
Sep 3, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem-
A user is experiencing an issue where the dependencies of their Android project are not being captured in the build-info.json file when using the JFrog CLI following command.
1- jf gradle "assembleDebug" --build-name=android-gradle --build-number=1
2- jf rt u "app/build/outputs/apk/debug/app-debug.apk" "demo-gradle-dev/android-sample-app/app-debug.apk" --build-name=android-gradle --build-number=1
3- Jf rt bp android-gradle 1
While this isn't preventing the build from completing, it creates a feeling that the project isn't being built properly.
"assembleDebug" is a gradle build task which lets you build the apk for the staging environment. This task does not enable the module-extractor task which helps to collect the dependencies.
Solution-
by adding artifactoryPublish in the command with assembleDebug. this will register the artifactoryTask in the gradle project which internally register the extract-module task for the project that collects the dependencies for the modules.
jf gradle "assembleDebug" atrifactoryPublish --build-name=android-gradle --build-number=1
Also, I have changed the hasModules() this function just not only check for the publication but also do check for the
modules present or not for the module now. It helps us to collect the dependencies for the modules that do no have any publication configured just like the android project.