If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 28/Jun/17 03:27 PM
Updated: 25/Jan/18 12:21 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Quickbuild Software
|
|
We would like to be able to be able to grammatically keep a job queued.
I have a configuration that I want to run concurrently but block concurrent runs for build requests with identical variables. I don't want to throw out the request (as I could easily do in a Pre-Queue Script) but instead want to allow the request to be queued up but not run until the duplicate request is finished.
|
Description
|
We would like to be able to be able to grammatically keep a job queued.
I have a configuration that I want to run concurrently but block concurrent runs for build requests with identical variables. I don't want to throw out the request (as I could easily do in a Pre-Queue Script) but instead want to allow the request to be queued up but not run until the duplicate request is finished.
|
Show » |
|
1. define two resources mirrorA, and mirrorB, with ONE count respectively on some node
2. define a variable say "mirrorDestination", and prompt as "selection box", with choices as:
${groovy:
def choices = "";
for (resource: com.pmease.quickbuild.entitymanager.ResourceManager.instance.getAll()) {
if (resource.getName.startsWith("mirror"))
choices += resource.getName() + ",";
\}
}
3. define node selection setting of your data mirror step to be "run on node with specified resource", and then define the resource as:
${vars.getValue("mirrorDestination")}
4. Also pass value of variable mirrorDestination to your data mirror step so that you can mirror data to desired destination