Is it always "kex_exchange_identification: Connection closed by remote
host" as the failure reason?
If so, it usually means the remote host is closing it before exchanging SSH
keys (maybe because of connection limits, or authentication problems), or
perhaps there is a firewall/network proxy or
Hi Chad,
Thank you for responding to my issue.
Just wanted to give some basic info on the GoCD version.
We are using GoCD 23.1.0 aarch version, all of our servers are Mac OS M1
servers(for both GoCD and agents)
- What are the specific clone errors you are getting?
*we get the below
GoCD doesn't do anything special with Git - it just uses whatever git
version you have available to the agent/server on the path. If something
has changed after the Sonoma upgrade, it is probably affecting all Git
usage on the machine.
- What are the specific clone errors you are getting?
-
Hi Team,
Recently, we upgraded all of our go-agents to macos Sonoma from ventura.
GoCD also runs on Sonoma version.
After the upgrade, we are seeing intermittent git clone failures in the
pipelines.
Each pipeline has 3 or more repos to clone, when multiple pipelines around
20 pipelines try to
