• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

j0k3r / banditore / 136 / 4
90%
master: 91%

Build:
Build:
LAST BUILD BRANCH: fix/guzzle7
DEFAULT BRANCH: master
Ran 03 Mar 2017 11:34PM UTC
Files 21
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Mar 2017 11:19PM UTC coverage: 90.3% (-0.06%) from 90.357%
COVERAGE=run

push

travis-ci

j0k3r
Add Github Client Discovery

Find the best token to use to fetch data to avoid Rate Limit.

The goal is to find the best authenticated method to avoid hitting the Github rate limit.
We first try with the default application authentication (which might work 99% of the time).
And if it fails, we'll try each user until we find one with enough rate limit.
In fact, the more user in database, the bigger chance to never hit the rate limit (this is theorical).

This mostly to handle new users.
When a new user logged in for the first time we need to retrieve all releases/tags of its starred repos and it use a lot (really a lot) of rate limit.

Also, using "ocramius/proxy-manager" to lazy services which require the Github/Client because we don't want the Github Client Discovery to be triggered when clearing cache.

512 of 567 relevant lines covered (90.3%)

2.81 hits per line

Source Files on job 136.4 (COVERAGE=run)
  • Tree
  • List 0
  • Changed 7
  • Source Changed 7
  • Coverage Changed 7
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 136
  • Travis Job 136.4
  • 420fc97c on github
  • Prev Job for COVERAGE=run on github-client-discovery (#123.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc