-
See https://github.com/gocd/gocd/issues/5937. V5 adds support for multiple clusters. We hope to get the v5 support in by 19.3 .
The idea is that an elastic profile will be associated with a cluster…
-
First, thank you for the template, very nice! I see you stopped publishing into the community-catalog repo as i also did ( .. https://github.com/EugenMayer/docker-rancher-extra-catalogs )
To the Go…
-
## Summary of issue
After restarting the GoCD server, the cluster status report is unable to render. `security_token` and `kubernetes_cluster_ca_cert` attributes on the cluster profile seem to be r…
-
This might not be the right place for it (should it be part of docker-swarm elastic agents or k8s maybe?). However, it will do for now.
The idea I want to discuss is the same as the title: Have a d…
-
Hi Guys,
I have noticed that the elastic agents do not get reused by the builds .
The plugin spins up another pod having the agent even if there is an idle one if I start the build
I am wonderi…
-
A lot of users running their GoCD servers within kubernetes.
Setting up a secret in GoCD involves choosing an auth method, which is currently either Token, AppRole or TLS.
For simplicity of setup, i…
-
Current Java agent accept a java properties file to setup and run in elastic-agents,
golang agent uses environment variables.
Because elastic-agents are in development, so we will wait until we have …
-
2.0.0 introduced terminating a pod immediately upon job completion which has proved useful when running many different pipelines with elastic agents, as nodes' resources are freed up quicker which red…
Evesy updated
5 years ago
-
#### Issue Type
Bug Report
#### Summary
When kubernetes pod for the elastic agent is starting up (let's say pulling the image), accessing the agent status report page throws an error with message…
-
##### Issue Type
- Feature proposal
##### Summary
For background: I'm asking this question in the context of moving the job detail page away from velocity + jstemplate to a spark based SPA.
…