[
https://issues.jenkins-ci.org/browse/JENKINS-10484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163466#comment-163466
]
Benjamin Hahne edited comment on JENKINS-10484 at 6/4/12 7:54 AM:
------------------------------------------------------------------
Please note that, when SVN_REVISION was not set in the previous, Jenkins cannot
tell that it's on the same revision and ALWAYS does a build, making this
function unusable with parameters.
was (Author: bjhahne):
Please note that, when SVN_REVISION was not set in the previous, Jenkins
cannot tell that it's on the same revision and ALWAYS does a build, making this
function unusuable with parameters.
> SVN_REVISION environment variable is not set when using parameterized
> Repository URL
> ------------------------------------------------------------------------------------
>
> Key: JENKINS-10484
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10484
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Environment: windows 2003 server, Jenkins 1.421, Subversion Plugin
> 1.2.8
> RedHat 6.0, Jenkins 1.447.1 LTS, Subversion Plugin 1.40
> Reporter: Erez Harari
> Priority: Critical
>
> I'm using a single Repository URL with parameterized value:
> ${SVN_URL}/application, where SVN_URL is defined as a node level parameter.
> in that case SVN_REVISION environment variable is not set.
> When using a clear text Repository URL all works fine.
--
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
