Details
-
Type:
Improvement
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: svn-tag-plugin
-
Labels:None
-
Environment:Jenkins 1.4.50
Environment Injector Plugin 1.30
SVN Tagging 1.16
Promoted builds plugin 2.4
-
Similar Issues:
Description
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'
Attachments
Activity
Is there anything we could do to bump up the priority of this ticket or help in any way? 
k2nakamura, do you have an expected ETA for it?
Gabriele Giuseppini
added a comment - Is there anything we could do to bump up the priority of this ticket or help in any way? k2nakamura, do you have an expected ETA for it? It also does not support approval parameters passed into the build for a promotion build.
For now, I'm going to have to just write a script to do an svn tag.
Steven Lee
added a comment - It also does not support approval parameters passed into the build for a promotion build.
For now, I'm going to have to just write a script to do an svn tag. Renjith, assigning to you as it appears you are now the official owner. What are your thoughts on this bug?
Gabriele Giuseppini
added a comment - Renjith, assigning to you as it appears you are now the official owner. What are your thoughts on this bug?
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.