Comment 1 for bug 969291

Attaching a screenshot of the implementation I did in the development branch.

This adds a new field "available" to qatracker_build that's meant to be populated by an external script (probably a python script).
The flag is set to 1 => available by default and can be set to 0 once we determine it's not accessible.

Suggestion on better wording are welcome.