|
|
|
[
Permlink
| « Hide
]
Robin Shen [25/Jun/10 08:51 AM]
This can be done now in 3.0 beta1 with step repetition parameters.
Reopened this issue.
Just as I've mentioned above, with the new build grid feature, you probably can set up only one QuickBuild server to include all configurations previously scattered in different servers. This will greatly reduce the maintenance overhead. But that's not what this request was for. This request was to have a single step to configure that runs the same config on multiple remote machines in parallel. If I have 5 machines to run root.myconfig on, why should I have to setup 6 steps (5 remote trigger and one parallel composition to call the 5 trigger steps)? If I want to pass artifacts between machines then I need 5 QB repos and 6 steps. I should be able to do both these with a single step. Please reclassify this RFE as it isn't resolved.
Yes, for simplicity reason, a single QuickBuild repository and remote trigger step only works for one server. However the remote trigger step is able to trigger multiple configurations on the same server parallelly (either locally or on some other servers). Since QuickBuild 2.0 is able to handle remote build through build agents, multiple QuickBuild servers are rarely needed.
We have 2.0 beta2 loaded, and I'm looking for the UI to configure this. I looked at both the QuickBuild repo config and the "Trigger Other Builds" step config, and they both have a checkbox to specify a remote server URL, but only one. How do I configure multiple remote URL's for a parallel trigger?
|