-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins: 2.30
Artifactory plugin: 2.8.1
I started with the sample multi-project gradle build provided here:
https://github.com/JFrogDev/project-examples/tree/master/gradle-examples/4/gradle-example-ci-server
The publish to Artifactory via the Jenkins plugin worked just fine. I then started stripping out the multiple modules and brought it down to just one module (the 'shared') module and then moved the source of the shared module to the top level, effectively making it a simple gradle project.
The Jenkins Artifactory plugin no now longer publishes the artifact to Artifactory. I dug into the temporary file that is generated by this plugin and found the below:
// Set the "archives" configuration to all Artifactory tasks.
for (Project p : root.getAllprojects()) {
Task t = p.getTasks().findByName(ArtifactoryTask.BUILD_INFO_TASK_NAME)
if (t != null)
}
Does this mean that the root project can not be published to artifactory via this mechanism and that all gradle projects have to have a sub-project that produces the artifact in order for this plugin to publish it to Artifactory. That would seem like an unreasonable restriction and would like to confirm.
- is related to
-
JENKINS-39755 Gradle project does not deploy
-
- Open
-
I found JENKINS-39755 and as per that issue, when I downgraded to 2.7.2 the publish from the root project worked. The generated gradle artifactory plugin file does look the same though. So I don't think my original analysis of this issue is valid.