Dominique Arnou added a comment - 2013-01-18 14:06 Without my global settings file provided as input, the release plugin seeking my own artifacts in the repository instead of mine

Dominik Bartholdi added a comment - 2013-03-11 06:35 - edited Since version 2.3 of the config-file-provider-plugin and jenkins 1.491, the settings.xml is handled correctly with the m2release plugin. but maybe you are talking about the other release plugin... I have never used it and I'm not sure what you mean by "are not available"? Each file provided by the config-file-provider can be used in every build (not only with maven) in different ways, e.g.: in the build environment as "Provide Configuration files" copy it to the workspace with a build step You can also give the copied script a final name and/or expose its name as a variable to reuse/reference it where ever you like.

Dominik Bartholdi added a comment - 2013-06-02 09:28 closing because of no feedback