[
https://ovirt-jira.atlassian.net/browse/OVIRT-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35521#comment-35521
]
Barak Korren commented on OVIRT-1811:
-------------------------------------
We've discussed this multipile times in the past - making a package retention
policy that works right and does not introduce various subtle issues is hard -
and we lack the proper tooling for this (E.g. a tool that can remove any
package older then X days while still keeping at least N versions of each
package and also keeping enough yum MD files so that for the duration that yums
keeps repomd.xml cached by default, users will never get 404 errors)
> tested rpms piling up
> ---------------------
>
> Key: OVIRT-1811
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1811
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: sbonazzo
> Assignee: infra
>
> /var/www/html/repos/ovirt/tested/master is now 351G
> This causes
> http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_nightly
> to run for one hour downloading obsolete code.
> Do we have something cleaning up tested repos?
> If not, can we get one?
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
