[
https://issues.jenkins-ci.org/browse/JENKINS-9743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158794#comment-158794
]
stigkj commented on JENKINS-9743:
---------------------------------
This is fixed in [GitHub
commit|https://github.com/jenkinsci/promoted-builds-plugin/commit/9b79be8796fe054ed02fa1d3ca01f57542e5fa83]
> SVN_REVISION environment variable not available to promote build shell command
> ------------------------------------------------------------------------------
>
> Key: JENKINS-9743
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9743
> Project: Jenkins
> Issue Type: Bug
> Components: promoted-builds
> Environment: Centos, Java 6, Jenkins 1.410
> Reporter: Robert Elliot
>
> When adding a shell action to a promotion process on a job that is using
> subversion source control the SVN_REVISION environment variable is not
> provided. The BUILD_NUMBER environment variable is there and correct, so we
> can work around it as so:
> {noformat}export SVN_REVISION=`wget -qO-
> http://<host>/job/spike-application/${BUILD_NUMBER}/api/xml?tree=changeSet[revisions[revision]]
> | grep -o "[0-9]\+"`
> echo PROMOTED ${SVN_REVISION} from unstable to stable{noformat}
> However, that's obviously horrible and given the BUILD_NUMBER is available it
> should be possible to retrieve the SVN_REVISION without an HTTP request.
--
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
