| Key: |
CIB-2005
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
4
|
| Assignee: |
Unassigned
|
| Reporter: |
Rohan McGovern
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 10/Jun/09 08:43 PM
Updated: 24/Jun/09 11:11 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
2.1.4
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related
|
|
This issue is relates to:
|
|
CIB-1470
57662,63156: Pulse should keep the ch...
|
|
|
|
|
|
|
It would be useful if we could configure cleanup rules to delete the logs from builds but leave the remaining build data. Or even better, delete the logs from successful builds only. Our build logs are large (up to ~4.8GB a day), which forces us to set cleanup rules to delete "whole builds" quite aggressively; that means we lose some data which may still have value.
Perhaps related to CIB-1470.
|
|
Description
|
It would be useful if we could configure cleanup rules to delete the logs from builds but leave the remaining build data. Or even better, delete the logs from successful builds only. Our build logs are large (up to ~4.8GB a day), which forces us to set cleanup rules to delete "whole builds" quite aggressively; that means we lose some data which may still have value.
Perhaps related to CIB-1470.
|
Show » |
|
There is functionality coming in 2.1 that allows finer grained cleanup rules to be configured. They currently allow for the cleanup of the artifacts produced during a build whilst leaving the build result in the database. This will do what you want it to do if the build log you are referring to is a captured artifact. If not, we can add the build log to the list of things that can be selectively cleaned up.