Those badges are also often useless. For example, here's their current failure reason: Bad response status from coveralls: 422 {"message":"service_job

Those badges are also often useless. For example, here's their current failure reason: Bad response status from coveralls: 422 {"message":"service_job_id (716381595) must be unique for Travis Jobs not supplying a Coveralls Repo Token","error":true} Has nothing to do with the actual compilation status. In projects I'm involved with, the vast majority of CI errors were due to stupid things, not actual code problems. For example, last week our tests were failing because the east coast IBM data center that ran the tests was offline due to extended power outages from the weather.