Hi
I would like to devise a way to generate a historical test report of common test failures from our test stage in a pipeline. This would be for trend analysis to help us spot and resolve either flakey tests or inconsistent failures which may be genuine but difficult to spot. I have not seen any features on GoCD documentation that lends itself as a solution to this - would anyone on this thread know of any possible solutions to this problem other than building a process from scratch (which may be my option otherwise!) :)
Thanks
I would like to devise a way to generate a historical test report of common test failures from our test stage in a pipeline. This would be for trend analysis to help us spot and resolve either flakey tests or inconsistent failures which may be genuine but difficult to spot. I have not seen any features on GoCD documentation that lends itself as a solution to this - would anyone on this thread know of any possible solutions to this problem other than building a process from scratch (which may be my option otherwise!) :)
Thanks
2 replies
hi, We have been using GoCD for a long time (@Myriad Genetics/Counsyl). We are on version 20.10.0. A couple of days ago it started responding sluggishly on the UI and the pipelines are also taking a long time. We are using a 8cpu AWS instance for the server and have around 100 agents. We do not see any resource issue except that sometimes cpu is very high and the load is higher than normal but still much lower than 1/core.
8 replies
i am trying to do the 20.4 -> 20.5 database migration from h2 to postgres and it is throwing exceptions, a lot of invalid format, and later UI warnings that it can't insert because of constraint violations. the modifications table is not getting copied completely during the migration is what i am guessing the cause is.
what should i do to cancel the building process of an agent?
@mdkadar ☝🏼
@fabriciocduarte the cadence isn’t monthly anymore — GoCD releases are cut as-needed (security fixes, new features, etc).
That sounds sensible - ultimately it’s just about following the same conceptual steps, which I think you’ve done:
- Bring DB up to date with 20.4.0 & back up DB
- Run migrator tool on the H2 file to generate a new H2 file in the new format
- Replace H2 DB (
cruise.h2.db) with the newly generated one in the prior step (cruise.mv.db— note the name change) - Upgrade to newer GoCD (anything after 20.5.0) and verify everything works
We're trying to upgrade GoCD Agent from 19.5 to 20.1 (or any higher version) on ARM64 (a HIL rig running Ubuntu18) and during installation it complains about not being able to find wrapper binaries for arm64. Are they not bundled any more?
Adding them manually makes us run into another issue: Cannot resolve JAVA version.
Our regular Ubuntu agents that are not arm64 have been upgraded successfully without issues.
Any ideas?
Adding them manually makes us run into another issue: Cannot resolve JAVA version.
Our regular Ubuntu agents that are not arm64 have been upgraded successfully without issues.
Any ideas?
2 replies
@cdahlhausen There is no plugin. Here's the guide: https://docs.gocd.org/current/installation/configuring_database/postgres.html I dropped in a postgresql JDBC driver, but I think that was unnecessary.
Hi there ... I wanna give gocd a try, but currently I can't manage to get version 21.2.0 docker to see the agent. I am using this 2 docker images: gocd/gocd-server:v21.2.0 and gocd/gocd-agent-debian-10:v21.2.0 on my local environment. I have started the agent docker image like this:
docker run -itd --name gocd-agent -e CI=true -e GO_SERVER_URL=https://$(docker inspect --format='{{(index (index .NetworkSettings.IPAddress))}}' gocd-server):8153/go gocd/gocd-agent-debian-10:v21.2.0but unfortunately I can't see the agent in the agent view in the gocd ui. Is there a special way to run the agent docker image in order to see it in the gocd ui?
Hi all,
I'm trying to setup an auto registration remote agent on aws but I'm stuck due to the following error:
My current configuration:
- [go-server] /etc/gocruise-config.xml:
<?xml version="1.0" encoding="utf-8"?> <cruise xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="cruise-config.xsd" schemaVersion="139"> <server agentAutoRegisterKey="195ea125-5d3a-4d33-8cc7-5c0e482cc0e7" webhookSecret="..." serverId="..." tokenGenerationKey="..."> <security> - [go-agent] /var/lib/go-agent/config/autoregister.properties
agent.auto.register.key=195ea125-5d3a-4d33-8cc7-5c0e482cc0e7 agent.auto.register.hostname=agent-01 agent.auto.register.elasticAgent.agentId=7f5e55d20407 agent.auto.register.elasticAgent.pluginId=com.example.aws
With these settings I'm getting the following error:
go-server (/var/log/go-server/go-server.log):
2021-07-21 06:44:21,034 ERROR [qtp993070390-40] AgentRegistrationController:242 - Rejecting request for registration. Error: HttpCode=[422] Message=[Elastic agent registration requires an auto-register agent key to be setup on the server. The agentAutoRegisterKey: [195ea125-5d3a-4d33-8cc7-5c0e482cc0e7] is either not provided or expired. Agent-id: [7f5e55d20407], Plugin-id: [com.example.aws]] UUID=[bbbfd276-ce32-430f-81f5-69dbc3cea571] Hostname=[4255f57b7ca5]ElasticAgentID=[7f5e55d20407] PluginID=[com.example.aws]go-agent (/var/log/go-agent/go-agent.log):
2021-07-21 06:44:16,390 ERROR [scheduler-2] RemotingClient:166 - Server responded to action `ping` with: status[403 Forbidden], body[] 2021-07-21 06:44:16,393 ERROR [scheduler-2] AgentHTTPClientController:114 - Error occurred when agent tried to ping server: java.lang.RuntimeException: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include: - This agent has been deleted from the configuration - This agent is pending approval - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details. at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:118) at com.thoughtworks.go.agent.RemotingClient.ping(RemotingClient.java:74) at com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:109) ... at java.base/java.lang.Thread.run(Unknown Source) Caused by: org.apache.http.client.ClientProtocolException: The server returned status code 403. Possible reasons include: - This agent has been deleted from the configuration - This agent is pending approval - There is possibly a reverse proxy (or load balancer) that has been misconfigured. See https://docs.gocd.org/21.2.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies for details. at com.thoughtworks.go.agent.RemotingClient.validateResponse(RemotingClient.java:141) at com.thoughtworks.go.agent.RemotingClient.post(RemotingClient.java:114) ... 14 common frames omitted 2021-07-21 06:44:21,043 ERROR [scheduler-1] SslInfrastructureService:173 - Error occurred during agent registration process: Elastic agent registration requires an auto-register agent key to be setup on the server. The agentAutoRegisterKey: [195ea125-5d3a-4d33-8cc7-5c0e482cc0e7] is either not provided or expired. Agent-id: [7f5e55d20407], Plugin-id: [com.example.aws]
Could anyone help me with this issue?
Thanks!
Hi all,
We've been working on setting up multiple agents for pipeline.For allocating jobs to agents as far as the documentation we've gone through.we needt to manually assign the resource to the agents.Is there any way to random assign agents to jobs without doing manually.
1 reply
Is there a way to have some form of file per github project that will give gocd instruction on how to run? Would that be https://docs.gocd.org/current/advanced_usage/pipelines_as_code.html and does it work per repo?
Good day! I might have posted this before, but I did not see an answer: I am trying to run gocd in an IPv6 only kubernetes cluster. However the gocd never starts, but errors out with:
Warning FailedPostStartHook 4m22s kubelet Exec lifecycle hook ([/bin/bash /preconfigure_server.sh]) for Container "gocd-server" in Pod "gocd-server-5b8fb6b58f-54qc8_default(799b2a6e-aa1c-4292-b091-4b500a0ab857)" failed - error: command '/bin/bash /preconfigure_server.sh' exited with 137: % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (7) Failed to connect to localhost port 8153: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed(lots of repetitions)
Does anyone know what is going on or whether it's somewhat possible to get gocd running in k8s/ipv6?
Heya! I'm trying to get the current version of go-server running on nixos, with the possible goal of contriubting changes back to the nixos packages. While updating the package for the go-agent was relatively straightforward, the go-server gives me a big long and scary exception that I do not know what to make of. Here is a log of it: https://gist.github.com/skeleten/8cbe11f1a620af4e702abebd62b63c95 I'd really appreciate any points as to whats going wrong here :)
3 replies
Mhm, that would be a problem, considering that the whole reason to update the package was that it was no longer compatible with the shipped jdk version. Thinking of it, the earlier versions gave a much more clear error message about what was going wrong, weird to see that being no longer the case. Thanks for your hint, i'll try to modify the package to use an earlier version (lts maybe) of java, i'll ask again if the problem persist ^-^
Hm, actually this goes against the documentation that says it just needs a version > 13 =/
Hello, does anyone have experience with the gocd api. I'm attempting to make a curl request to update EnvironmentVariables for a single pipeline, but the request isnt working.
For Materials
Usually you login with those via https, just use the https url and your username, set the access code as password
@skele10 Correct, however on August 13th GitHub changed what is allowed for logging in and I receive this message now for Materials:
STDERR: remote: Support for password authentication was removed on August 13, 2021. Please use a personal access token instead.
STDERR: remote: Please see https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ for more information.
STDERR: fatal: unable to access 'https://github.com/my-repo': The requested URL returned error: 403
Hello, I try to build test and pack and angular application in 3 separate stages, but it seems that the between each stage the 'node-modules' folder that contains dependent packages is deleted by 'git clean' and I need to add a task to build again on the next stages. Is it possible to keep working directory uncleaned between stages?
@ConFliX: Weird, it seems to work on my instance. Are you positive you've set an personal access token as password? (created on https://github.com/settings/tokens)? Username should be your github username. You also need to set the repo permissions on the token, so it can be used to read the repository
Hey Folks, is there a way to install multiple agents on windows? I tried silent setup but the installer detects existing agent and exists...
Install using Generic zip is the answer :) : https://docs.gocd.org/current/installation/install/agent/zip.html
We are exploring GoCD for our CI/CD pipeline. Currently we are using Bitbucket Pipelines.
I tried locally and have few questions regarding how-to,
I tried locally and have few questions regarding how-to,
- Can we configure a pipeline without git dependency / material? We have a pipeline which runs on a schedule and the pipeline is just pure shell script (and it does not depend on any code from any repo).
- How to configure multi-branch pipeline? For example, we have an frontend repo with different branch for different environment, like dev, prod, … so that when triggering the pipeline manually, we can select which branch to trigger from.
- Here is a complex scenarios which we trying to resolve. We have 2 repo, 1 for frontend and 2 for backend. The backend pipeline will be dependent on frontend pipeline. Whenever the frontend pipeline build is successful, it should trigger backend pipeline. Also if there is any change in backend repo, it should trigger backend pipeline. I’m able to configure this by adding multiple dependencies for backend pipeline. The complexity here is, we generated random key when building frontend (For eg.: KEY=hash-BUILD-1), and the same needs to be passed to backend pipeline.
a. How to trigger backend pipeline with custom build parameter (KEY)? From pipeline 1 it should pass parameter and value for pipeline 2 build.
b. How to persist param value (KEY) in backend pipeline, so that subsequent build from backend repo (commits, poll scm) trigger will use the param value (KEY) which is already set. Param value changes only when frontend pipeline creates a new build.
@vigneshraaj For #2, please look at this stackoverflow response: https://stackoverflow.com/a/56811461
For #1: No, you need to have a material. But, it can be a dummy material, with polling turned off. So, it'll only trigger on timer.
For #3: The way to pass information between pipeline instances in usually via artifacts. You'd publish an artifact (can be any file) in the frontend pipeline with that key / param. You can then fetch that artifact from the upstream (frontend) pipeline in the downstream pipeline (backend) and use it. If you ever re-run the backend pipeline instance, it'll get that artifact again and use it. That same version of the artifact. You can verify the versions in the VSM.
Thanks @arvindsv for clarifying. One more question,
- As part of UAT or Production build, we do git tag and push it through build pipeline script. Is there a way to ignore such commits? Usually we add like
[skip]in git commit message and CI/CD pipeline will ignore it. Anything similar in GoCD?
cp: can't create '/go-working-dir/config/logback-include.xml': Permission denied
Hello team, I need two jobs which are in different stages need to be run in the same go-agent. I am unable to understand where can we configure this. Can someone help me with this?
1 reply