You can set your workspaces so they clean every build or start
fresh. Depending on your build process, you can have your job clean
up temp files after it finishes. Only archive items that are
needed.
I think I suggested this before, but it might not be a bad idea to
open feature request against hudson to allow the old workspace clean
up that Hudson does, to be configurable. Right now I think it does
it every 30 days.
Dave
On 10/04/2011 04:30 PM, Kim Moir wrote:
I opened a bug for
this request.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=359912
Kim
From:
Denis Roy
<denis.roy@xxxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
Date:
10/04/2011 04:09 PM
Subject:
Re:
[cross-project-issues-dev]
Disk usage report for Hudson/Build
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
On 10/04/2011 04:04 PM, Kim Moir wrote:
I have been cleaning up our old
builds
for the last hour. I do have them configured to only keep a few
builds
but since they are 6GB each they tend to consume a lot of the
space.
Can your build job simply not move them to /shared where there's
much more
space, rather than keeping them in the workspace?
Denis
Kim
From: David
M Williams <david_williams@xxxxxxxxxx>
To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 10/04/2011
03:12 PM
Subject: Re:
[cross-project-issues-dev] Disk usage report for Hudson/Build
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
> Looks like the Hudson "fastlane" will soon be out of local
workspace disk space... But there is 1.3TB left on /shared.
and ... ?
I ask rhetorically :)
First, I assume "fastlane" is the same as "hudson-slave3"
in your reports?
Second, since only about "50% of use" shows up in your report,
I guess there's a lot of "little" directories consuming 20G?
But, in either case ... what are we to do? Pester the
eclipse-equinox team
to clean up after themselves? Ask you to delete anything more
than a week
old?
I see we are not even supposed to use fastlane, by default,
according to
http://wiki.eclipse.org/Hudson#Slaves_and_usage
But, my main point, I could not find any pointers on "how to
clean
up after your build jobs" or "how to keep slave disk usage down"
though I thought for sure this has come up before.
So ... not rhetorically :) ... does anyone know/remember those
tips?
Thanks,
==== hudson-slave3.eclipse.org ====
/dev/xvda1 55G 53G 2.9G
95% /
-> Usage exceeding 1GB for: Hudson workspace on
hudson-slave3 (50G capacity)
(2011-10-04T10:00)
16.5G eclipse-equinox-test-N
15.7G eclipse-equinox-git-test-N
1.4G modisco-integration
==== END: hudson-slave3.eclipse.org ====
From: Denis
Roy <denis.roy@xxxxxxxxxxx>
To: cross-project-issues-dev@xxxxxxxxxxx
Date: 10/04/2011
01:15 PM
Subject: Re:
[cross-project-issues-dev] Disk usage report for Hudson/Build
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Looks like the Hudson "fastlane" will soon be out of local
workspace
disk space... But there is 1.3TB left on /shared.
Denis
==== hudson-slave3.eclipse.org ====
/dev/xvda1 55G 53G 2.9G
95% /
-> Usage exceeding 1GB for: Hudson workspace on
hudson-slave3 (50G capacity)
(2011-10-04T10:00)
16.5G eclipse-equinox-test-N
15.7G eclipse-equinox-git-test-N
1.4G modisco-integration
==== END: hudson-slave3.eclipse.org ====
Denis Roy
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
