-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local settings.xml not picked up by Jenkins agent #63
Comments
The issue is related to the If you only want to run the build independently of the user, you can use the follow as agent:
A few notes:
|
@gonzalesraul That works! Thank you for the help. |
Is there any other workaround for it? Of course I want a new clean Maven container for each job run. And there must be a way to inject a custom settings.xml if container is not run as root. In Jenkins, if the container is forced to run as root via
subsequent runs will fail as Jenkins is unable to delete generated directories. Seems to be a long-time issue with this image, see: #14, #16, #18, |
@steinsag yes, there is a few but I would suggest these below:
|
I think this is an issue with jenkins, and somewhat fixed based on #16 (comment)
|
@carlossg the issue resides on Jenkins for sure. I think the root cause to getting these behaviors, resides on Your mention to jenkinsci/docker-workflow-plugin#63 only resolves the It still might not be on the maven container scope, but still a valid issue when used with |
I'm using this image to build on jenkins:
The
${HOME}/.m2/settings.xml
is there but is not getting picked up.Using
help:effective-settings
, I get this:I have also tried adding the
settings.xml
to/usr/share/maven/ref
but get the same settings:Is there a way to force the maven image to use
${HOME}/.m2/settings.xml
?The text was updated successfully, but these errors were encountered: