Closed
Bug 739527
Opened 14 years ago
Closed 14 years ago
remove builds older than 7 days from jenkins build slaves
Categories
(Cloud Services :: Server: Other, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Atoll, Assigned: telliott)
Details
(Whiteboard: [qa-])
Please configure pruning of builds older than 7 days (*) within 5 business days.
Alternately, please indicate within 5 business days that we can permanently shut off centos5.build and that rhel6.build is unaffected.
This issue crashed centos5.build so badly tonight that it had to be taken offline for manual repair by Operations.
(*) It's okay to keep the 5-10 latest okay builds per product, regardless of how old they are. For instance, "ls -t -d -1 build[1-9]* | tail -n +10 | xargs echo rm".
Paths of concern that are not being pruned:
/var/lib/jenkins/workspace/*/build[1-9]*/
/var/lib/jenkins/workspace/*/rpms/*.rpm.[1-9]*
Updated•14 years ago
|
Whiteboard: [qa-]
| Assignee | ||
Comment 2•14 years ago
|
||
I have added
#cleans up the workspaces that jenkins leaves behind, filling up the disks00 1 * * * ls -t -d -1 /var/lib/jenkins/workspace/*/build[0-9]* | tail -n +50 | xargs rm -r
To the sudo crontab on both boxes. Also ran the command to clear it out manually. That tends to leave us with about two days worth of builds, which should be plenty
| Assignee | ||
Comment 3•14 years ago
|
||
Well, with a carriage return in the correct place :P
| Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•