If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 18/Jan/12 04:37 AM
Updated: 18/Jan/12 05:26 AM
|
|
Component/s: |
None
|
Affects Version/s: |
3.1.68
|
Fix Version/s: |
None
|
|
Original Estimate:
|
5 hours
|
Remaining Estimate:
|
5 hours
|
Time Spent:
|
Unknown
|
Environment:
|
Windows 7, connecting to either a virtual machine running Red Hat, or Dell dual core machines running Red Hat.
|
|
QuickBuild needs the capability of restricting the number of builds that each node can execute in parallel. By build, I mean complete configurations, including all steps within.
There are known methods for acquiring resources so that QuickBuild does not execute STEPS in parallel. However, this raises an issue when two configurations use the same external resource between steps. For example, one step may involve setting up a virtual machine for testing, and another step could connect to the machine and execute the tests. If a second configuration interrupts this process and modifies the state of the virtual machine, the test would be invalid.
Also, I followed http://wiki.pmease.com/display/QB31/Limit+Number+of+Concurrent+Jobs+on+Node, and modified each step within two of my configurations. When I played both configurations, I ended up with both stuck in a state of "Executing pre-execute action...". Neither wanted to release the resource "resource1", and I had to cancel both of the runs.
However, there should be an additional setting per node that specifies the number of concurrent jobs that are permitted to run on it.
|
Description
|
QuickBuild needs the capability of restricting the number of builds that each node can execute in parallel. By build, I mean complete configurations, including all steps within.
There are known methods for acquiring resources so that QuickBuild does not execute STEPS in parallel. However, this raises an issue when two configurations use the same external resource between steps. For example, one step may involve setting up a virtual machine for testing, and another step could connect to the machine and execute the tests. If a second configuration interrupts this process and modifies the state of the virtual machine, the test would be invalid.
Also, I followed http://wiki.pmease.com/display/QB31/Limit+Number+of+Concurrent+Jobs+on+Node, and modified each step within two of my configurations. When I played both configurations, I ended up with both stuck in a state of "Executing pre-execute action...". Neither wanted to release the resource "resource1", and I had to cancel both of the runs.
However, there should be an additional setting per node that specifies the number of concurrent jobs that are permitted to run on it. |
Show » |
No work has yet been logged on this issue.
|
|