20.1.0
, some of the pipelines are not getting triggered and shows a blank screen for environment and material page with the error saying its already triggered, but they aren't jvm 1 | 2021-02-23 08:19:16,650 INFO [qtp444758881-283553988] ManualBuild:61 - 'Failed to trigger pipeline: XYZ' because 'Pipeline already triggered' jvm 1 | 2021-02-23 08:25:45,664 INFO [qtp444758881-326911547] PipelineTriggerService:48 - [Pipeline Schedule] [Processed] Manual trigger of pipeline 'XYZ' processed with result 'com.thoughtworks.go.serverhealth.ServerHealthState@4749803c[healthStateLevel=OK,type=<HealthStateType ARTIFACTS_DISK_FULL LogScope[GLOBAL, scope=GLOBAL]>,message=,description=,expiryTime=<null>,timestamp=Tue Feb 23 08:25:45 GMT 2021]'
. What might cause this? Thanks in advance
Author identity unknown
* Please tell me who you are.
Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: empty ident name (for <@github.com>) not allowed
20.1.0
onwards which we are failing to upload config.xml via post request with 400 bad request.curl -s -XPOST ${GOCD_API_ENDPOINT}/go/admin/restful/configuration/file/POST/xml -H "Content-Type:application/x-www-form-urlencoded" --data-urlencode xmlFile@cruise-config.xml -H "Confirm: True" -u "$GO_SERVER_USER_NAME:$GO_SERVER_PASSWORD" -d md5=$config_xml_md5
gocd-agent-ubuntu
for 20.04 LTS?
Hi All,
with the recent change to GitHub’s authentication,
Basic authentication using a password to Git is deprecated and will soon no longer work.
https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/
how can we integrate this in GOCD build pipeline?
we are currently usign GOCD 16.1.0 version.
Thank you :)
[GIT] Cleaning all unversioned files in working copy
wrapper.conf
:
set.AGENT_STARTUP_ARGS=-Dtoggle.agent.git.clean.keep.ignored.files=Y
Hello, guys. We are using GoCD version 21.1.0 and when we checked the logs, we saw this error for each agent:
2021-04-22 07:41:43,409 WARN [qtp1740200769-58] AgentService:539 - Agent [Agent [ 0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99, null]] has no cookie set
2021-04-22 07:41:43,410 ERROR [qtp1740200769-58] BuildRepositoryRemoteImpl:59 - Error occurred in com.thoughtworks.go.server.service.AgentRuntimeInfo@767b3180[agentBootstrapperVersion=21.1.0-12439,agentVersion=21.1.0-0,buildingInfo=AgentBuildingInfo[, ],cookie=<null>,identifier=Agent [ 0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99],location=/var/lib/go-agent-3,operatingSystemName=CentOS Linux 7.9.2009 Core,runtimeStatus=Idle,usableSpace=21260271616] ping.
com.thoughtworks.go.server.service.AgentNoCookieSetException: Agent [Agent [0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99, null]] has no cookie set
This error appears only at restart, and in the end the cookie is assigned for each agent:
2021-04-22 07:41:44,788 INFO [qtp1740200769-211] BuildRepositoryRemoteImpl:127 - [Agent Cookie] Agent [Agent [0fdc505c-eda8-4d9c-a70b-f2cdf0dd7d99]] at location [/var/lib/go-agent-3] asked for a new cookie, assigned [33afe63e-2c18-41fa-97f5-8602e9f4c95a]
We have a lot of agents and logs are polluted with these errors. Do you have any idea how can I get rid of this error? Is any way to disable the log for com.thoughtworks.go.server.service.AgentRuntimeInfo/com.thoughtworks.go.server.service?