Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

2023-11-14 Thread Chad Wilson
While getting a new plugin initially configured, I would use the UI to begin with, yes. Your `ls` command starts with 'gocd-' so is filtering out plugins that don't start with the same (such as the docker elastic agent plugin). If the version and list of plugins is correct on the admin > plugins

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

2023-11-14 Thread Chad Wilson
The pluginId in that cluster profile fragment refers to a completely different ec2 elastic agent plugin so not sure what you're trying to show us there  Personally, I don't think it's a good idea to be directly configuring cruise-config.xml especially for plugin-oriented config, since it

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

2023-11-13 Thread Chad Wilson
There's no such release. You should use a non-experimental release from https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases and find the link to the main jar file within that release. There should be no reason you cannot use the most recent release

[go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

2023-11-13 Thread Satya Elipe
Hi All Im containerizing my standalone GoCD server v22.3.0 with elastic agents, and looking for the elastic agents plugin jar file location for the version that works with server version v22.3.0 and use it in the container something like: docker run -d -p 8153:8153 -p 8154:8154 \ -v