Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 21:37
    ibnc synchronize #5756
  • Jan 31 2019 20:02
    ibnc synchronize #5756
  • Jan 31 2019 19:07
    arvindsv commented #3304
  • Jan 31 2019 19:06
    arvindsv commented #3304
  • Jan 31 2019 18:59
    varshavaradarajan synchronize #5791
  • Jan 31 2019 18:24
    ibnc synchronize #5756
  • Jan 31 2019 18:11
    mushycode commented #3304
  • Jan 31 2019 17:29
    GaneshSPatil opened #5797
  • Jan 31 2019 15:22
    arvindsv unpinned #5776
  • Jan 31 2019 15:07
    arvindsv commented #3304
  • Jan 31 2019 15:07
    arvindsv commented #3304
  • Jan 31 2019 14:59
    arvindsv commented #5796
  • Jan 31 2019 14:09
    akshaydewan commented #5796
  • Jan 31 2019 13:21
    maheshp commented #5796
  • Jan 31 2019 12:42
    ketan commented #5795
  • Jan 31 2019 12:39
    ketan commented #5795
  • Jan 31 2019 12:38
    JorritSalverda commented #5795
  • Jan 31 2019 12:35
    JorritSalverda commented #5795
  • Jan 31 2019 12:35
    JorritSalverda closed #5795
  • Jan 31 2019 12:00
    mushycode commented #3304
lynnxia517
@lynnxia517
I wanna make task pass or failed according to the script execution result. But it is not exepected. anyone knows what's the problem?

[go] Task: Plugin with ID: script-executortook: 0.196s
[script-executor] OS detected: 'Linux'. Is Windows? false
[script-executor] Script:

[script-executor] -------------------------
! grep "failed" /home/pi/lxia/web_test/webdriver_test.log

echo $?
[script-executor] -------------------------
[script-executor] Script Type: bash
[script-executor] Script written into '/home/pi/go-agent-20.10.0/pipelines/Test/21b80e6b-f0b5-45d8-b48a-59b0238dfd2f.sh'.
2020-12-22 17:47:55,848 WARNING : login_test_login failed: 'Time-Entry' != 'Time Entry'
: failed. Page title is not expected
1
[go] Task status: passed, took: 0.196s

I've got the status code of script: 1. why the task is still 'passed'
Aravind SV
@arvindsv
The status of a shell script is the status of its last executed statement. In your case, it seems to be: echo $?. The exit status of the echo is 0, which is success. So, the task succeeds.
Of course, it doesn't matter that the exit status of the command before the final statement grep is non-zero, since the echo is the final statement.
lynnxia517
@lynnxia517
Thanks. @arvindsv
jmanuelortiz
@jmanuelortiz
Hi guys
Is this a chat for quick question of only for contributors?
marques-work
@marques-work
Anyone can ask
jmanuelortiz
@jmanuelortiz
thanks ...
I am upgrading from 19.3.0 to 19.12.0
  • Server has been upgraded
  • Linux agents are working using agent v19.3.0
  • elastic linux agents working using agent v19.3.0
  • I can get get windows (dockerized) agents to connect using v19.12.0, i upgraded to java 12 services is running but logs show
2020-12-23 22:47:24,883 ERROR [WrapperJarAppMain] ServerBinaryDownloader:82 - Couldn't update admin/agent-launcher.jar. Sleeping for 1m. Error:
org.apache.http.conn.HttpHostConnectException: Connect to localhost:8154 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
jmanuelortiz
@jmanuelortiz
my GO_SERVER_URL is already setup
looks like is not taking the value .. ive set

PS C:\gocd-agent\go-agent-19.12.0\logs> gc .\go-agent-bootstrapper-wrapper.log
STATUS | wrapperm | 2020/12/23 22:46:03 | go-agent service installed.
STATUS | wrapperm | 2020/12/23 22:46:10 | Starting the go-agent service...
STATUS | wrapper | 2020/12/23 22:46:10 | --> Wrapper Started as Service
STATUS | wrapper | 2020/12/23 22:46:10 | Java Service Wrapper Standard Edition 64-bit 3.5.41
STATUS | wrapper | 2020/12/23 22:46:10 | Copyright (C) 1999-2019 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2020/12/23 22:46:10 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2020/12/23 22:46:10 | Licensed to ThoughtWorks for GoCD Agent
STATUS | wrapper | 2020/12/23 22:46:10 |
STATUS | wrapper | 2020/12/23 22:46:13 | Launching a JVM...
INFO | wrapperm | 2020/12/23 22:46:15 | Waiting to start...
INFO | jvm 1 | 2020/12/23 22:46:14 | WrapperManager: Initializing...
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] Starting process:
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] Working directory : C:\gocd-agent\go-agent-19.12.0
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] Application arguments: [-serverUrl, https://localhost:8154/go]
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] GoCD Version: 19.12.0-10888
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] Java Version: 12.0.1
INFO | jvm 1 | 2020/12/23 22:46:16 | [Wed Dec 23 22:46:16 GMT 2020] Operating System: Windows Server 2016(10.0)
INFO | jvm 1 | 2020/12/23 22:46:17 | Could not find file config\agent-bootstrapper-logback.xml'. Attempting to load from classpath. INFO | jvm 1 | 2020/12/23 22:46:17 | Using classpath resourcejar:onejar:lib/agent-bootstrapper-19.12.0-10888-classes.jar!/config/agent-bootstrapper-logback.xml'.
INFO | jvm 1 | 2020/12/23 22:46:18 | SLF4J: Class path contains multiple SLF4J bindings.
INFO | jvm 1 | 2020/12/23 22:46:18 | SLF4J: Found binding in [jar:onejar:lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
INFO | jvm 1 | 2020/12/23 22:46:18 | SLF4J: Found binding in [jar:file:/C:/gocd-agent/go-agent-19.12.0/data/deps-3743202ae70745ae-agent-launcher.jar/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
INFO | jvm 1 | 2020/12/23 22:46:18 | SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
INFO | jvm 1 | 2020/12/23 22:46:18 | SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
INFO | jvm 1 | 2020/12/23 22:46:18 | Could not find file config\agent-launcher-logback.xml'. Attempting to load from classpath. INFO | jvm 1 | 2020/12/23 22:46:18 | Using classpath resourcejar:file:/C:/gocd-agent/go-agent-19.12.0/data/deps-3743202ae70745ae-agent-launcher.jar/agent-launcher-19.12.0-10888-classes.jar!/config/agent-launcher-logback.xml'.
marques-work
@marques-work
Sorry I will have to get back to you. I am driving right now and can’t really look at this yet. However if anyone else wants to jump in on this feel free
jmanuelortiz
@jmanuelortiz
No problem
I will have a look at this note
marques-work
@marques-work
@jmanuelortiz is the server url not localhost:8154? Try setting it in wrapper-config rather than environment.
And of course validate network connectivity to the host/port from the agent as a sanity check
marques-work
@marques-work

@jmanuelortiz we moved configuration to wrapper-properties.conf as of 19.6. From the issue you posted:

The agent will no longer honor the GO_SERVER_URL environment. This environment variable will be removed upon upgrade.

If the file config/wrapper-properties.conf exists, you must add the following config options to that file (substituting the appropriate GoCD server URL).

wrapper.app.parameter.100=-serverUrl
wrapper.app.parameter.101=<https://your-gocd-server:8154/go>
1 reply
Syam Pradeep Reddy
@syam38
Screenshot 2020-12-29 at 5.50.04 PM.png
I am trying to install a package in gocd agent and when the corresponding task runs, the gocd console gives me the above error. Does anyone has an idea about this.
Syam Pradeep Reddy
@syam38
The command I am trying to run is npm install n -g, I added the arguments in separate line in custom command
marques-work
@marques-work
Paste your task config xml?
Looks like your command isn’t constructed properly
@syam38 ☝🏼
Kelly Schoenhofen
@kellyschoenhofen
Super simple setup question - I want to force https for everyone, I started with haproxy and then I saw the apache/nginx documentation ;) so I'll probably switch to apache, but what's the right away to redirect http to https? In haproxy, I bound to both 80 and 443, redirected to 443, and the backend pointed to 8153. Except http://server:8153 is still listening to requests.
What's the right way to address this?
1 reply
jmanuelortiz
@jmanuelortiz

Hey quick question for windows agents ...
I am using containerized windows agents .... which user use gocd to run the agent ??

Previously i was using ContainerAdministrator, but after upgrading to 19.12.0 version i am getting Host key verfication failed

6 replies
AntoineProvot
@AntoineProvot
Hi, I'm currently trying GoCD for our CICD purposes and I face problems with webhooks when trying to reach the gocd server. I tried several api POST features but none of them are triggering the pipeline I created. We're using Gitea as a git service and I'm wondering : is it even possible to trigger gocd from gitea/gogs using webhooks?
marques-work
@marques-work
GoCD supports webhook payloads from GitHub, gitlab, and bitbucket for push events
The webhook headers, auth, and payload would need to mimic one of those services in order to trigger a material update (and subsequently pipelines)
1 reply
marques-work
@marques-work
It looks like Gitea comes close, but not enough to GitHub
Yeah - the auth isn’t correct
For GitHub it wants an hmac calculated against the payload and webhook secret to be on the X-Hub-Signature header
marques-work
@marques-work
For gitlab it wants the webhook secret at x-gitlab-token
So gitea isn’t sending either of those headers

Otherwise it mimics the GitHub payload body well enough (we only check for the ref and repository chunks), as well as x-GitHub-event.

But the auth is wrong.

I’m looking at this example in the Gitea docs as a basis for my claim: https://docs.gitea.io/en-us/webhooks/
marques-work
@marques-work
Doesn’t look like there’s an obvious workaround unless you know how to configure gitea to send the hmac as x-hub-signature
@AntoineProvot ☝🏼
AntoineProvot
@AntoineProvot
Thank you very much for the confirmation @marques-work ! Have a good day!
marques-work
@marques-work
You as well
suzhang85
@suzhang85
Hi , I 'm new to gocd. go-agent and go-server is running in different PC. but the go-agent can't connect to go server with below exception:
2021-01-13 08:58:59,218 ERROR [scheduler-1] AgentHTTPClientController:105 - Error occurred when agent tried to ping server:
org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [http://10.22.1.41:8153/go/remoting/remoteBuildRepository]; nested exception is 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/20.10.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:226)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:153)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
at com.sun.proxy.$Proxy11.ping(Unknown Source)
at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:100)
at jdk.internal.reflect.GeneratedMethodAccessor11.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/20.10.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details.
at com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.validateResponse(GoHttpClientHttpInvokerRequestExecutor.java:100)
at com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.doExecuteRequest(GoHttpClientHttpInvokerRequestExecutor.java:66)
at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:137)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:202)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:184)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:150)
... 15 common frames omitted
could any one help me?
the agent is not shown in the list on server.
Cristiano Fontes
@cfontes
Hello everybody
We are facing a pretty nasty prod issue with our GoCD server
please take a look if you can, I have no idea what to do anymore.