History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-710
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Major Major
Assignee: Steve Luo
Reporter: Jasmin Lapalme
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

Support for multiple trac servers

Created: 27/Oct/10 02:56 PM   Updated: 27/Dec/12 02:37 PM
Component/s: None
Affects Version/s: 3.0.16
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
It would be useful to have a way to specify multiple trac server. In our environment, we have three separate trac servers for a same project (include three major components). We have a default trac server which we write #1234 to specify a ticket number. All the others are specified by adding a prefix (ex: tracyyy:#1234).

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [27/Oct/10 11:23 PM]
How about solve the problem by separate your project build into three configurations: one of each major component. And then you may set up different Trac server for different configuration. To aggregate build results of these components, you may set up a separate configuration to depend on them so that component artifacts can be collected and packaged into a single product.