Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] restarting sandbox hudson

On 06/10/2013 09:23 AM, Matthias Sohn wrote:
Looking at current disk usage at
there are a couple of jobs consuming quite a lot of disk space for their workspaces,
maybe some of them could free some space. I'd recommend they all configure their
jobs to only retain the artifacts of the last successful build.
I cleaned some other jobs to keep only the 3 last builds (GMF-Tooling-Sonar, Nebula-sonar, Nebula-incubation-sonar), it should save a few hundreds megs.
Just after, I re-triggered the platform-sonar job ;) I'm crossing fingers to see it going to the end without filling all the free space.

Probably a large fraction of this space is consumed by job-private maven repositories.
Not sure if there is a way to get rid of the need to use private maven repositories, 
AFAIK this is needed since sharing local maven repositories between multiple jobs
doesn't work reliably.
Yes, private repositories seem necessary to ensure no side-effects between jobs and because Maven repository doesn't accept well concurrent modifications.

Overall it looks like sandbox Hudson needs more HDD resources.

Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

Back to the top