Re: [go-cd] Performance of popups in the gui

On Mon, May 13, 2024 at 4:10 PM 'Wolfgang Achinger' via go-cd < go-cd@googlegroups.com> wrote: > Dude the fix is amazing ! > > Am Mo., 13. Mai 2024 um 04:05 Uhr schrieb Chad Wilson < > ch...@thoughtworks.com>: > >> Apologies for the slow release of

Re: [go-cd] Performance of popups in the gui

t; > Am Sa., 17. Feb. 2024 um 18:08 Uhr schrieb Chad Wilson < > ch...@thoughtworks.com>: > >> Hiya folks >> >> I've been able to replicate this problem and should be able to fix it for >> a subsequent release - thanks for the help debugging. >> &

[go-cd] Release Announcement - 24.1.0

Hello everyone, A new release of GoCD (24.1.0) is out. This release is a relatively minor maintenance release, however does make some potentially breaking changes to reduce maintenance overhead. - Links are no longer forced opened in new tabs - Java

Re: [go-cd] GOCD restart issue

> - ./gocd/passwd:/godata/config/passwd > - > ./gocd/docker-elastic-agents-3.2.3-415.jar:/go-working-dir/plugins/external > networks: > - gocd > > > > On Tuesday, May 7, 2024 at 9:05:30 PM UTC+5:30 Chad Wilson wrote: > >> Please share how you a

Re: [go-cd] Mount .ssh from EFS to the container (from the image gocd/gocd-server:v22.3.0)

To add onto the many options here, if you only need the SSH keys to be used by Git for clones etc, you can entirely customise how GIT uses SSH using the *GIT_SSH_COMMAND* env var ; set at the container level.

Re: [go-cd] pipeline as code - stuck on waiting for agent

Perhaps you can share the agent(s) you are expecting it to run on, and the job configuration of the jobs that aren't scheduling? If the job isn't being assigned, it means there is no free agent[1] in the desired pipeline-scope environment[2] that offers the requested job-scope resources [3]. All

Re: [go-cd] Elastic agents plugin usage

It seems you are using the third party EC2 Elastic Agent Plugin . This plugin does not implement the plugin API correctly and does not support environments correctly,

Re: [go-cd] Elastic agents plugin usage

Can you be specific about the type of elastic agents you are creating and the plugin you are using. Kubernetes? Docker? Something else? There are many elastic agent plugins. > Here's where it gets tricky: when the staging job completes and triggers > the production job, I expect one of the

Re: [go-cd] GOCD server Db issue

You may have killed GoCD while it was starting up? If you are sure that you do not have multiple processes accessing the same database at the same time and it is still stuck, you will have to try manually clearing the lock

Re: [go-cd] Query re: Gitlab build status notifier

Hi Steve I'm not familiar with use of either of these plugins with GitLab, however it seems pretty clear that the gocd-build-status-notifier plugin does not have gitlab support merged so the two plugins don't work together right now. It seemed to be blocked by this comment here

Re: [go-cd] Help Needed with GoCD Docker Setup and cruise-config.xml Configuration

ner:67 - Plugin load starting: >> /go-working-dir/plugins/external/gocd-ec2-elastic-agent-plugin-2.2.2.jar >> 2024-04-11 08:11:02,693 INFO [Thread-79] GoConfigDao:108 - Config update >> request by anonymous is in queue - >> com.thoughtworks.go.config.update.ReplaceElasticAge

Re: [go-cd] Help Needed with GoCD Docker Setup and cruise-config.xml Configuration

Hi Satya When running a standard GoCD docker server image, you should mount a writable volume to the entire */godata* directory which includes the config as noted at https://hub.docker.com/r/gocd/gocd-server, but not directly to an individual config file. If you do not, even if you get the

Re: [go-cd] SCM VALIDATE FAILED

s/external/github-pr-poller-1.4.0-RC4.jar", > "bundled_plugin" : false, > "about" : { > "name" : "Github Pull Requests Builder", > "version" : "1.4.0-RC4", > "target_go_version" : "15.1.0", > "

