Travis build metrics should account for > 100 repos

Description

Our travis API script will interrogate Travis's REST API to determine how many builds are running in our entire org. It hinges on a `get_repos` REST call that is limited to the first 100 repos on Travis's side. As of this writing, we are using 67 repos, so we may eventually hit that limit. We should account for that in our script.

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Assignee

Unassigned

Reporter

Ben Patterson

Labels

Reach

None

Impact

None

Platform Area

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Platform Map Area (Levels 1 & 2)

None

Platform Map Area (Levels 3 & 4)

None

Epic Link

Priority

Unset
Configure