|
||||||||
|
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.

+1 I just ran into this situation as well. If other have a better work around I would be interested. Currently I think the only solution that works for us is to configure the settings.xml file for each slave which cause more maintenance overhead and loses the value provided by Jenkins performing the Maven Artifact Deployment.