|
||||||||
|
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 just had an issue that let me discover this one which is for now considered as a normal behavior (https://github.com/jenkinsci/maven-plugin/blob/master/src/main/java/hudson/maven/RedeployPublisher.java#L203)
Not totally wrong as I wrote a part of this code and that's right that the upload is done from master (that's why it requires to archive artifacts to move back artifacts from the agent to master) and thus on master the workspace can be missing thus using always the shared $HOME/.m2/repository is a solution.
The problem is that it may create conflict between jobs trying to upload at the same time (that's why the ability to use a repository local to each workspace was added).
I don't have a real solution.
Enforcing to create a local workspace on master for the job could be a solution with less conflicts but it may always happen (if another build is starting on master for the same job).
Using a temp directory will enforce maven to download the earth each time ....
Perhaps the best solution nowadays could be to use the deployAtEnd option of the recent version of the maven-deploy-plugin : https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd