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
Rasmus Hartvig
@rhartvig
@marques-work , thanks for swift response, much appreciated!
marques-work
@marques-work
You’re welcome 👍🏼
Aditya M
@adityam01
Screen Shot 2020-12-17 at 8.05.49 PM.png
Hey there all + @marques-work , went through 30 minutes of struggle, and still not able to download ^
any thoughts?
marques-work
@marques-work
@adityam01 I haven’t looked at this script for a long time. But the error seems to indicate your wget installation didn’t install openssl. There isn’t a reason we need wget over curl in the script since curl can do everything wget can. Let me take a look and see if I can fix it. In the meantime, you could try reinstalling your wget package (guessing homebrew)?
Aditya M
@adityam01
awesome thanks. will try that
marques-work
@marques-work
You might need to reinstall openssl too since it reports it cannot find that dynamic library
Aditya M
@adityam01
working - thanks @marques-work
marques-work
@marques-work
@adityam01 actually, what should work better is to uninstall wget if you don’t need it. The script will fall back to curl if wget isn’t on the path
Meanwhile I’m removing that part of code altogether. We should just use curl only.
Aditya M
@adityam01
:thumbsup:
marques-work
@marques-work
@adityam01 Ok, I’ve published the fix to the website. It should no longer try to use wget even if it’s on your path. LMK if you run into any more issues
lynnxia517
@lynnxia517
@rhartvig @marques-work understood. Thanks a lot.
marques-work
@marques-work
:thumbsup:
ssanchez227
@ssanchez227
@marques-work thank you for responding to my question. What I would like to do is have a list of options available that a user can select from when manually triggering a pipeline. i.e. I have a pool of VMs developers can deploy to. I would like to have the user select from a list of VMs (instead of typing the VM name in) and I would then deploy the build to a share in that VM. Thanks.
marques-work
@marques-work

@ssanchez227 ok, I see. There isn’t a way to have prepopulated suggestions for env variables on the trigger with options modal AFAIK.

However, maybe there are other ways to solve your problem:

  • if your users are statically assigned VMs in the pool, maybe you could make a mapping in your build script that chooses the appropriate VM based on the user that kicked off the build. This username is exposed to your jobs as the GO_TRIGGER_USER environment variable
  • or, if the pool size is small, templatize your build and create a pipeline to deploy to each VM. The added benefit is that your builds to each VM can run concurrently if you have enough eligible agents to run
  • or, you can create a script for you users to run that will trigger the pipeline with the correct variable using the API with a personal access token, sourcing the vm from the user’s local environment (also assumes there is some consistent association between users and vms). This is more setup, but maybe is more convenient in the long run for devs

Maybe someone more clever than me has a better idea

lynnxia517
@lynnxia517
hello, everyone! I have a query. go-agent on the rasberry pi, and it will get the code from git. where should I put the key on the agent?
marques-work
@marques-work
Are you asking about an ssh key?
@lynnxia517 ☝🏼
lynnxia517
@lynnxia517
yeah
marques-work
@marques-work
ssh keys are by default expected in $HOME/.ssh of the user making the handshake
So it depends on what user owns the go agent process
lynnxia517
@lynnxia517
$HOME means the agent's work dir?
marques-work
@marques-work
If you started the process as the pi user, then ~pi/.ssh
No it means the user’s home directory
Standard meaning in unix, in other words
So use whichever user’s home directory that owns the agent PID
lynnxia517
@lynnxia517
got it. thanks a lot
marques-work
@marques-work
👍🏼
Don’t forget to chmod 0400 /path/to/your/key
lynnxia517
@lynnxia517
yeah. thanks for the reminder. I've got the warning. haha
marques-work
@marques-work
Np, hope it works
lynnxia517
@lynnxia517
after chmod, it works
marques-work
@marques-work
Good to hear
lynnxia517
@lynnxia517
:)
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