Well, the name is one thing, but the artifacts themselves differ (I create two ZIP files, but only one (and which one?) ends up as Jenkins artifact.
I would expect that the Maven job type asks Maven about the job artifacts - but then I'm probably wrong ;-) For the moment I can live with the fact that I have to get artifacts from the workspace instead of Jenkins (even though I'll miss the nice permalinks). But should I write an issue in the Jenkins JIRA? Best regards, Eric Von: [email protected] [mailto:[email protected]] Im Auftrag von Stephen Connolly Gesendet: Donnerstag, 7. Juni 2012 10:54 An: [email protected] Betreff: Re: Maven build results don't match Jenkins Build Artifacts Those are what maven considers the artifacts, ie those are the names that will end up in the maven repository. You can manually archive the files if the name is that important to you. Of course I never use the maven job type as it does things (which make the users life initially easier) that are not the maven way. My preference is a maven build step in a freestyle project... But what would I know! One of these days sacha will ok me writing a correct maven job type (something which I know how it should be done, but haven't had the time to do yet. Btw that fork of jenkins has not done it right either ;-) ) On Thursday, 7 June 2012, Lewis, Eric wrote: Hi Since changing from an old Hudson to Jenkins 1.460 I noticed that Maven's build results differ from what Jenkins considers Build Artifacts. Specifically it has to do with renaming and using other results of the Maven assembly plugin. For instance, I have a build which repackages some XML schemas in various forms. Here's what it looks like in the workspace: target/ |-- schemas.war |-- xml-schemas-1.6.0-sources.jar |-- xml-schemas-1.6.0.jar |-- xml-schemas-application-server-1.6.0.zip `-- xml-schemas-public-schema-server-1.6.0.zip Here's what Jenkins considers build artifacts: Build Artifacts xml-schemas-1.6.0-sources.jar xml-schemas-1.6.0.jar xml-schemas-1.6.0.pom xml-schemas-1.6.0.war xml-schemas-1.6.0.zip Is this a known bug? Best regards, Eric
