Currently https://pagure.io/releng/failed-composes/issues has over 900 issues, we should probably find a way to close old tickets.
Maybe a successful compose should be closing the tickets older tickets ? Or we could just cleanup based on time for example anything that is older than 60 days ?
We have never had a "FINISHED" compose. ;)
I agree we do need to clean them up... perhaps after 2 weeks (since we only keep the composes around for that long, longer than that we might not be able to do much).
Or perhaps we keep open all DOOMED ones until we get a INCOMPLETE, then close all old doomed ones (and perhaps all other old INCOMPLETE ones too). ie, when there's a incomplete, it closes all earler ones, when it's DOOMED we keep them open. That would allow conversation/tracking in DOOMED tickets to get composes working again.
Yes, this is an outstanding feature request. Thanks for opening the ticket. There are a lot of ways this tool could be improved :)
Time would be easiest to implement, but I've had ideas like "closing older tickets if a compose succeeds".
@kevin We have never had a "FINISHED" compose. ;)
I think that used to be true but I think we've had at least one or two FINISHED rawhide composes in the past few years. Either way we do get a lot of notifications here and it would be nice if we could get some consistency in our builds succeeding.
I started to close some of the really old tickets based on time using a script (sorry for the email spam).
Now that we have labels on tickets which should make it easier to filter them. We could try to implement some logic in the tool, to close older tickets
Login to comment on this ticket.