Right now, you can set rpmbuild_timeout in kojid to have kojid kill builds that reach this time limit.
Unfortunately, some builds avoid this by being freed to another machine when kojid restarts or causing kojid itself to crash and restart so it starts over. So, while they never reach the rpmbuild_timeout, they restart over and over and linger for many days until someone cancels them.
It would be nice if we could add something to the hub to limit total time since submission, even if it wasn't building or was building many times during that period.
Would it be worth a policy? That some tags/builds shouldn't be affected by this and restart forever, while some other could cancel it? Or is it more hub-wide option?
Metadata Update from @tkopecek: - Custom field Size adjusted to None
Policy could be nice, then you could for example limit scratch builds more than regular...but if a global option is easier that would still be helpfull.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/1876
Please continue any further discussion there.