<< Back to previous view

[QB-351] Parallel Trigger Remote (with option to wait for results, QB-335)
Created: 13/May/08  Updated: 25/Jun/10

Status: Resolved
Project: QuickBuild
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Justin Georgeson Assigned To: Robin Shen
Resolution: Fixed Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown
Environment: main QB instance on Linux, build machines Linux, Solaris, and Windows


 Description   
Virtually all of our build configurations on our main server are just doing a checkout from SCM, publishing the source as an artifact, and running identical remote build configurations on multiple machines, waiting for each one to complete. There is already a request to add an option to have Trigger Remote Build block for completion (QB-335) so I don't need to request that here. All I need is a single step that can take a list of remote QB servers, and run Trigger Remote on all of them in parallel. This way I don't have to configure 20 QuickBuild Repositories and 20 Checkout steps from those Repositories to get a build running on all necessary machines.

 Comments   
Comment by Justin Georgeson [ 08/Jun/09 08:09 AM ]
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?
Comment by Robin Shen [ 08/Jun/09 03:13 PM ]
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.
Comment by Justin Georgeson [ 08/Jun/09 03:21 PM ]
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.
Comment by Robin Shen [ 08/Jun/09 03:34 PM ]
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.
Comment by Robin Shen [ 25/Jun/10 08:51 AM ]
This can be done now in 3.0 beta1 with step repetition parameters.
Generated at Sat May 04 13:45:17 UTC 2024 using JIRA 189.