Re: [go-cd] SCM VALIDATE FAILED

clarification about it how to config those > > On Tuesday, March 19, 2024 at 11:38:13 AM UTC+5:30 Chad Wilson wrote: > >> Version 1.4.0 of the plugin has never been officially released, so I am >> not sure if that is stable, but I do not get those errors with that version >> ei

Re: [go-cd] SCM VALIDATE FAILED

nched the config > gocd which is have own url in it for security purpose. It display like > this, whoever visit this url and use this scm plugin it display the error. > i need to resolve it > > > On Tuesday, March 19, 2024 at 11:13:05 AM UTC+5:30 Chad Wilson wrote: > >> I ca

Re: [go-cd] SCM VALIDATE FAILED

arification > > [image: image.png] > > > > On Monday, March 18, 2024 at 3:36:18 PM UTC+5:30 Chad Wilson wrote: > >> It may help if you share screenshots of exactly what you are doing and >> entering in the fields, as it's a bit difficult to understand what you are >> seein

Re: [go-cd] SCM VALIDATE FAILED

It may help if you share screenshots of exactly what you are doing and entering in the fields, as it's a bit difficult to understand what you are seeing? Can you also share the versions of your GoCD server and plugins, plus which browser you are using? On Mon, Mar 18, 2024 at 5:51 PM Suthar

Re: [go-cd] git clone failures in gocd pipelines after sonoma upgrade

o when there are >failures? > > *The failures are happening on the agents. the agent path is > /Users//go-agent-23.1.0/* > *We installed GoCD in /Applications/.* > > *The artifacts path is /Volumes/Artifacts.* > Please let me know if you need more information. > Tha

Re: [go-cd] git clone failures in gocd pipelines after sonoma upgrade

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? -

Re: [go-cd] Is it possible for multiple GoCD servers to use the same database?

Unfortunately moving to an active-active state would be a huge architectural change for GoCD, and unfortunately not consistent with its original design - let alone its current maintainer/community state (alive, but not thriving). Previously,

Re: [go-cd] Is it possible for multiple GoCD servers to use the same database?

Unfortunately not if they are both running at the same time; no. GoCD does not support active-active configurations like that. If they otherwise share DB and storage and have the same identity, but one deployment is scaled to 0 and the other scaled to 1 replica, that is theoretically possible -

Re: [go-cd] Wehbook notification plugin

> (and so it means that the "Slack notification plugin" can also be tagged > as "Mattermost notification plugin :) ) > > > Le lundi 19 février 2024 à 17:21:48 UTC+1, Chad Wilson a écrit : > >> That's not necessarily true. All the error tells us is that the plugin >> cou

Re: [go-cd] Wehbook notification plugin

ks.go.server.service.PluginService.updatePluginSettings(PluginService.java:118) > >at > com.thoughtworks.go.apiv1.pluginsettings.PluginSettingsControllerV1.update(PluginSettingsControllerV1.java:115) > >at spark.RouteImpl$1.handle(RouteImpl.java:72) > > I suspect this error confir

Re: [go-cd] Wehbook notification plugin

> net.getsentry.gocd.webhooknotifier.WebhookNotifierPlugin.handle(WebhookNotifierPlugin.java:53) > >... 161 common frames omitted > > > The webhook is in place, and has been tested independantly (and is working) > > Thanks for your help, > > > > > Le lu

Re: [go-cd] Wehbook notification plugin

Does that plugin really not work? I note the repo has recently been archived, but the plugin was updated relatively recently in 2023 and there haven't been any changes in those plugin APIs for quite a while to my knowledge - nor removal of old versions of the (plugin API) extension points. In

Re: [go-cd] Performance of popups in the gui

the additional information out, but not directly, they come from a > different mail address over a secure transfer method. > > Am Do., 15. Feb. 2024 um 17:57 Uhr schrieb Chad Wilson < > ch...@thoughtworks.com>: > >> Cool, thanks! Just trying to gather enough informa

Re: [go-cd] Performance of popups in the gui

> time of the popups). > > If it is ok i will send the support output directly your our mailadress > so it will not get shared in the thread. > > Am Do., 15. Feb. 2024 um 15:50 Uhr schrieb Chad Wilson < > ch...@thoughtworks.com>: > >> And how many resources are

