Quantcast
Jenkins › Jenkins issues

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

classic Classic list List threaded Threaded
♦
♦
 14 messages Options
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Gregory Boissinot
Components: artifactdeployer
Created: 25/Sep/12 6:29 AM
Description:

Commit 51d5220f6c19c4e7d5c35a07b62219472b2a7870 changed the RedeployPublisher such that the global Maven settings are no longer checked as fallback, if no per user configuration is found. The Build Slave is running as a service and thus as no user. Hence, the RedeployPublisher requires the configuration to be in C:\.m2\. As a result I have to copy the settings.xml to this location, and maintain both identical files in order to have it available for the service as well as when I log in to the machine manually.
Environment: Build Master on Ubuntu, Build Slave on Windows XP as a service
Project: Jenkins
Priority: Major Major
Reporter: Sven Amann
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
Change By: Sven Amann (25/Sep/12 6:45 AM)
Component/s: maven2
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
sbrinkmeyer commented on Bug JENKINS-15292

i too now have this issue with RedeployPublisher
channel stopped
Archiving artifacts
Maven RedeployPublisher use rhel.61.x32.1 maven settings from : /home/cmadmin/.m2/settings.xml
ERROR: Publisher hudson.maven.RedeployPublisher aborted due to exception
hudson.util.IOException2: Failed to copy /home/cmadmin/.m2/settings.xml to /usr/local/jenkins-secure/tmp/jenkins314223192807287748temp-settings.xml

jenkins version 1.483
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Same problem here after having upgraded from v1.479 to v1.483:

...
[WARNINGS] Parsing warnings in console log with parser Java Compiler (javac)
Maven RedeployPublisher use  maven settings from : /pathto/tomcat/.m2/settings.xml
ERROR: Publisher hudson.maven.RedeployPublisher aborted due to exception
hudson.util.IOException2: Failed to copy /pathto/tomcat/.m2/settings.xml to /pathto/tomcat/temp/jenkins6746977447219049704temp-settings.xml
	at hudson.FilePath.copyTo(FilePath.java:1650)
	at hudson.maven.RedeployPublisher.createEmbedder(RedeployPublisher.java:287)
	at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:153)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
	at hudson.model.Run.execute(Run.java:1527)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Caused by: java.io.FileNotFoundException: /pathto/tomcat/.m2/settings.xml (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.<init>(FileInputStream.java:138)
	at hudson.FilePath$33.invoke(FilePath.java:1676)
	at hudson.FilePath$33.invoke(FilePath.java:1671)
	at hudson.FilePath.act(FilePath.java:852)
	at hudson.FilePath.act(FilePath.java:825)
	at hudson.FilePath.copyTo(FilePath.java:1671)
	at hudson.FilePath.copyTo(FilePath.java:1645)
	... 11 more
Email was triggered for: Failure
...
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Ive got exactly the same issue (1.483), the only way around it is to add a pre-build step and execute a script to copy the global settings.xml to the local .m2/settings.xml......
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Gregory Boissinot (07/Oct/12 9:25 AM)
Component/s: artifactdeployer
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
sbrinkmeyer commented on Bug JENKINS-15292

my scenario, the master is linux, and the slaves that are failing this are also linux.
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Jeff MAURY commented on Bug JENKINS-15292

I have also the same problem on my single master Jenkins machine where I don't have a $HOME/.m2/settings.xml because I'm using Maven settings files managed by Jenkins (config-file-provider plugin)
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
olamy commented on Bug JENKINS-15292

IMHO https://github.com/jenkinsci/jenkins/commit/51d5220f6c19c4e7d5c35a07b62219472b2a7870 must be reverted.
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
sbrinkmeyer commented on Bug JENKINS-15292

so it looks like this is a partial good fix that misses use case. instead of rolling it back, can this be fixed instead? ...
don't get me wrong, i'd really like this fixed ASAP also
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Sven Amann commented on Bug JENKINS-15292

From the respective changeset I take that maven default settings are considered automatically if MVN_HOME is set, right?
The error occurs in case the user-wise maven config doesn't exist, because the code tries to copy the file anyways what results in FNF. Therefore, if the code doesn't need to fall back to the maven default config, because that happens automatically, you should just avoid the copy in case the target file is missing? I'm not sure about how the config files behave though...
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: Nicolas De Loof
Path:
maven-plugin/src/main/java/hudson/maven/RedeployPublisher.java
http://jenkins-ci.org/commit/jenkins/6eba5a87bc82bcc4895486e3905b10cd0956b142
Log:
[FIXED JENKINS-15292] Revert "setting maven home is enough for global settings to be m.getHome()/conf/settings.xml"

This reverts commit 51d5220f6c19c4e7d5c35a07b62219472b2a7870.

hudson.maven.MavenUtil#createEmbedder set GlobalSettingsFile to MavenHome/conf/settings.xml by default so I can't explain this regression
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: SCM/JIRA link daemon (15/Oct/12 9:47 AM)
Status: Open Resolved
Resolution: Fixed
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
JIRA noreply@jenkins-ci.org
Reply | Threaded
Open this post in threaded view
♦
♦
|  
Report Content as Inappropriate
♦
♦
star
♦
♦

[JIRA] (JENKINS-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
dogfood commented on Bug JENKINS-15292

Integrated in jenkins_main_trunk #2003
[FIXED JENKINS-15292] Revert "setting maven home is enough for global settings to be m.getHome()/conf/settings.xml" (Revision 6eba5a87bc82bcc4895486e3905b10cd0956b142)

Result = UNSTABLE
Nicolas De Loof : 6eba5a87bc82bcc4895486e3905b10cd0956b142
Files :

  • maven-plugin/src/main/java/hudson/maven/RedeployPublisher.java
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
Loading...
Powered by Nabble Edit this page