Issue Type: Bug Bug
Assignee: Gregory Boissinot
Attachments: config.png, console_output.png
Components: envinject-plugin
Created: 02/Dec/14 1:08 PM
Description:

Team Concert plugin automatically creates several environment variables during the SCM checkout. Jenkins is able to resolve them properly, but EnvInject isn't.

In order to reproduce the bug, configure the Team Concert plugin as specified here: https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin

Then simply add and EnvInject build step with the following Properties Content:
TESTE=${RTCBuildResultUUID}

where RTCBuildResultUUID is a known variable at this point. It can be proved with a Windows Batch build step "echo %RTCBuildResultUUID%".

The Console Output will print
[EnvInject] - Injecting as environment variables the properties content
TESTE=${RTCBuildResultUUID}

Here, RTCBuildResultUUID is not replaced by its actual content.

The attached images show the configuration and the console output. Two variable copies are created (SuccessfulVar and FailedVar), the first is persisted even when the original variable changed its value. The latter one isn't persisted.

Environment: Jenkins 1.556, Team Concert Plugin 1.1.9, Environment Injector Plugin 1.90.
OS: Windows 7.
Project: Jenkins
Labels: envinject envinronment-variables team-concert
Priority: Major Major
Reporter: Rafael Rezende
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to