[JIRA] (JENKINS-38357) Cannot use Jenkins Node properties as load directory for Team Concert plugin
Title: Message Title Rob Leach commented on JENKINS-38357 Re: Cannot use Jenkins Node properties as load directory for Team Concert plugin A free style job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38357) Cannot use Jenkins Node properties as load directory for Team Concert plugin
Title: Message Title Rob Leach commented on JENKINS-38357 Re: Cannot use Jenkins Node properties as load directory for Team Concert plugin Sorry, one other point to bring up I thought about last night. The example I provided is probably not the best example, but it underscores the point. This is not limited to just the location of the load source directory. It's applicable for any Node property environment variable that might be unique to a Node, and that needs to be consumed by a build job. Other examples could be the location of required build libraries (such as WebSphere or Java) which might be located in different directories on each node. A property file can help with this issue, but being able to manage that in the build job can be quicker, and not require the overhead of updating property files in source control etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-38357) Cannot use Jenkins Node properties as load directory for Team Concert plugin
Title: Message Title
Rob Leach created an issue
Jenkins / JENKINS-38357
Cannot use Jenkins Node properties as load directory for Team Concert plugin
Issue Type:
Improvement
Assignee:
Unassigned
Components:
teamconcert-plugin
Created:
2016/Sep/19 9:08 PM
Environment:
Jenkins 1.656 Team-concert 1.2.0.1
Labels:
plugin build
Priority:
Major
Reporter:
Rob Leach
There is no way to specify a predefined Node property environment variable as the Load directory for a build job using RTC source code management. So if you have multiple build nodes, you can't defined lets say: SRC_BASE uniquely for each node and then consume that Node property environment variable in a build job, so that the build job could execute on any node available. Some details; we have two linux hosts and two windows hosts setup as a build farm. These four hosts are configured as individual nodes in Jenkins. We want to configure our build jobs so they can run on any node. But there is no way to tell team concert to load to a location on the host that is platform independent. So if node1 was configured with a node property environment variable SRC_BASE=/opt/rtc/ssd and node2 was configured with a node property environment variable SRC_BASE=c:/common/rtc. Then I should be able to configure my build job to use the load directory $ {SRC_BASE}/productname. This currently does not work as it treats ${SRC_BASE} as a string and appends that to the default load directory location.
