We haven't started leveraging elastic agents yet so I can't comment on whether or not what you are looking to do is possible but if the restriction truly is for a single instance, why not use a single static agent instead of an elastic agent profile?
On Tuesday, 3 September 2019 09:43:55 UTC-4, Doug Lethin wrote: > > I have a use case where I would like to limit the number of parallel jobs > running on a particular elastic agent profile in our kubernetes cluster to > just one at a time. If GoCD is currently executing a job with this elastic > again profile I would want all pending jobs associated with the elastic > agent to wait until the currently running agent finishes. Is this current > possible? If so, its not immediately obvious how to do it. I thought > maybe using kubernetes ResourceQuota's might solve the problem. I hadn't > tried that yet, but my guess is it wouldn't work causing the request to > spin up the next against to fail rather than wait. > > The use case I have is that the agent has a dependency on a fixed resource > that can't be shared. > > Thanks. > > > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/8720fded-59d2-4e29-afa3-5862a472a581%40googlegroups.com.
