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.
@anoop-l This also provides the various directories that are used: https://github.com/gocd/docker-gocd-server#under-the-hood
Unable to create database upgrade script for database. The problem was: Could not acquire change log lock
Getting error - Failed to find 'git' on your PATH. Please ensure 'git' is executable by the Go Server and on the Go Agents where this material will be used.
@arvindsv It was indeed some browser plugins in firefox that caused errors when trying to Save any configuration change: "The change you wanted was rejected", ""precondition failed" and even something that read similar to "someone (else) changed the configuration, please try again" (I don't have the exact wording at hand). And in the logs there was the "InvalidAuthenticityToken" note.
All of this went away with a clean browser.
Super quick help and resolution. Once again go.cd shows it has the BEST support and community! Thank you for all that you do!! @arvindsv (and other great people who have answered questions over the years of using Go.CD)
@Jatin0597 It means what it says. The GoCD server (in this case, since "Test connection" happens on the server) is unable to find git in PATH. Usually this happens if the user the GoCD server is running as is different from your usual user. You might think you've added this to PATH locally, but the GoCD server user doesn't have it in PATH. I've seen this happen often on Windows, where GoCD runs as a service, as some kind of a system user. I've used Procexp from Microsoft Sysinternals to find the PATH to verify this. I'd look to set the PATH in the server's wrapper-properties.conf file to see if it helps.
Hi, we are running with GoCD version
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
1 reply
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
Hello - I need to record a demo of some pipelines we use for container deployments. We have quite a big environment - is there any way to suppress the errors at the top right of the page? I can't clean up the errors as I'm not the pipeline owner - doesn't make for the best impression! GoCD 21.1.0
1 reply
can I talk with gocd support
Hi team,
We recently upgraded GoCD to to
We are using the following command
Is there config.xml file size limit on post request?
or do you sugest any other way? Any help would be much appreciated as we are blocked on this.
We recently upgraded GoCD to to
20.1.0 onwards which we are failing to upload config.xml via post request with 400 bad request.We are using the following command
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_md5Is there config.xml file size limit on post request?
or do you sugest any other way? Any help would be much appreciated as we are blocked on this.
I would check whether the underlying material polling is delayed. Once you click trigger, it tries to get the latest commits. While it is doing that, if you refresh the browser and trigger again, it'll show you that message. Till it finishes that and starts building, it won't mark the pipeline as "in progress" and so, you will be able to trigger it again.
1 reply
Hi, we are using GoCD as our ci/cd tool on Kubernetes with elastic agents. Due to the deprecation of docker as underlying runtime (https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/) we are evaluating some alternatives as Kaniko or Podman/Buildah to build our docker containers in our pipelines. The main option at the moment is Podman/Buildah as we think we can install it on a GoCD agent and keep most of the pipeline configuration we already have, but we found some issues... the main question here is ¿Are you planning to release a version for
gocd-agent-ubuntu for 20.04 LTS?
1 reply
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 :)
2 replies
Hi! I'm trying to test GoCD, but I can'the find the app shortcut icon after install it on Windows. Does somebody have and suggestion? Thank you!
2 replies
@arvindsv: I've tried that without luck. I gonna reinstall Java. Let's see what happens.
is it possible to tell GoCD to leave my node_modules directory intact on Fetch materials ?
when it does a fetch, I see
[GIT] Cleaning all unversioned files in working copy
I don't want it doing this
1 reply
added this to the end of my Go agent's
wrapper.conf:
set.AGENT_STARTUP_ARGS=-Dtoggle.agent.git.clean.keep.ignored.files=Y
Good morning! Yesterday, my team and I came across the announcement that GoCD would be community-driven as of 2021. We noticed the steering committee but haven't seen any updates as of August 2020. Is there any documentation or roadmap we are missing? We are wondering if the steering committee is taking over ownership or if there is any information around that. Thanks!
2 replies
