[
https://issues.jenkins-ci.org/browse/JENKINS-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163663#comment-163663
]
jonathan_w_brown commented on JENKINS-12042:
--------------------------------------------
Output excerpt taken from a build shell script step for a non-decorated svn url:
U .
At revision 72666
[workspace] $ /bin/sh -xe /tmp/hudson1315590806389520477.sh
+ env
+ grep SVN
SVN_URL=http://urlpath
SVN_REVISION=72603
Then I add a string build parameter [REVISION] and modify the svn url to be in
the form http://urlpath/@${REVISION}. For this test I set the value of my
REVISION parameter to '71640'.
U .
At revision 71640
no revision recorded for http://urlpath/ in the previous build
[workspace] $ /bin/sh -xe /tmp/hudson6960655887912316261.sh
+ env
+ grep SVN
The result is the same if I hardcode the revision number as part of the url
rather than parameterize it.
Environment: Jenkins 1.466, svn plugin 1.40.
Let me know if there is any additional information I can provide.
> SVN_REVISION varable is empty if URL contains "@Revision"
> ---------------------------------------------------------
>
> Key: JENKINS-12042
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12042
> Project: Jenkins
> Issue Type: Bug
> Components: core, subversion
> Environment: Jenkins 1.442
> Subversion plugin 1.37
> Reporter: Oleksandr Popov
> Priority: Blocker
>
> SVN_REVISION variable is not set if I specify revision (or keyword like HEAD)
> in URL (like @123).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
