Bug 1130233 - koji: Immediate scratch build purging
Summary: koji: Immediate scratch build purging
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: koji
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Mike McLean
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-14 15:10 UTC by Mikolaj Izdebski
Modified: 2018-10-26 20:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Mikolaj Izdebski 2014-08-14 15:10:59 UTC
(Moved from trac because appearently it's not very active.
See: https://fedorahosted.org/koji/ticket/284 )

Please implement boolean option for build XML-RPC call which when set together with scratch flag would cause scratch build results (except logs) to be immediately removed (instead moving to scratch location) after build upon completion.

Justification: Results of a single scratch build may take space in order of hundreds of megabytes and they add up quickly. One of the most important uses of scratch builds is simply checking whether package builds or not. Build results (RPMs) are not needed and only waste storage. If this feature is implemented then submitter of scratch build will be able to tell Koji that build results are not important and should be removed immediately to conserve storage.

This feature has to be explicitly enabled by build requester thus it's completely backwards-compatible.

I can provide patch if you think that this feature should be implemented.

Comment 1 Parag Nemade 2014-08-14 16:52:16 UTC
+1. I too have same kind of thinking. While doing package reviews/updates I sometimes need to just do scratch build for rawhide and after checking the results I no longer need the logs.

Comment 2 Fedora Admin XMLRPC Client 2016-03-10 14:44:24 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Note You need to log in before you can comment on or make changes to this bug.