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

Bug #1310419 reported by Allan LeSage on 2014-04-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

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?

Changed in qa-coverage-dashboard:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers