I am looking for the build artifacts location in GoCD server, also my pipelines are very slow. #11594
Replies: 2 comments 1 reply
-
|
Sorry, it's not really clear what you're asking here, or what you have already done to investigate. Artifact files storage location depends on your deployment method but if it's a raw windows install, probably the If your pipelines are slow, you probably want to look at the operating system process metrics (memory, CPU) where your agents are running, and compare to how long it takes if you run the same commands outside GoCD. Since GoCD agents just fork processes to run your builds, often slowness is not GoCD itself, but configuration of tooling or the server where the agents are running. You might get wider help on the GoCD forums at https://groups.google.com/g/go-cd . |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply @chadlwilson when I run 3-4 pipelines it takes 2 hours to complete. |
Beta Was this translation helpful? Give feedback.
-
|
Please re-read the above? You will need to analyse OS metrics and npm build logs yourself, do some basic problem solving, and ask for more specific guidance based on your research. Generic hardware specs aren't helpful beyond noting that there there should be no issue with a properly configured GoCD server and agent working on that hardware. If agents are on the same host it depends what your builds are doing as to additional memory or CPU requirements. No-one else can know what your npm build is doing, how long it normally should take outside GoCD or how long it takes on alternative hardware but yourself. 🙂 |
Beta Was this translation helpful? Give feedback.
-
I am looking for the build artifacts location in GoCD server, also my pipelines are very slow.
npm build took long time to finished. When I run 3-5 pipeline build server hanged using 64GB RAM + 400 GB memory (Windows Server 2019)
I used ci cmd instead of install change the firewall settings
Beta Was this translation helpful? Give feedback.
All reactions