Coloring of projects based on pass/fail needs to take branch into account

[leto]

Currently, if a project has a master branch with all passing tests, but then someone pushed a commit on a topic branch that fails a test, the project will show up "red" on the dashboard, which is misleading. I am not quite sure what the best course of action is, ideas?

We could add a config key which specifies a regex for which branches to care about failures on, and the default could be just the string "master". We already have a similar variable for when to send failure emails.

[fcuny]

there is another issue. If you are using perlbrew, and the build pass for every perl except one, should we color in red ? orange ? green ? maybe another key in the config to support this ?