[go-cd] GO_TRIGGER_USER recorded as "changes" when pipeline is manually triggered through GoCD UI by admin

Hi, I've noticed today that the GO_TRIGGER_USER variable is being set to "changes" when I trigger a pipeline manually. I do see in the pipeline screen that pipeline was triggered by myself, my GoCD user but the variable value doesn't match this. It should only be set to "changes" when it's trig

[go-cd] Re: GO_TRIGGER_USER recorded as "changes" when pipeline is manually triggered through GoCD UI by admin

Hello, The GO_TRIGGER_USER environment variable is based on who triggered a stage. On the dashboard, the trigger message `Triggered by admin` refers to who triggered the first stage. I am not sure which console log you've attached, whether its for the first or the second stage. If its for the s

[go-cd] Re: GO_TRIGGER_USER recorded as "changes" when pipeline is manually triggered through GoCD UI by admin

Hi, It was indeed for the 2nd stage which is according to your explanation. I now verified the 1st stage and it shows "admin". We have a wrapper for the execution on the go-agent side which was relying on some verifications of who has triggered the pipeline but given this information I will ha

Re: [go-cd] Re: Faster method to add/append artifacts?

Cool. Thanks for confirming. The documentation PR is submitted: https://github.com/gocd/api.go.cd/pull/232. Should show up soon. -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an e

[go-cd] Agent Health API endpoint

I have a server and agent running v18.2.0. Running the Agent Health endpoint as documented in the GoCD API Reference returns a 404. Other API endpoints and my pipelines are all running fine. I have tried both `/health/v1/isConnectedToServer` and `/

Re: [go-cd] Agent Health API endpoint

I suspect that you're accessing the endpoint remotely. For security reasons — the endpoint is only bound to the local-loop interface (localhost/ 127.0.0.1). So you'll have to invoke with `localhost/127.0.0.1` instead of whatever host/ip you're using. If you'd like to bind this to a different IP or