It's hard to say, but it looks like either due to CPU or network saturation, the GoCD server did not respond in time, to the agent. Some instances I've seen this happen:
Uploading a huge artifact saturates the network (on the GoCD server side) and it can't service any agents.
Usually "Start to prepare" means it is about to check out materials. If your SCM repository is also on the GoCD server (and maybe lots of agents are using that repo), the git checkouts could be causing a CPU or n/w spike, meaning the GoCD server is unable to respond.
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