[
https://issues.jenkins-ci.org/browse/JENKINS-12933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160539#comment-160539
]
Gabriele Giuseppini commented on JENKINS-12933:
-----------------------------------------------
We are also hitting this one. Our tag names need to contain some extra
information that is injected by the EnvInject plugin in an earlier step of a
promotion process, but the SvnTag plugin does not see these environment
variables.
> svn-tag plugin does not support environment variables injected by EnvInject
> Plugin in promoted build
> ----------------------------------------------------------------------------------------------------
>
> Key: JENKINS-12933
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12933
> Project: Jenkins
> Issue Type: Improvement
> Components: svn-tag
> Affects Versions: current
> Environment: Jenkins 1.4.50
> Environment Injector Plugin 1.30
> SVN Tagging 1.16
> Promoted builds plugin 2.4
> Reporter: A Geller
> Assignee: k2nakamura
> Attachments: 2012-02-29 17h03_45.png
>
>
> During 'build promotion' I would like to tag the project sources. The tag
> name should be given automatically by an environment variable. This variable
> is not included in the Jenkins default environment but given by the
> EnvInjection plugin.
> The scenario is given in the attachment.
> Expected behaviour:
> The variable 'release.number' set by the EnvInject plugin should be available
> to the svn-tag plugin.
> Present behaviour:
> ${env['release.number']} is expanded to 'null'
--
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
