Comment by
Robin Shen
[
20/Oct/14 09:51 PM
]
|
This is not a bug. The node selection setting "on step running parent step" or "on step running previous sibling step" only tells the step to run on that particular agent but does not prevent that agent from running other steps of other builds as QuickBuild agent by design is able to run multiple steps concurrently. If you would like to prevent other steps from running, you will have to define a resource with only one count on that node and make parent step of involved steps to require that resource. For details please check resource on our wiki.
|
Comment by
ChangSeop LEE
[
20/Oct/14 11:45 PM
]
|
I understand your concept and appreciate concurrency of Quickbuild system also.
But sometimes we are facing unexpected changing of buildagent like I mentioned even we defined a resource with only one count.
We defined a resource with about 500 agents and only one count on that node to reduce wasting of agents.
And using the resource on thousands of configurations and each steps require the same resource.
Can you recommend a best way for preventing aforementioned problem?
|
Comment by
Robin Shen
[
22/Oct/14 05:47 AM
]
|
Can you please send me [robin AT pmease DOT com] your database backup (can be done via administration / database backup), and let me know which step of which build experience this issue, and which agent is in problem?
|
Generated at Tue May 21 01:26:55 UTC 2024 using JIRA 189.