Thanks. Good to know that it won't occur again. Since I don't 
use ArtifactCleanup I am now manually deleting the files (well, actually I 
wrote a small program which does that), so I'll be able to copy the 
relevant folders.
 
Kind regards,
Daniel Rose

Am Donnerstag, 21. Juni 2012 12:17:57 UTC+2 schrieb Ruben Willems:

> Hi
>
> this has been fixed from 2012-05-05 onwards :
>
> https://github.com/RubenWillems/CruiseControl.NET/commit/9d8a6a054854ac3253bbc99514857a9b97338760
> http://www.cruisecontrolnet.org/issues/103
>
>
> so any build higher than 1.7.712.8065 is ok
>
> if you use the ArtifactCleanUp publisher, those xml files will be cleaned 
> up automatically
> and they will not be generated again by default.
>
> I'll update the release notes that this is also fixed :-)
>
> with kind regards
> Ruben Willems
>
>
> On 21 June 2012 11:33, Daniel Rose <[email protected]> wrote:
>
>> In my company, I am currently switching the server where 
>> cruisecontrol.net is running on. While copying the project data 
>> (including the build artifacts), I noticed that in the Artifacts\buildlogs 
>> directory there are a huge number of tiny (couple of KB) .summary files. 
>> Huge as in 130000 to 190000 or more (in each directory!). That neatly 
>> explains why it often took minutes when viewing any project's page on the 
>> web dashboard.
>>  
>> Anyway, it seems that those are temporary files which are not being 
>> deleted. I haven't found any issue for that so far, and I have no idea if 
>> those files are created by cruisecontrol.net or a plugin (although I 
>> assume the former).
>>  
>> I have been continuously upgrading the installation of ccnet; currently I 
>> have 1.7.706 installed. As far as I can tell, this issue is there since a 
>> very long time (opening an Explorer window to such a directory tends to 
>> freeze everything for 10 minutes or more, since Explorer isn't capable of 
>> handling directories with hundreds of thousands of files). I tried it once, 
>> and it seems these files are created every minute or so when ccnet is 
>> running.
>>
>
>

Reply via email to