Hi Doug,
What you've described fits the static agent pattern better. We could try to
coerce that sort of behavior it into the elastic agent but it doesn't seem
natural to an elastic agent to work in that way.
I'd also like to point you to the "agent.replicaCount" setting in
values.yaml in the GoC
Hello Doug,
Yes, as Jason said a static agent might work. However, if it doesn't and
given that your question was about elastic agents, the answer would be "it
depends on the elastic agent plugin". The plugin interface definitely has
enough power to do this, since it controls almost all aspects of
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,
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
