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.
Merge branch 'master' into doCheckRemote-masterEnvVars
Merge branch 'master' into doCheckRemote-masterEnvVars
Revised to only use masterEnvVars from getExpandedLocation(AbstractBuild).
A user reported that $SVN_REVISION_1 etc. were not getting set otherwise.
Merge branch 'master' into doCheckRemote-masterEnvVars
Make buildEnvVars take into account non-build variables when computing locations for SVN_* variables.
log external URL, not object ID (toString)
Added value 'unknown' for 'Repository depth option'
Added a test case for verifying that depth 'unknown' works
[JENKINS-17974] Changed 'undefined' to 'as-it-is' in web interface of subversion-plugin
[JENKINS-17974] Move 'as-it-is' option to the end.
[JENKINS-17974] Updated help page so it refers to 'as-it-is' instead uf 'unknown'
Merge pull request #46 from ezjenkins/master

[FIXED JENKINS-17974] new SVN plugin option to leave --depth parameters as they are
It's obvious that these are options, we don't need to say that
Merge branch 'master' into doCheckRemote-masterEnvVars
Make sure SVN_* variables are set even when SVN location involves recursive variable substitution.
Suppress warning for common and apparently harmless case.
> WARNING: no revision found corresponding to …; known: []