[JIRA] [plugin] (JENKINS-24738) Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable

[tanya....@gmail.com (JIRA)]

Tanya Fernandez created JENKINS-24738 Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable Issue Type: Bug Assignee: Deluan Quintão Attachments: RTC buildtoolkit issue.png Components: plugin, rtc, teamconcert, toolenv Created: 17/Sep/14 5:52 AM Description: Checkout from RTC doesnt happen if the Build ToolKit to be used is specified in the form of an environment variable. This is so that the Build ToolKit on slave machine is used. configurations on Jenkins: System configuration:RTC build toolkit installation path provided as the environment variable Job configuration: Override global RTC repository connection option selected for RTC scm. Overriding the toolkit path in slave configuration using environment variables just lead to Jenkins searching for the toolkit in directory where the slave is located(in Screenshot) The variations in the way the path was provided: $RTC_BUILD_HOME , %RTC_BUILD_HOME% The way around this was to hard code path to toolkit in job configuration in which case the slave machine's toolkit was could is not the one being used. Environment: Jenkins Version: 1.571 installed plugins: Team Concert Plugin(1.1.8) , Tool Environment Plugin (1.1) OS:Windows 7 Project: Jenkins Labels: plugin slave toolEnvironment RTC rtcBuildToolKit Priority: Major Reporter: Tanya Fernandez

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.