Re: [go-cd] Elastic agents plugin usage

It seems you are using the third party EC2 Elastic Agent Plugin . This plugin does not implement the plugin API correctly and does not support environments correctly,

Re: [go-cd] Elastic agents plugin usage

Thank you Sriram. Please find my comments below. >Do the various jobs have an elastic profile ID set? Yes, I have two environments staging and prod, so we have separate profiles set for them. Here is pretty much what each profile has: 1. ec2_ami 2. ec2_instance_profile 3. ec2_subnets

Re: [go-cd] Elastic agents plugin usage

Can you be specific about the type of elastic agents you are creating and the plugin you are using. Kubernetes? Docker? Something else? There are many elastic agent plugins. > Here's where it gets tricky: when the staging job completes and triggers > the production job, I expect one of the

Re: [go-cd] Mount .ssh from EFS to the container (from the image gocd/gocd-server:v22.3.0)

On Thu, Apr 25, 2024 at 10:16 PM Satya Elipe wrote: > Hi all > > Wonder, what's the way around to mount .ssh from EFS into the gocd base > container (from the image gocd/gocd-server:v22.3.0). > > > We have saved all our content into EFS under /godata and maps that into > the container as

Re: [go-cd] Elastic agents plugin usage

On Thu, Apr 25, 2024 at 10:01 PM Satya Elipe wrote: > Hi All > > I'm encountering some issues with the way Elastic agents are launched, > assigned, and terminated. Despite setting the maximum agent count to two, > both agents launch sequentially, with only the first being assigned to the > job.

[go-cd] Mount .ssh from EFS to the container (from the image gocd/gocd-server:v22.3.0)

Hi all Wonder, what's the way around to mount .ssh from EFS into the gocd base container (from the image gocd/gocd-server:v22.3.0). We have saved all our content into EFS under /godata and maps that into the container as /godata. We are using gocd/gocd-server:v22.3.0. It all runs good,

[go-cd] Elastic agents plugin usage

Hi All I'm encountering some issues with the way Elastic agents are launched, assigned, and terminated. Despite setting the maximum agent count to two, both agents launch sequentially, with only the first being assigned to the job. Here's where it gets tricky: when the staging job completes and

Re: [go-cd] "/godata/db/h2db/cruise.mv.db" is locked

Sure, I will. Thank you . On Thu, Apr 25, 2024 at 2:56 PM Sriram Narayanan wrote: > > > On Thu, Apr 25, 2024 at 9:53 PM Satya Elipe wrote: > >> Thank you, Sriram. >> >> >> I managed to launch the new container alongside the old one. >> > > Good! > > >> >> As you use the Elastic Agents plugin,

Re: [go-cd] "/godata/db/h2db/cruise.mv.db" is locked

On Thu, Apr 25, 2024 at 9:53 PM Satya Elipe wrote: > Thank you, Sriram. > > > I managed to launch the new container alongside the old one. > Good! > > As you use the Elastic Agents plugin, can I ask you a question please. > Could you post this as a separate email question? That will help

Re: [go-cd] "/godata/db/h2db/cruise.mv.db" is locked

Thank you, Sriram. I managed to launch the new container alongside the old one. As you use the Elastic Agents plugin, can I ask you a question please. I'm encountering some issues with the way agents are launched, assigned, and terminated. Despite setting the maximum agent count to two, both

Re: [go-cd] GOCD server Db issue

You may have killed GoCD while it was starting up? If you are sure that you do not have multiple processes accessing the same database at the same time and it is still stuck, you will have to try manually clearing the lock