After some tests, I found the problem (but not the solution...) : The subversion plugin try to find configured property by it's name into Job properties, as seen in the config.xml into <properties>. It's why the release plugin "Override build parameters" works with subversion plugin. The release plugin register "release" defined properties into an <buildWrapper> (in config.xml) and that's seen by the Job class as an Action (containing properties). So, if looking at "properties" of a given Job you can't seen Release properties. Anyway, where is the bug ? Does Release plugin need to store it's properties differently ? Does jenkins Job class need to be improved ? Does subversion plugin ? Hope my investigations help ! |