![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Deluan Quintão
|
|
Components:
|
rtc, teamconcert |
|
Created:
|
26/Feb/14 4:47 PM
|
|
Description:
|
We are looking to use the same build project for multiple streams in rtc (parallel supported versioning). Currently if you try to add a parameter or variable to the build definition name or repository workspace name, the team concert plugin will not parse the variable and error out, not finding the correct definition/workspace. for example
parameter choice list :
stream = ver2.5, ver3.2, ver6.0
build definition = jenkins.$stream
adding this functionality would allow us to greatly expand our use of jenkins for production builds as well as testing processes for individual developer workspaces. Currently we are considering this a blocker for set up of developer testing.
the only know method around this is to set up a template project using another plugin.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
James Griffin
|
|
|
|
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/groups/opt_out.
