Hello Warren, Can you share these please?
1. Output of this command in one of those directories: *hg showconfig paths.default * 2. The configured URL in the config. This behavior should not be happening. Can you confirm with a git or SVN material that it works properly? Thank you, Aravind On Fri, Nov 24, 2017 at 4:24 AM, Warren Farre <[email protected]> wrote: > > I am having the same issue, we have a fairly large hg repo as the > material. It seems like the clone never completes and go just keeps adding > more and more folders in flyweight with partially cloned / updated copies > of the repo (there were 25 folders for the single pipeline I am trying to > setup). > > Anyone know how to fix this? > > > > On Tuesday, 22 July 2014 13:58:42 UTC+2, Aravind SV wrote: >> >> Hi Eric! >> >> The flyweight directory should definitely not grow. Go should clone the >> material (SCM, git or hg) repository the first time, and from then on, it >> should just poll for changes (the size shouldn't increase much). It should >> also have only one directory per material. When you say it grows and runs >> out of space, do you see the number of directories in that flyweight >> directory increase, or do you see the directory size of one or more >> directories increase? >> >> Is your config public enough that you can show it here, somehow? >> >> Cheers, >> Aravind >> >> >> >> On Sun, Jul 20, 2014 at 2:33 PM, Eric Ramseur <[email protected]> wrote: >> >>> Hello, >>> >>> I'm installing go to simply pull from some HG or Git repos, compile the >>> source in .NET on change and deploy to another server. >>> >>> It seems simple enough but I'm running into issues. The first of which >>> that by default the flyweight directory checks out the source every 2 >>> minutes and has no limit. It seems this should be an option to turn off. >>> I do mind checking out source every 10 minutes and not just growing a >>> directory. >>> >>> Even when I pause pipelines this directory continues to grow and crash >>> my server. I understand go uses this directory to make polling more >>> efficient but it should be an option and not by default ? >>> >>> Is there anyway to still have polling changes and not grow the flyweight >>> directory? >>> >>> Also does anyone have a simple config of a net project compile and >>> deploy on a remote machine? This seems to be the normal real world example >>> (even when you are not on dot net) : Poll source on change, pull , compile >>> , deploy on another machine. >>> >>> Thank you for your patience >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "go-cd" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
