|
||||||||
|
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.
No, The access to artifactory is via a global settings.xml file that all users on the same jenkins server all use via the defaults set for maven jobs. I did configure the Invoke top-level Maven targets -> Advanced -> Settings file -> Settings file in filesystem to point to the file that is used by default in Maven 2/3 jobs: /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml and I am seeing it echoed in my console output debug logs so it is using the correct file to get artifactory repo credentials.
Also I have a freestyle job which uses the same Invoke top-level maven targets and the same configuration but runs the build only once, and it passes every time, only the multi-configuration job gets this error on 1 of it's two configurations.
[DEBUG] Reading global settings from /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml
[DEBUG] Reading user settings from /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml