
Key: |
QB-223
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Robin Shen
|
Votes: |
2
|
Watchers: |
1
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 19/Mar/07 05:44 PM
Updated: 06/Jun/09 11:02 PM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
From Forum Post:
I have configA, with child configAchild. configA uses explicitly queueA and child config uses queueAchild.
configA checks out from configAchild.
If I trigger configAchild, I can see it in its queue queueAchild, as expected.
But if I trigger configA, it in turn triggers configAchild, but I can only see configA in queueA. The child does not get put in its queue, and does not even appear at all in any build queue.
Thus it seems that I cannot control the number of children that can run in parallel directly.
Is that expected behaviour ?
|
Description
|
From Forum Post:
I have configA, with child configAchild. configA uses explicitly queueA and child config uses queueAchild.
configA checks out from configAchild.
If I trigger configAchild, I can see it in its queue queueAchild, as expected.
But if I trigger configA, it in turn triggers configAchild, but I can only see configA in queueA. The child does not get put in its queue, and does not even appear at all in any build queue.
Thus it seems that I cannot control the number of children that can run in parallel directly.
Is that expected behaviour ? |
Show » |
There are no comments yet on this issue.
|
|