|
||||||||
|
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 |
||||||||
|
||||||||
|
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 |
||||||||
We see similar behavior. To add to what Justin sees above, if we don't check "Disable automatic artifact archiving" under the Maven Build step, and let Jenkins grab the artifacts per module, what gets saved after running the release plugin is the initial SNAPSHOT artifact of the project (from release:prepare, I believe).
If we check "Disable automatic artifact archiving" and add a post-build step to archive the artifacts we want, it saves the correct 'release' (non-SNAPSHOT) artifacts, but the Jenkins fingerprints for the artifacts are invalid: "The fingerprint xxxxxxx did not match any of the recorded data."