On 08/06/2012 05:07 PM, Seth Vidal wrote:
On Mon, 6 Aug 2012, Mike McLean wrote:
> Some sort of 'retired' flag to hide them is on my todo list.
> They generally can't be removed from the db because they are
> referenced by other tables. If they've seen any kind of use, the
> references are extensive.
In many cases the last time they saw any use was > 3yrs ago.
At what point can we walk away from old data?
And out of curiosity - what is being stored related to the builder?
As a general rule, we preserve all relevant data for completed builds.
That includes which hosts performed them. Specifically, we have
references in the task table and the buildroot table.
> In the meantime, I suggest using list-hosts --enabled on the
> line. The web ui currently defaults to just showing the enabled builders.
Right - but when I disable hosts intentionally to reinstall/update them
- I need to use just list-hosts - which means I see about 100+ entries -
when really we only have like 35 of ACTUAL hosts.
I know the current situation is less than ideal. It's common to
temporarily disable hosts, and there is no easy way to distinguish those
that are temporarily disabled from those that are permanently retired.
That is why I want to implement the retired flag for builders. This will
solve the display problem.