If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 06/Jul/16 02:08 AM
Updated: 21/Jul/16 01:31 AM
|
|
Component/s: |
None
|
Affects Version/s: |
6.1.14
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Hi Support Team,
I have Step1, Step2, Step3 and Step4 which are running in parallel, and they are running on 2 nodes which are in resource pool: Pool1. Each of these steps is doing several tests and then revert the node (to what it was before the test) after the test is completed. I am having an issue with this node distribution. For example, Step1 and Step2 are running on those 2 nodes, and Step3 and Step4 are waiting for available nodes. Let said Step1 is completed and executed the revert, but the step3 kicks in before the node to be inactive. The step 3 is failed because the node is down at a middle of the test. Looks like the node doesn't go in active node quick enough. May you advise me on how to handle this node distribution?
Thanks,
ptrinh
|
Description
|
Hi Support Team,
I have Step1, Step2, Step3 and Step4 which are running in parallel, and they are running on 2 nodes which are in resource pool: Pool1. Each of these steps is doing several tests and then revert the node (to what it was before the test) after the test is completed. I am having an issue with this node distribution. For example, Step1 and Step2 are running on those 2 nodes, and Step3 and Step4 are waiting for available nodes. Let said Step1 is completed and executed the revert, but the step3 kicks in before the node to be inactive. The step 3 is failed because the node is down at a middle of the test. Looks like the node doesn't go in active node quick enough. May you advise me on how to handle this node distribution?
Thanks,
ptrinh |
Show » |
|
1. the original step1, but set its node selection setting as "run on parent node"
2. add a step "remove from pool" running on server node executing below script:
groovy:
def attributes = parent.node.userAttributes;
attributes["active"] = "yes";
parent.node.setUserAttributes(attributes);
3. add a step "revert node" and set its node selection setting as "run on parent node", and have it execute the node reverting logic
Also make sure to modify Pool1 to add another constraint of only selecting node with attribute "active" defined as "yes".
This way you can exclude the node from Pool1 before it is reverted.