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.
Merge branch 'master' into doCheckRemote-masterEnvVars
Make sure SVN_* variables are set even when SVN location involves recursive variable substitution.
[FIXED JENKINS-16533] Respect external revision
add test for JENKINS-16533
document testPollingRespectExternalsWithRevision()
Merge pull request #51 from yoichi/master

[FIXED JENKINS-16533] Respect external revision
[maven-release-plugin] prepare release subversion-1.51
[maven-release-plugin] prepare for next development iteration
Merge pull request #38 from jglick/doCheckRemote-masterEnvVars

Expand environment variables in repository URL.
fixed sample repository url in help texts
upgrade trilead lib