|
||||||||||||
|
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.
example project attached tc-jenkins.zip
when parent pom is in remote repo jenkins fails.
the project:
two modules referencing a parent deployed in artifactory. a root pom as reactor.
jenkins 1.598
simple maven job.
local maven 3.2.5 home, but same happens with auto install.
checks out ./project
maven build step: clean install
settings.xml containing artifactory mirror in jenkins home .m2/settings.xml
parent deployed to artifactory
when run on master:
Parsing POMs
FATAL: null
java.lang.StackOverflowError
at java.lang.reflect.InvocationTargetException.<init>(InvocationTargetException.java:72)
build the jenkins workspace manually with mvn clean install succeeds and downloads the parent from artifactory.
now the jenkins job works because the parent is in the local repo.
remove the settings.xml from jenkins home .m2/settings.xml , jenkins job fails with same exception although the parent is still in the local repo.
supplly Maven settings.xml and Global settings.xml configured with artifactory mirror, by config file plugin. jenkins job succeeds again.
delete the parent from the local repo. jenkins job fails again.
if I add on this 'Resolve artifacts from Artifactory' the jenkins job is stuck.
same thing when configuring jenkins to Use private Maven repository
downgrade to 1.597 all is working again