Config or other means to track Jenkins jobs of interest for coverage

A couple of ideas for this: we could just literally commit to a config file with projects/jobs of interest. Or these could be added as database objects via the admin (until a suitable form comes into existence, e.g.) Alternately we could see how expensive it would be to just scan Jenkins or builds with coverage--in this case we'd probably still want to track "projects of interest", but maybe this would only be interesting when we've decided on a means to aggregate projects, e.g.

Chris Gagnon, your thoughts?