Re: [go-cd] Performance of popups in the gui

164 materials > 0 elastic agents > 2 config repos > 0 artifact stores > 0 pluggable scms > > Am Do., 15. Feb. 2024 um 15:01 Uhr schrieb Chad Wilson < > ch...@thoughtworks.com>: > >> How many distinct environments and resources do you have across these >>

Re: [go-cd] Performance of popups in the gui

How many distinct environments and resources do you have across these 1200 pipelines, roughly? On Thu, Feb 15, 2024 at 5:38 PM 'Wolfgang Achinger' via go-cd < go-cd@googlegroups.com> wrote: > Additional information > Since the pipelines are configured via ~150 yaml files. > I tested it now with

Re: [go-cd] Performance of popups in the gui

Hi Hans Is this slowness specific to builds that are currently running? Or is the slowness (and speed up with deleted agents) the same even with builds/stages that are no longer running (even if the agents are)? Anything majorly different about this GoCD server setup compared to the others, e.g

Re: [go-cd] API on pipeline instance returns 404

Hiya David Did you look at https://api.gocd.org/19.1.0/#get-pipeline-instance ? You need *GET /go/api/pipelines/:pipeline_name/instance/:pipeline_counter *to get an instance of a pipeline run - that should work? -Chad On Mon, Feb 12, 2024 at 8:46 PM David DOS SANTOS wrote: > Hello, > > I'm

Re: [go-cd] question on pipeline and view ordering

1) Pipelines on dashboard should be ordered for display by - pipeline group | environment, in order that you see it in the config file (may be different for pipelines-as-code implied groups|envs) - then by pipeline as implied by - order it is in config file - pipelines-as-code:

Re: [go-cd] Are optional artifacts possible ?

It's a reasonable question. Possible different way of thinking about this: When you have varying numbers of artifacts that are related to one another, put them in a directory together and artifact the whole directory as a single artifact (on the upload side). That way it is not dependent on any

Re: [go-cd] Mac agent unable to connect to server

There's no error shown in that log file, which just means that the bootstrapper/launcher is starting OK - but doesn't tell us much else. You need to look at the other agent logs to see why it is failing to register with the server. Look in the logs directory for the others (for most problems you

Re: [go-cd] Is possible to run task parallel

Indeed, you need the ability to have multiple agents running in parallel to be able to do multiple jobs in parallel. The best way to achieve this depends on 1) your installation/deployment choice 2) your agent requirements 3) whether you are experimenting or thinking about a production deployment.

[go-cd] Release Announcement - 23.5.0

Hello everyone, A new release of GoCD (23.5.0) is out. This release is another relatively minor maintenance release, fixing a minor UX regression from 23.4.0 when interacting with job console logs alongside a few other older issues. As always, please

Re: [go-cd] Repo Sync issues

Yeah, sorry, that artifact was probably unintentionally included in the metadata. It'll be fixed in the next release when the metadata is corrected. I'm not familiar with Foreman, but is it possible to filter out this artifact (NessusAgent) with a content view or similar? -Chad On Wed, Dec 6,

Re: [go-cd] Re: GOCD Email server configuration

