Tony, Jenkins should pick up things generated by the maven assembly plugin. Having said that, could you not use the build-helper-maven plugins attach-artifact goal to attach the zip file to your Maven project:
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html After that Maven and Jenkins would do what comes naturally. -Jim -----Original Message----- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of abargnesi Sent: Wednesday, March 28, 2012 12:47 PM To: Jenkins Users Subject: Using relative paths when deploying ZIP artifact using Jenkins Artifactory Plugin Hello, I have a ZIP file generated by a maven assembly that I want to install into an artifactory instance. This ZIP file is not an artifact of the maven build so it is not picked up by the Maven3 artifactory deployment. I instead enabled Generic-Artifactory Integration and mapped that zip file to a path on artifactory. The problem is it always appends the relative path of the ZIP file to the deployment path on artifactory. My goal is to deploy into a standard maven layout GROUP_ID/ARTIFACT_ID/VERSION. Is this possible from the jenkins artifactory plugin? Thanks! Tony Bargnesi
