Check CONFIGURE permission on the actual job, not Jenkins overall.
Typo.
Expand environment variables in repository URL in job confguration during validation check, affecting also entering of credentials.
This should allow you to use the same $JENKINS_HOME contents while switching the physical location of your Subversion server using a startup environment.
(Has no effect when "Validate repository URLs up to the first variable name" is checked.)
$SVN_REVISION also needs to take into account possibly substituted server location.
checkRevisionPropertiesSupported also needs to subst env vars.
Different overload now being called.
Fail with useful error message instead of NPE, if subversion is not
installed
ignore
rolling forward after botched release
rolling forward after botched release
[maven-release-plugin] prepare release subversion-1.48
[maven-release-plugin] prepare for next development iteration
Merge branch 'master' into doCheckRemote-masterEnvVars
French translations - Fix encoding
Add French translations
English translation - Fix quotes
Merge pull request #41 from damienfinck/master

Add and edit French/English translation
- Update maven-scm-api to fix problem with localized git output while releasing
- surefire and hpi-plugin updates
[FIXED JENKINS-14551] added files merged from a branch results in those files having doubled content
Grr, even maven-scm-api 1.8.1 doesn't fix the problem with localized git output.
Rolling forward after botched release