Do you have the SMTPS setting enabled? IIRC needs to be enabled for port 465 on Gmail but something might have changed. And which GoCD version (if you have tried both and they don't work on port 465) On Thu, 23 Nov 2023, 14:40 Vijayakumaran A., < vijayakumara...@praniontech.com> wrote: > HI

Re: [go-cd] LDAP Group Authentication/Roles/Permissions

up Authentication/Roles/Permissions > > > > Thanks! I’ll take a look. We are using the bundled version. > > > > *From:* go-cd@googlegroups.com *On Behalf Of *Chad > Wilson > *Sent:* Wednesday, November 8, 2023 1:09 PM > *To:* go-cd@googlegroups.com > *Subject:* Re

Re: [go-cd] Ruby on Rails-Server-Version end-of-life

Hiya Erik Plans, yes: https://github.com/gocd/gocd/pull/12077 - but it's not EOL *quite* yet :P. Arguably there are riskier pieces of EOL software within GoCD than Rails right now (Spring Security, Spring Framework) and if things get messy I'm more inclined to focus on pieces with better

Re: [go-cd] Material branch check exclusion?

ing 3. This property must be the same over all pipelines which use the same > material. You cannot have one pipeline which pulls and one which receives > a push for the same material. > On Friday, November 17, 2023 at 2:54:32 AM UTC Chad Wilson wrote: > >> In theory if you ha

Re: [go-cd] GOCD Version Upgrade Issue - Windows Agents Failing to Execute 'git pull'

> >pipeline="" stage="Build" job="defaultJob"> > > > > > > > > > > > > > > [image: image.png] > On Friday, November 10, 2023 at 12:15:03 AM UTC-6 Chad Wilson wrote: > >&

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

/gocd-contrib/docker-elastic-agents-plugin/releases/download/v3.2.3-399/docker-elastic-agents-3.2.3-399.jar > \ > --name gocd-server \ > gocd/gocd-server:v22.3.0``` > > Sorry about cruise-config.xml, looks like I have sent the old config. > > Best > Satya > > > On

Re: [go-cd] Agent docker image

The default go-server docker image is Alpine based, so the equivalent image would be https://hub.docker.com/r/gocd/gocd-agent-alpine-3.18 Having said this, most folks find they end up building their own agent image using a GoCD official image as base image, so they can add on required tooling of

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

he code snippet), but doesn't seem to > be working as those profiles doesn't appear on the Admin->Elastic Agents > Configurations tab, but its asking for a fresh configuration, wonder what > am I missing? Also, is it still a valid way of configuration ? > > Regards > Satya > &g

Re: [go-cd] Docker Elastic agent plugin .jar location (to run it in the ECS)

There's no such release. You should use a non-experimental release from https://github.com/gocd-contrib/docker-elastic-agents-plugin/releases and find the link to the main jar file within that release. There should be no reason you cannot use the most recent release

Re: [go-cd] GOCD Version Upgrade Issue - Windows Agents Failing to Execute 'git pull'

It's possibly a side effect of fixing issues with spaces in windows commands in GoCD 22.2.0: https://www.gocd.org/releases.html#22-2-0 It may be that some of your command tasks were *technically* incorrectly configured on earlier versions but worked as a side effect of these bugs in GoCD, and

Re: [go-cd] LDAP Group Authentication/Roles/Permissions

There are multiple LDAP plugins, so it depends which one you are referring to. Sounds like you might want to look at https://github.com/gocd/gocd-ldap-authorization-plugin rather than the bundled 'authentication-only' version? -Chad On Thu, 9 Nov 2023, 05:33 Funkycybermonk, wrote: > Hello! >

Re: [go-cd] Where can I find the end-of-support documentation for GoCD releases?

Other than Ram's (accurate) comments about non-use of semantic versioning, please see https://github.com/gocd/gocd/blob/master/SECURITY.md Upgrading from 22.3.0 through to 23.3.0 or 23.4.0 is likely to be very low risk/impact given the slow rate of change in GoCD over the last year. -Chad On

[go-cd] Release Announcement - 23.4.0

Hello everyone, A new release of GoCD (23.4.0) is out. This release is mainly a maintenance release. As always, please remember to take a backup before upgrading. Special thanks to Victor Sollerhed (MPV) and k-c-p for helping us debug a (likely) rather

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

24 moves to >> containerd runtime images and we are still using DIND for our elastic >> agents. That seems like it could be the culprit. I'll do some testing and >> change our elastic agent images. Thanks for pointing that out. >> >> On Thu, Oct 26, 2023 at 10:46

Re: [go-cd] goCD Yaml plugin doesn't pick-up code

As the error mentions please "Check the 'Rules' of this config repository" - by default your config repo won't have rules/permissions to define pipelines in any pipeline groups, environments etc. It is "secure by default". You'll want to add a permission to do so. e.g a blanket permission to

Re: [go-cd] GoCD and private GitHub repo

oing wrong? May that be I have messed with permissions for *go > user*? > > > Vlad. > > On Thursday, October 26, 2023 at 8:41:33 PM UTC+13 Chad Wilson wrote: > >> To add on to Sriram's comments, the use of the >> github-oauth-authorization-plugin doesn't have any relat

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

on the kubernetes side, or does it never get that far? -Chad On Thu, Oct 26, 2023 at 11:37 PM Chad Wilson wrote: > Just curious - were the errors/stack traces on failure essentially > identical before and after you upgraded your gocd and elastic agent plugin > versions? > > On Th

Re: [go-cd] Kubernetes Elastic Agents - Pods can no longer be created

Just curious - were the errors/stack traces on failure essentially identical before and after you upgraded your gocd and elastic agent plugin versions? On Thu, Oct 26, 2023 at 11:33 PM Kim Pham wrote: > Hi Ashwanth, > > I checked the clusterrole of the service account it's using and it >

Re: [go-cd] GoCD and private GitHub repo

To add on to Sriram's comments, the use of the github-oauth-authorization-plugin doesn't have any relationship with access to repository content on GitHub - it simply allows people to log onto GoCD using their Github identity, and optionally to have access to GoCD pipeline groups mapped to GitHub

Re: [go-cd] POC setting up

Hiya Gowtham It looks like you downloaded and are trying to run the *x64 version* on an *Apple Silicon* mac which will likely give errors like that. You probably want the *aarch64* version from https://www.gocd.org/download/#osx As a side note, the easiest way to POC GoCD locally is probably via

Re: [go-cd] Seeking clarification with GoCD Release Notes

ded > clarification for internal skeptics like me. > > On Thursday, October 5, 2023 at 12:48:23 PM UTC-4 Chad Wilson wrote: > >> Yeah, that's correct. >> >> Any particular question you're trying to answer? >> >> -Chad >> >> On Fri, 6 Oct 2023, 00:3

Re: [go-cd] Seeking clarification with GoCD Release Notes

Yeah, that's correct. Any particular question you're trying to answer? -Chad On Fri, 6 Oct 2023, 00:36 Cory McKelvey, wrote: > Does https://www.gocd.org/releases/ act as release notes for both > gocd-server and gocd-agents? > > -- > You received this message because you are subscribed to the

Re: [go-cd] Enterprise Support for GoCD

wtham Ravipati > > On Saturday, September 30, 2023 at 3:38:58 AM UTC-6 Chad Wilson wrote: > >> Hi Gowtham - To my knowledge there has been no change in this situation. >> >> -Chad >> >> On Wed, 27 Sept 2023, 23:50 Gowtham Ravipati, >> wrote:

Re: [go-cd] Enterprise Support for GoCD

Thanks for the detail. >> >> >> Please write to me : sriramNRN at gmail >> >> >>> >>> On Monday, June 27, 2022 at 4:05:23 PM UTC+5:30 Chad Wilson wrote: >>> >>>> Hi there >>>> >>>> Thoughtworks no longer prov

Re: [go-cd] Unable to run Microsoft Upgrade assistant

Which GoCD version are you using? Can you share a screenshot from your task configuration? e.g something like the below [image: image.png] Generally speaking you shouldn't need to do a "cmd /c" yourself, as GoCD does this implicitly and it's possible doing this might be causing something to go

Re: [go-cd] GoCD Agent in Arch Linux container - Can't start any job

Hi Jacques - that looks like a bug of some kind with the way the work for the agent to do is being serialized by the server back to the agent. Have never seen that before though. Could you report at https://github.com/gocd/gocd/issues along with the relevant versions of your server, agents, Java

Re: [go-cd] GoCD Pipeline Views - Can they be copied across users?

Yeah, they are in the DB keyed to the user's id: https://github.com/gocd/gocd/blob/0f58107c851cf2df6ce7c6902eebde796dc1f742/db-support/db-migration/src/main/resources/db-migration-scripts/initial/create-schema.xml#L291-L303 While it comes with some risks, it probably wouldn't be super difficult

Re: [go-cd] Config Repositories has always in fetch status

the current GoCD server (v22.1.0). > > So they are the same configuration but there are difference only GoCD > version and new GOCD server use only git over https. > > Best Regards, > Komgrit > > On Tuesday, August 8, 2023 at 11:23:25 PM UTC+7 Chad Wilson wrote: > &g

Re: [go-cd] Config Repositories has always in fetch status

ernal 74m 3% > 2570Mi 81% > > > Best Regards, > Komgrit > > On Tuesday, August 8, 2023 at 4:11:18 PM UTC+7 Chad Wilson wrote: > >> If you are getting logs like that, it sounds like the container is >> experiencing CPU starvation. >> >>

Re: [go-cd] Log in Issues

t; "competing" with your manual edits. >> >> On Tue, Aug 8, 2023 at 10:40 AM Chad Wilson >> wrote: >> >>> I can't recall exactly how it works, but perhaps if the config file is >>> *completely >>> removed* like you say you did below

Re: [go-cd] Config Repositories has always in fetch status

time but it is not help. > > And I dig to see timeout logs. There is log messages. > INFO | wrapper | 2023/08/08 07:43:48 | Wrapper Process has not > received any CPU time for 22 seconds. Extending timeouts. > > Best Regards, > Komgrit > On Tuesday, August 8, 2023

Re: [go-cd] Log in Issues

't running or "competing" with your manual edits. On Tue, Aug 8, 2023 at 10:40 AM Chad Wilson wrote: > I can't recall exactly how it works, but perhaps if the config file is > *completely > removed* like you say you did below, GoCD does some magic to restore the > latest known version f

Re: [go-cd] Log in Issues

I can't recall exactly how it works, but perhaps if the config file is *completely removed* like you say you did below, GoCD does some magic to restore the latest known version from the history git repo (that I referred to below) rather than starting from scratch. The most reliable way is to look

Re: [go-cd] Log in Issues

The server configuration that controls this is plain XML, and has source controlled history using git itself so you can use standard git tools (git log, git show etc) to find the config revision as it was before your change and revert the security/login settings back to what they were before.

Re: [go-cd] Multi gocd server

Hiya - no it's not. GoCD *previously* had the ability to run a warm standby ("business continuity") instance against a replicated database, however the failover was also manually triggered between the two. That functionality was removed due to a major security issue being discovered, and lack of

Re: [go-cd] Rollback deployment method

It depends on the tooling you are using and what environment/stack you are deploying to, alongside artifact storage relevant to your deployments. Not all deployments can be rolled back without extra effort in tooling or application design (e.g how will you roll back a DROP TABLE for a database?

Re: [go-cd] Gocd refresh

Are you using Pipelines as Code via YAML Config Repositories - and this is what you are talking about? Assuming so, unless you've turned off auto updating for the underlying repository, by default they should update within a minute. Admins can review the configuration at Admin > Config

Re: [go-cd] Regarding Gocd user management

Generally speaking, the permission required to pause a pipeline should be the same as the permissions required to trigger it ("operate" or "admin" permission to the pipeline or the pipeline group). https://docs.gocd.org/current/configuration/dev_authorization.html The only other thing I can guess

[go-cd] Release Announcement - 23.3.0

://www.gocd.org/download/> to try it. Cheers, Chad & Aravind On Tue, Jul 25, 2023 at 12:41 PM Chad Wilson wrote: > Hi folks - unfortunately a problem sneaked through our automated > regression in 23.2.0 which prevents UI navigation via Stage History to > older stage runs in the hist

Re: [go-cd] shouldn't required resources also be at the pipeline level?

with gocd specifically. > > regardless- yes got what i needed! > > thx again to everybody who tried to help > > > > On Mon, Jul 24, 2023 at 11:27 PM Chad Wilson > wrote: > >> If you read Jason's message a bit more closely he is conveying that the >> script

[go-cd] Re: Release Announcement - 23.2.0

:38 Chad Wilson, wrote: > Hello everyone, > > A new release of GoCD <https://www.gocd.org/releases/#23-2-0> (23.2.0) is > out. > > This release is mainly a minor maintenance release. As always, please > remember to take a backup before upgrading. > > To know more

Re: [go-cd] shouldn't required resources also be at the pipeline level?

ts as >>>> long as parameter exists and works. >>>> >>>> I still have a question about how this works in examples using >>>> templates. >>>> If we didn't define the pipeline parameter by default, how would gocd >>>&g

Re: [go-cd] shouldn't required resources also be at the pipeline level?

her fail or see it as blank i.e "no resource requirement" - I don't think there's a strong case for either behaviour being more correct. -Chad > On Sun, Jul 23, 2023 at 10:04 AM Chad Wilson > wrote: > >> With that description, if you want to use *environments

Re: [go-cd] shouldn't required resources also be at the pipeline level?

# won't this will make my pipeline fail when I want it to simply try > another agent? > exit 1 > fi > > > > or perhaps people saying this know of some environment variable that where > we can request another agent? > > obviously pipeline parameters themseles don't do

Re: [go-cd] shouldn't required resources also be at the pipeline level?

ay here, sorry. Perhaps this would be easier if you gave a specific example of how you achieve "have some pipelines that are given higher preferences for agent/build resources" currently, rather than talking in abstract terms? -Chad On Sat, Jul 22, 2023 at 6:56 AM Chad Wilson wrote

Re: [go-cd] shouldn't required resources also be at the pipeline level?

Have you tried to use "environments" (or a mix of environments and resources) to achieve what you are trying to? When scheduling jobs it's the combination of the resource and the environment that are matched to an agent, but the relevant environment is declared at the pipeline level like you

[go-cd] Release Announcement - 23.2.0

Hello everyone, A new release of GoCD (23.2.0) is out. This release is mainly a minor maintenance release. As always, please remember to take a backup before upgrading. To know more about the features and bug fixes in this release, see the release notes

Re: [go-cd] Failed to find 'git' in path with Helm based installation

CH=x86, >> GOCD_APP_SERVER_PORT_8153_TCP_PORT=8153, KUBERNETES_PORT_443_TCP_PORT=443, >> HOME=/home/go} >> >> Which is weird, because if I just run those commands directly with git, >> it's fine: >> kubectl exec --stdin --tty gocd-app-server-5c9dd5b56c-646pn -n h

Re: [go-cd] Failed to find 'git' in path with Helm based installation

The core error regarding git you are seeing is not directly related to the agent not coming up, but they may have the same root cause. What operating system, hardware architecture and Kubernetes variant are you deploying the Helm chart to? At a guess, is this perhaps a local cluster on an M1

Re: [go-cd] source code compile problem

Maybe, GoCD is built with Node 18 right now. It still uses Webpack 4, which might not work correctly with Node 20. -Chad On Mon, 17 Jul 2023, 09:59 jianhua guo, wrote: > After running the command "yarn cache clean" and "rm -rf > server/src/main/webapp/WEB-INF/rails/node_modules", I compile

Re: [go-cd] source code compile problem

The commit is still at https://github.com/dtabuenc/karma-html-reporter/commit/51ba3f91a6f19ef383c676431aa7f8c3fa73dab3 so it *should* work fine. Perhaps try yarn cache clean and rm -rf server/src/main/webapp/WEB-INF/rails/node_modules and try again? If that doesn't work, what's your Yarn

Re: [go-cd] Go-Agent || CVE-2022-42889

Hiya GoCD has been using commons-text 1.10 (with the issue you refer to fixed) since GoCD 22.3.0: https://github.com/gocd/gocd/commit/293022076385c48c9fb41485b5674fa2e69c29c1 The agent *bootstrapper* doesn't use commons-text at all, however the agent jar which is dynamically downloaded from the

Re: [go-cd] Postgres backup not working on gocd server pod

Hi Alex You would need to either - build your own custom child GoCD server image which contains the relevant postgres binaries for your Postgres version, push 8t to our own registry and then override the repository/image:tag when installing the Helm chart, or - use an additional docker entrypoint

Re: [go-cd] Config repository and github webhook

There might be some confusion here, triggering a config repo material update from a webhook is via webhooks such as https://gocd.somewhere.org/go/api/webhooks/github/config_repos/ I believe this has been available since GoCD 21.1.0 (it may work with regular

Re: [go-cd] Queries on Webhook

I'm not sure I understand the question or what you are trying to achieve, however. Webhooks notify the GoCD server of a change to *materials*. The GoCD server then finds the relevant material(s), and updates them from source to determine the changes. It then follows normal operations (as it

Re: [go-cd] Modify Fan in behaviour

rvice(aka upstreams). > And was able to simulate and see where the fan-in didn't happen when > upstreams do not share any of the materials. > > Thanks for prompt response, > Mani > > On Tue, Jun 13, 2023 at 8:43 AM Chad Wilson > wrote: > >> If it's "not monorepo&quo

Re: [go-cd] Modify Fan in behaviour

not monorepo. Is there any other alternative? > > On Tue, Jun 13, 2023, 07:18 Chad Wilson wrote: > >> Doing that means removing the guarantees fan-in offers you as to >> consistency of the material versions on upstream pipelines when triggering >> a downstream. >>

Re: [go-cd] Modify Fan in behaviour

Doing that means removing the guarantees fan-in offers you as to consistency of the material versions on upstream pipelines when triggering a downstream. It's possible to turn off fan-in globally (although I have never done so personally) but to my knowledge not for individual pipelines.

[jira] [Commented] (IO-791) Regression in FileUtils.touch - no longer creates parent directories

[ https://issues.apache.org/jira/browse/IO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725422#comment-17725422 ] Chad Wilson commented on IO-791: Sure, its just an option for folks who may be looking for other fixes

[jira] [Commented] (IO-791) Regression in FileUtils.touch - no longer creates parent directories

[ https://issues.apache.org/jira/browse/IO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725397#comment-17725397 ] Chad Wilson commented on IO-791: May or may not be acceptable for all users but the workaround is basically

Re: [go-cd] Optimizing Plugin Loading Time in GoCD Server

Yeah, I agree with Ashwanth. You'd need to share more details, like the logs during start-up, version number, nature of your deployment, list of the plugins etc and details of your analysis - and clarify whether you are talking about the server restart time or an agent. There's not enough

Re: [go-cd] Ansible + Mitogen Performanceproblem

don't > expect mitogen will get ever any bigger updates again. > Currently, we have 20 servers with 10 go-agent each. To be honest, I think > 10 agents are still to much and if all 10 are running mitogen will start > slowing down again. > > Next we will try to get the go-agent runni

[jira] [Commented] (IO-791) Regression in FileUtils.touch - no longer creates parent directories

[ https://issues.apache.org/jira/browse/IO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723762#comment-17723762 ] Chad Wilson commented on IO-791: Thanks [~ggregory] ! > Regression in FileUtils.touch - no longer crea

  1   2   3   4   5   >