Jenkins › Jenkins issues

[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build

Classic

List

Threaded

4 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build

Issue Type:	Bug
Assignee:	k2nakamura
Attachments:	config.xml
Components:	promoted-builds, svn-tag
Created:	27/Jul/12 9:04 AM
Description:	Parameter myversion2 (see attachment) is not useable in svn tag plugin. The tag gets names as null.
Environment:	Jenkins: 1.450 Jenkins promoted builds plugin: 2.6.1 Jenkins Subversion Plugin: 1.34 Jenkins Subversion Tagging Plugin: 1.16
Project:	Jenkins
Priority:	Major
Reporter:	Christian Gmeiner

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build

Change By:	k2nakamura (27/Jul/12 5:04 PM)
Assignee:	k2nakamura Renjith V

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build

In reply to this post by JIRA noreply@jenkins-ci.org

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!

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-14606) svn-tag plugin does not support environment variables from promoted build

In reply to this post by JIRA noreply@jenkins-ci.org

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);