Learn more about these different git repos.
Other Git URLs
Rawhide tree expiry is manual at the moment, unless I missed something.
You are correct, it's manual. We need to come up with agreed upon policy as to how many to keep around, since these serve as our "archives of previous rawhides" to run comparisons against.
The quick hack would be to have a cron.monthly script that removes all $(month-2) trees. Of course, you get into fun with year wrapping.
Probably just easier to keep N trees around, cleaning a new one off each night, as part of the compose.
masta will take care of this.
one thing we want to do is makesure we have at least one installable rawhide tree
resetting ownership as this has not been done
We need to decide on a policy
we need a script to implement the policy and have it ran as part of rawhide.
In todays meeting
15:50 < dgilmore> #agreed we will remove any branched/rawhide compose older than 14 days
15:50 < dgilmore> #action dgilmore to implement rawhide/branched cleanup in nightly.sh
This is now done, we keep two weeks of composes
Metadata Update from @notting:
- Issue tagged with: easyfix
to comment on this ticket.