Updates Jenkins to latest LTS release, and updated config file provider to 
latest. The problem is still there:
The RedeployPublisher tells me it is using this file:

Maven RedeployPublisher use remote XXX maven settings from : 
C:\.jenkins\tools\hudson.tasks.Maven_MavenInstallation\Maven_3.0.4/conf/settings.xml


Looking into that file I see that it is a default Maven Config, but NOT the 
global or jenkins-specific settings.xml! So I think there is a bug in the 
config provider -- it apparently does not tell the RedeployPublisher that 
it must use both provided files (the global one and the local one) on a 
remote slave!

Can somebody confirm this?

Regards
-Markus

Am Donnerstag, 6. März 2014 09:26:12 UTC+1 schrieb Christian Willman:
>
> Depends. Are you using a MavenBuild or a FreestyleBuild? The Config File 
> Provider plugin will hook into a MavenBuild, but for a FreestyleBuild 
> (using the "Invoke Maven Top-Level Targets" build step), you will need to 
> enable the "Provide configuration files" Build Environment task and then 
> modify the Maven command to include '-s ${SETTINGS_PATH}'.
>
> If you are using this as a mechanism to push out settings.xml changes then 
> it might be worthwhile to just provision out VMs using Puppet or Chef using 
> your desired Maven configuration.
>
> On Wednesday, March 5, 2014 10:21:18 AM UTC-5, [email protected] wrote:
>>
>> I have configured the Config File plugin to provide a custom settings.xml.
>> But it seems the Jenkins slave is not using it.
>> How to tell Jenkins that the Maven installation it automatically pushes 
>> on the slave shall use that custom settings.xml file?
>> I thought Config File plugin would automatically do that "under the hood" 
>> (as it knows it is a Maven config file) but in fact it seems it does not.
>> Any help appreciated! :-)
>> -Markus
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" 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/groups/opt_out.

Reply via email to