|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I have also encountered this problem, although I'm not sure it is an Artifactory plugin problem.
When Jenkins builds your Gradle project, it seems to checkout your code into a directory call 'workspace' rather than the name of your git repo.
Since Gradle uses the project directory as the default for the artifact name, your artifact gets built with the name 'workspace' which is wrong.
The workaround is to use the "Advanced Project Options" in Jenkins to make sure you project is built in an appropriately named directory.
The Artifactory plugin is unwittingly picking up the artifact as produced by Gradle.
It seems that this might be more of an issue of Gradle/Jenkins integration.