We have several Continua CI agents Each agent should be able to execute a job of a certain type, but only 1 job for that type at a given time. We are trying to find a way to use shared resource locks that will distribute the jobs on the agents based on agent+type combination availability: Job of …

Hi Arik, We made some changes in version 1.9.2.754 so that the $Buiild.SharedResources$ expression is populated before the agent requirements are evaluated. Now, if you set up a Server Shared Resource of type Quota List and enter a list of agent host names; [image] you can then set your stage to…

Hi Arik, There does not currently appear to be good way to achieve this goal with Continua CI, so we are now looking into what we can change to make this possible using shared resource locks. Meanwhile, can you elaborate on what you mean by “job” and “type”? Would “job” be a build or an individual…

[image] Sparky: Meanwhile, can you elaborate on what you mean by “job” and “type”? Would “job” be a build or an individual stage? Does “type” refer to the configuration, project or a variable value? Hi Dave, First, thanks for looking into this for us! By “job” I meant a Continua CI Configur…

Thank you Dave! I’ve only recently had a chance to evaluate this: First, Just wanted to note that agent conditions seems to break this: Since agent conditions are probably evaluated after the stage’s agent requirements had sent the build to the agent matching the shared resource lock expression -…

Hi Arik, You appear to be using Continua CI as a Continuous Deployment server rather than as a Continuous Integration server. The agents have really been designed as build runners rather than deployment targets. You can, however, still achieve these aims, but you will need to create a shared resou…

Thank you kindly for the detailed response Dave! [image] Sparky: You appear to be using Continua CI as a Continuous Deployment server rather than as a Continuous Integration server. The agents have really been designed as build runners rather than deployment targets. Sorry, I think I wasn’t …

[image] ktopaz: Can the “Acquire Expression” operation acquire multiple labels? No, it can only acquire one label. If you want to acquire more than one label repeat the line for each label. [image] ktopaz: list of services that a user checks in the queue options window using a “Checkbox …

We are using the “agent hostname as labels” locking mechanism for a couple of weeks now and it seems to work well! I’d only wish there was a way to have this work and have the system select the least busy agent for the next job being queued. Right now - as we have multiple configurations, each wit…

Hi Arik, Can you confirm that you are using the the “Acquire Any” operation to acquire the shared resource lock from the quota list? The labels currently do not have any order number in the database, so the first label which is chosen by this operation is currently arbitrary. Without any priority …

[image] Sparky: Can you confirm that you are using the the “Acquire Any” operation to acquire the shared resource lock from the quota list? I confirm, we indeed use “Acquire Any” as discussed earlier in this thread. [image] Sparky: we’ll make this change for the next version without requ…

Hi Arik, This has now been implemented in v1.9.2.978

VSoft Technologies Forums

Locking shared resources based on a combination of the selected agent and the job type?

Continua CI Discussion

Locking shared resources based on a combination of the selected agent and the job type?

Products

Support

Resources

Company