QA (public) » openQA Project (public)

and the total sum of all size limits would be interesting too I guess to prevent overbooking of the disk :)

It's not so easy. Job groups can share assets, but their size limits apply per group. Only if an asset is out of the limit for all groups, it's deleted. And you shouldn't even come close to overbook the disk with assets - as the test results and temporary asset uploads are on the same disk.

About the initial issue:

It would be grouping the assets by job group and show the accumulated size. And yes, by default this grouping would also include assets shared with other job groups. However, it would be possible to accumulate only exclusively used assets.

Not sure whether the grouping can be done with the help of the database (SQL GROUP BY statement) rather than doing it manually. When having to filter out shared assets it is likely only possible to do it manually.

But the variant to filter out shared assets makes likely most sense because only exclusive assets are definite candidates for cleanup (and cleanup is the purpose and only use for the size limit).

About making this part of the assets list:

and it's unclear when they were used the last by what job group
...
I see this as part of the asset list

So the table of assets should show the last use? And 'the last use' includes - beside the date - the job group which has the job which lastly referenced it?

I also noticed that we actually save the size of each asset in the database but do not display it in the asset table in the web UI. At least that could be easily improved.

You can also commit data back into the DB from the GRU tasks - that calculates a lot already anyway.