This will almost certainly not fly. /home/ubuntu will also need permission
change. Adding a world writeable permission 777 is a very bad idea. I would
recommend that you add the go user to the same group as the ubuntu user,
and make sure the deployment folder has write permission for the ubuntu
gro
Looks like this is a bug that was introduced in v22.1.0. If you check
connection on a private URL and your auth isn't correct it will timeout the
entire server. I've verified it works in v21.4.0, v21.3.0, and v21.1.0.
I've bug reported this as I'm guessing the main server thread is doing the
c
I changed the user and group ownership of /home/ubuntu/app to go, although
777 should have sufficed for testing purposes.
When I su to user go, I am able to view /home/ubuntu/app, and also touch
foo.txt in /home/ubuntu/app . I
go@app:/home/ubuntu$ cd app
go@app:/home/ubuntu/app$ touch foo.txt
g
Howdy all,
Sorry got pulled off onto another project and just got back to this.
I did diff the log files from a clean launch of GoCD vs a crashing one. The
only difference was the JVM saying it was restarting.
I tried setting the wrapper.ping.interval and timeout.action and let it run
over nig
Hello Chris,
This appears to be a permissions issue rather than anything specific to
GoCD.
I recommend logging on to the Agent and manually running the script as the
GoCD user (via sudo or su). From there you should be able to troubleshoot
the permissions error.
Once the script runs properly
Hello
I face the following issue using gocd, with my gocd agent:
My app is containerized [docker] and needs to log via bind mount. The app
cannot log in the sandbox, as it does not have permissions to the log
directory.
I would like the app to be copied out from the sandbox, into
/home/ubuntu
