Hi everyone. I need this bug/feature so much that I'm willing to pay 40.00 bucks for it.
This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/39/svn-tag-plugin-does-not-support-environment-variables-from-promoted-build).
Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too)
I'll then check it out and will gladly pay up!

If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors!

The problem is that the svn-tag plugin takes the environment variables from the ancestor build and not the actual build that was triggered.

The issue can be solved if the environment variables from the actual build are put in the var map and then the ancestor build adds/overrides its environment variables to the map. That would not change the original behaviour of the svn-tag plugin but add the wanted functionality for it to work well together with the promoted build plugin.

The bugfix would be in the SvnTagPlugin.java in line 100.

<replace>
EnvVars envVars = rootBuild.getEnvironment(buildListener);

<with>
EnvVars envVars = abstractBuild.getEnvironment(buildListener);
EnvVars rootVars = rootBuild.getEnvironment(buildListener);
envVars.putAll(rootVars);

This issue still exists with the following versions:

• Jenkins 1.609.1
• Jenkins Subversion Tagging Plugin 1.18
• Jenkins Subversion Plugin 2.5.1
• Jenkins promoted builds plugin 2.21

I no longer support this plugin. Please find someone who can add the feature.