scribu / travis-stats Goto Github PK

View Code? Open in Web Editor NEW

44.0 2.0 22.0 149 KB

Travis CI build charts

Home Page: http://scribu.github.io/travis-stats/

License: GNU Affero General Public License v3.0

HTML 13.91% JavaScript 79.26% CSS 6.83%

travis-ci chart

travis-stats's Introduction

travis-stats

Charts for Travis CI.

Demo: http://scribu.github.io/travis-stats/#wp-cli/wp-cli

Blog post: http://scribu.net/blog/travis-ci-build-stats.html

Private repositories

If you want to show charts for private repositories, you'll have to host the files yourself.

Add a config.json file in the root directory, with an API token:

{
	"travis_api_token": "YOUR TOKEN",
	"travis_api_endpoint": "api.travis-ci.org",
	"travis_endpoint": "travis-ci.org"
}

Important: To avoid getting your API token stolen, configure your server to require basic auth before serving both index.html and config.json.

travis-stats's People

Contributors

Stargazers

Watchers

Forkers

olivierlacan afeld shyam334 suzannesoy edunham phongdly grasmash colindean larsxschneider dvoet jdrew1303 pombredanne nylen arthaey nhdaly aibarbetta volkm ferrastas hathway abhinay4021

travis-stats's Issues

Option to show human start-to-end waiting times

Thanks for travis-stats!

Would it be possible to add an option to chart the actual, start-to-end running time? With more than one build job, the duration isn't so useful because jobs are run concurrently and the real, human waiting time is shorter.

For example, one project has eight jobs (one per Python version) which take between 4 and 9 minutes each. The total duration is about 50 minutes, but because 5 jobs can run concurrently, the actual time I have to wait is about 10 minutes. I'd like to primarily optimise the human waiting time.

The Travis CI API has "started_at" and "finished_at" timestamps:
http://docs.travis-ci.com/api/#builds

Of course, occasionally a job can be manually restarted, causing a longer time. But these are rare and the trend would still be visible.

Thanks!

It looks like .org is being deprecated in favor of .com soon:
https://blog.travis-ci.com/2018-05-02-open-source-projects-on-travis-ci-com-with-github-apps
Over the next several months, we’ll be migrating all travis-ci.org repositories and customers to travis-ci.com

Unable to hit Travis Enterprise locally

Hitting the CORS problem:

d3.v4.min.js:3 

XMLHttpRequest cannot load file:///Users/cdean/Source/travis-stats/config.json. Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.

send @ d3.v4.min.js:3

Is there a way to avoid CORS problems on file:// urls for development? Or am I going to have to set up a simple server, e.g. python -m SimpleHTTPServer, in order to do development?

Sub-minute test times cause labels to be unreadable

Able to reproduce on https://scribu.github.io/travis-stats/#pittmesh/pittmesh.net