Hi there ... I wanna give gocd a try, but currently I can't manage to get version 21.2.0 docker to see the agent. I am using this 2 docker images: gocd/gocd-server:v21.2.0 and gocd/gocd-agent-debian-10:v21.2.0 on my local environment. I have started the agent docker image like this:
docker run -itd --name gocd-agent -e CI=true -e GO_SERVER_URL=https://$(docker inspect --format='{{(index (index .NetworkSettings.IPAddress))}}' gocd-server):8153/go gocd/gocd-agent-debian-10:v21.2.0but unfortunately I can't see the agent in the agent view in the gocd ui. Is there a special way to run the agent docker image in order to see it in the gocd ui?
Hi all,
I'm trying to setup an auto registration remote agent on aws but I'm stuck due to the following error:
My current configuration:
- [go-server] /etc/gocruise-config.xml:
<?xml version="1.0" encoding="utf-8"?> <cruise xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="cruise-config.xsd" schemaVersion="139"> <server agentAutoRegisterKey="195ea125-5d3a-4d33-8cc7-5c0e482cc0e7" webhookSecret="..." serverId="..." tokenGenerationKey="..."> <security> - [go-agent] /var/lib/go-agent/config/autoregister.properties
agent.auto.register.key=195ea125-5d3a-4d33-8cc7-5c0e482cc0e7 agent.auto.register.hostname=agent-01 agent.auto.register.elasticAgent.agentId=7f5e55d20407 agent.auto.register.elasticAgent.pluginId=com.example.aws
With these settings I'm getting the following error:
go-server (/var/log/go-server/go-server.log):
2021-07-21 06:44:21,034 ERROR [qtp993070390-40] AgentRegistrationController:242 - Rejecting request for registration. Error: HttpCode=[422] Message=[Elastic agent registration requires an auto-register agent key to be setup on the server. The agentAutoRegisterKey: [195ea125-5d3a-4d33-8cc7-5c0e482cc0e7] is either not provided or expired. Agent-id: [7f5e55d20407], Plugin-id: [com.example.aws]] UUID=[bbbfd276-ce32-430f-81f5-69dbc3cea571] Hostname=[4255f57b7ca5]ElasticAgentID=[7f5e55d20407] PluginID=[com.example.aws]go-agent (/var/log/go-agent/go-agent.log):
2021-07-21 06:44:16,390 ERROR [scheduler-2] RemotingClient:166 - Server responded to action `ping` with: status[403 Forbidden], body[] 2021-07-21 06:44:16,393 ERROR [scheduler-2] AgentHTTPClientController:114 - Error occurred when agent tried to ping server: java.lang.RuntimeException: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include: - This agent has been deleted from the configuration - This agent is pending approval - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details. at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:118) at com.thoughtworks.go.agent.RemotingClient.ping(RemotingClient.java:74) at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:109) ... at java.base/java.lang.Thread.run(Unknown Source) Caused by: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include: - This agent has been deleted from the configuration - This agent is pending approval - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details. at com.thoughtworks.go.agent.RemotingClient.validateResponse(RemotingClient.java:141) at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:114) ... 14 common frames omitted 2021-07-21 06:44:21,043 ERROR [scheduler-1] SslInfrastructureService:173 - Error occurred during agent registration process: Elastic agent registration requires an auto-register agent key to be setup on the server. The agentAutoRegisterKey: [195ea125-5d3a-4d33-8cc7-5c0e482cc0e7] is either not provided or expired. Agent-id: [7f5e55d20407], Plugin-id: [com.example.aws]
Could anyone help me with this issue?
Thanks!
Hi all,
We've been working on setting up multiple agents for pipeline.For allocating jobs to agents as far as the documentation we've gone through.we needt to manually assign the resource to the agents.Is there any way to random assign agents to jobs without doing manually.
1 reply
Good day! I might have posted this before, but I did not see an answer: I am trying to run gocd in an IPv6 only kubernetes cluster. However the gocd never starts, but errors out with:
Warning FailedPostStartHook 4m22s kubelet Exec lifecycle hook ([/bin/bash /preconfigure_server.sh]) for Container "gocd-server" in Pod "gocd-server-5b8fb6b58f-54qc8_default(799b2a6e-aa1c-4292-b091-4b500a0ab857)" failed - error: command '/bin/bash /preconfigure_server.sh' exited with 137: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed(lots of repetitions)
3 replies
@skele10 Correct, however on August 13th GitHub changed what is allowed for logging in and I receive this message now for Materials:
STDERR: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
STDERR: remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
STDERR: fatal: unable to access 'https://github.com/my-repo': The requested URL returned error: 403
Hey Folks, is there a way to install multiple agents on windows? I tried silent setup but the installer detects existing agent and exists...
Install using Generic zip is the answer :) : https://docs.gocd.org/current/installation/install/agent/zip.html
I tried locally and have few questions regarding how-to,
- Can we configure a pipeline without git dependency / material? We have a pipeline which runs on a schedule and the pipeline is just pure shell script (and it does not depend on any code from any repo).
- How to configure multi-branch pipeline? For example, we have an frontend repo with different branch for different environment, like dev, prod, … so that when triggering the pipeline manually, we can select which branch to trigger from.
- Here is a complex scenarios which we trying to resolve. We have 2 repo, 1 for frontend and 2 for backend. The backend pipeline will be dependent on frontend pipeline. Whenever the frontend pipeline build is successful, it should trigger backend pipeline. Also if there is any change in backend repo, it should trigger backend pipeline. I’m able to configure this by adding multiple dependencies for backend pipeline. The complexity here is, we generated random key when building frontend (For eg.: KEY=hash-BUILD-1), and the same needs to be passed to backend pipeline.
a. How to trigger backend pipeline with custom build parameter (KEY)? From pipeline 1 it should pass parameter and value for pipeline 2 build.
b. How to persist param value (KEY) in backend pipeline, so that subsequent build from backend repo (commits, poll scm) trigger will use the param value (KEY) which is already set. Param value changes only when frontend pipeline creates a new build.
For #1: No, you need to have a material. But, it can be a dummy material, with polling turned off. So, it'll only trigger on timer.
For #3: The way to pass information between pipeline instances in usually via artifacts. You'd publish an artifact (can be any file) in the frontend pipeline with that key / param. You can then fetch that artifact from the upstream (frontend) pipeline in the downstream pipeline (backend) and use it. If you ever re-run the backend pipeline instance, it'll get that artifact again and use it. That same version of the artifact. You can verify the versions in the VSM.
- As part of UAT or Production build, we do git tag and push it through build pipeline script. Is there a way to ignore such commits? Usually we add like
[skip]in git commit message and CI/CD pipeline will ignore it. Anything similar in GoCD?
1 reply
nixos-rebuild build --flake git+ssh://some.remote/user/flake
Hi all, I see someone asked about this in June as well, but in the hope that at some point someone from gocd might read this. Since I updated to the latest gocd version, and did the same for go-agent, I keep hitting:
2021-09-16 08:37:02,448 ERROR [scheduler-2] RemotingClient:166 - Server responded to action `ping` with: status[403 Forbidden], body[]
2021-09-16 08:37:02,449 ERROR [scheduler-2] AgentHTTPClientController:114 - Error occurred when agent tried to ping server:
java.lang.RuntimeException: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include:
- This agent has been deleted from the configuration
- This agent is pending approval
- There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:118)
at com.thoughtworks.go.agent.RemotingClient.ping(RemotingClient.java:74)
at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:109)
at jdk.internal.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65)
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include:
- This agent has been deleted from the configuration
- This agent is pending approval
- There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
at com.thoughtworks.go.agent.RemotingClient.validateResponse(RemotingClient.java:141)
at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:114)
... 13 common frames omittedI deployed the latest helm chart, and I've tried an existing go-agent, as well as using the provided go agent daemonset. Both hit this same error. I configured my k8s instance with valid ssl certificates etc., so the suggestions w/r/t reverse proxies doesn't seem to make sense.
1 reply
jvm 1 | 2021-09-16 17:15:08,016 WARN [Thread-78] PluginSettingsMetadataLoader:63 - Failed to fetch plugin settings metadata for plugin cd.go.contrib.elasticagent.kubernetes. Maybe the plugin does not implement plugin settings and view? + huge stack trace of course, and I no longer see any of the failed remote agent "ping" requests, even though the agents keep printing they get 403's
jvm 1 | 2021-09-17 08:03:55,172 INFO [qtp1374887279-28] RequestLog:28 - 10.42.0.1 - - [17/Sep/2021:08:03:55 +0000] "POST /go/remoting/api/agent/ping HTTP/1.1" 403 0 1
jvm 1 | 2021-09-17 08:04:00,182 INFO [qtp1374887279-29] RequestLog:28 - 10.42.0.1 - - [17/Sep/2021:08:04:00 +0000] "POST /go/remoting/api/agent/ping HTTP/1.1" 403 0 1
[pid 2927458] 1631866185.681554 <... read resumed>"POST /go/remoting/api/agent/ping HTTP/1.1\r\nHost: ***\r\nX-Request-ID: d537cf703cb517a52982aa86744f7083\r\nX-Real-IP: 10.42.0.1\r\nX-Forwarded-For: 10.42.0.1\r\nX-Forwarded-Host: ***\r\nX-Forwarded-Port: 443\r\nX-Forwarded-Proto: https\r\nX-Scheme: https\r\nContent-Length: 428\r\nAccept: application/vnd.go.cd+json\r\nX-Agent-GUID: 3f2771f3-1fd2-4093-a896-4bba33ae9ca2\r\nAuthorization: c2lyAYi0TfYXcaKuEd80oCjhoam9f3vEwm3zySsTrPE=\r\nContent-Type: application/json; charset=UTF-8\r\nUser-Agent: Apache-HttpClient/4.5.13 ("..., 8192) = 1047
[pid 2927458] 1631866185.683503 writev(421, [{iov_base="HTTP/1.1 403 Forbidden\r\nDate: Fri, 17 Sep 2021 08:09:45 GMT\r\nX-XSS-Protection: 1; mode=block\r\nX-Content-Type-Options: nosniff\r\nX-Frame-Options: SAMEORIGIN\r\nX-UA-Compatible: chrome=1\r\nContent-Length: 0\r\n\r\n", iov_len=204}], 1 <unfinished ...>
[pid 2927458] 1631866185.684559 write(48, "2021-09-17 08:09:45,684 INFO [qtp1374887279-40] RequestLog:28 - 10.42.0.1 - - [17/Sep/2021:08:09:45 +0000] \"POST /go/remoting/api/agent/ping HTTP/1.1\" 403 0 3\n", 161 <unfinished ...>
[pid 2927458] 1631866185.685155 write(1, "2021-09-17 08:09:45,684 INFO [qtp1374887279-40] RequestLog:28 - 10.42.0.1 - - [17/Sep/2021:08:09:45 +0000] \"POST /go/remoting/api/agent/ping HTTP/1.1\" 403 0 3\n", 161 <unfinished ...>sudo apt install --reinstall -o Dpkg::Options::="--force-confask,confnew,confmiss") , and the helm provided agent deployment is also not working. at least I got something working now. If someone finds this on google perhaps they will find it useful, if you've updated. Best just purge the existing agents completely, don't try to update them, and don't try to use the agents that are prepared by helm.
I am trying to configure go cd behind nginx reverse proxy. I followed the documentation, but when I access gocd using url domain.com/go, its giving a 404 page (the browser url now is /go/pipelines) . My nginx config file is
location /go/ {
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_http_version 1.1;
proxy_pass http://localhost:8153/go;
client_max_body_size 10000m;
}Is there any other changes I need to do to make this working?
3 replies
Hey everybody! I am quite new to GoCD, love it so far! I had a question about webhooks. Can somebody point me to the documentation to the feature this PR introduced gocd/gocd#8023 ?
More specifically, I am looking for the payload config_repo webhook is expecting. Basically, my code is hosted on codecommit (not on GitHub/BitBucket etc). So my plan was to intercept codecommit trigger, convert it into one of the expected payloads to trigger webhook.
I was able to get it to work mostly, but I encountered an issue. Looks like GoCD only triggers the pipeline for branch configured in Config Repo. So, I was planning to mask the branch and convert it to whichever is configured before sending the payload. If I can get what payload GoCD is expecting, maybe I could get it to refresh the material for other branches too?