It is a MavenBuilld, not a FreestyleBuild, that's why I am rather confused.
The MavenBuild correctly BUIILDSin fact, but is unable to publish to the
repository ("unauthorized"), which is a proof that the "personal"
settings.xml provided by the config plugin is NOT considered by that job
option (at least).
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, ka...@quipsy.de 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
