Flyweight Directory grows and Microsoft .NET

[Eric Ramseur]

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

[Aravind SV]

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

--
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 go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Eric Ramseur (ANANT)]

Yes the directory just keeps creating a new material guid directory over and over for the same material.

It seems it thinks its a new repo every time so it does this.  I read a little about why on other sites.

We have since removed Go as we needed a quick CI/CD solution.  We used team city with octopus deploy.

Would be nice to have sample configs that admins can use to quickly get started with go and simply modify the material settings.

We simply needed a source control pull, ms build, and then IIS deployment on another server.  Nothing too crazy but I couldnt get the material step to work.  It would never do a successful run.

--
Regards,

Eric Ramseur | Internet Architect & Partner

To empower people through the Internet to create a better world.

Anant Corporation | http://anant.us
394 Broadway, 5th Floor
New York, NY 10013

o 855-262-6826 X 102 | li  http://www.linkedin.com/pub/0/430/214


This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Anant Corporation .  If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone.  Please contact the sender if you believe you have received this email in error.

[Aravind SV]

:( That's sad. Sorry, you had a bad experience and to see you go.

If possible and not much trouble, consider providing some information about the material (if it's a public GitHub material, for instance), or about the environment (Windows / Linux), or even better, logs. Maybe we can prevent others from facing the same issue.

Thank you,

Aravind

[Eric Ramseur]

It was default material Hg. I used a couple of them HG/Git/SVN.

I followed the instructions from the docs and the code was indeed being checked out. However it seems the agents kept thinking it was a new material and kept checking out the same source every 2 minutes. It seems it be nice if their would be an option to pull the source only when it changes in the polling method.

[Warren Farre]

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?

[Aravind SV]

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

To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscribe@googlegroups.com.

[Warren Farre]

Hi Aravind

Sorry for the late reply but not working on this full time. I found that the hg update was failing (due to a windows path / filename length (270 characters) restriction issue, as the flyweight gets created a fair bit down the path especially when installing the server to c:\program files (x86) and we had some deep paths with long names in our repo).

I moved the installation to a shorter path and everything is working as it should.

SO.. it would seem the actual issue is that goCD keeps creating new flyweights when the hg update fails. 

You received this message because you are subscribed to a topic in the Google Groups "go-cd" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/go-cd/cFoVqsqS4qA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to go-cd+un...@googlegroups.com.