|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've looked into this a few months ago, and this is what I found:
The problem is that AbstractBuild queries (in that order) EnvironmentContributors, SCM, BuildWrapper.Environments and EnvironmentContributingActions to incrementally build the set of environment variables while a build is started.
SubversionSCM (an SCM) looks for matching entries in the URL -> Revision map during this variable resolution. If so, they are added as SVN_URL_x and SVN_REVISION_x. Why not just add everything? My guess is externals (while listed for a build, only explicitly defined locations have corresponding variables).
Due to the order of resolution, Env-Injected variables are not yet defined. This leads to a warning in the log of the form:
WARNING hudson.scm.SubversionSCM buildEnvVars no revision found corresponding to ${SVNURL}; known: [https://svn/repo/...]