-
Notifications
You must be signed in to change notification settings - Fork 41
CI build monitoring (build matrix) #25
Comments
@harlantwood 👍 👍 (also, i think markdown numbering bit?) I'd vote for "we should probably add badges to the readme's, you could see build health there." I'd also like to have one page that aggregates everything, but dont want to add yet another thing to manage. it we could do it programmatically (i.e. run a program that verifies every repo has CI setup correctly, and is added to whatever program, etc.) that may be fine, but manually is painful and errorprone. |
Yeah, I like that. Maybe a single page JS app (say hosted on GH pages (and later (or maybe now) IPFS) so there is basically nothing to maintain) that polled all projects under IPFS in Circle (or Travis, but hopefully not both) and:
And displayed all that on a single page, inspired by, but simpler than http://ci.pivotallabs.com/ Thoughts? |
@harlantwood i would really, really like that. maybe we can have a big grid, a bit like build.golang.org |
I found something very close. It comes in two visual flavors: https://gist.github.com/petehamilton/5494978 This version is mostly ruby. But translating it to run 100% client side should be very easy. I'll take a crack at that when I have time -- or anyone else feel free to take this one too. |
Another interesting example: http://ethereum-buildboard.meteor.com/ |
OK, I'm going to take a stab at a fully client-side build monitor tool that can run from IPFS. THIS LIST IS DEPRECATED, PLEASE SEE THE NEW VERSION AT ipfs-inactive/project-repos#1 (comment)Features:
Deployment:
|
So far we are showing travis and circle build status for each repo in IPFS org. Very cool, I've been wanting to do this for a while! try this first: https://ipfs.io/ipfs/QmdicuP1EArpwc5avocNeBCw3Zd4CDAguhcuKy7rDxkzTq/ backup url: http://harlantwood.github.io/repos/ source: https://github.com/harlantwood/repos Feedback anyone? Likely interested: @RichardLitt @jbenet @diasdavid @dignifiedquire |
This is pretty sweet! :D This could go into something like dashboard.ipfs.io with stats about the status of our public gateways, some metrics about the network, commit activity in all the projects, all of the things :D |
Good stuff ! but there seem to be a lot of unkown builds atm. |
Can someone with access fork this over to the ipfs github org plz? @jbenet @whyrusleeping |
What is the right name for this dashboard? I think 'dashboard' is not so great because webui has a lot of dashboard-ness. I suggest 'status'. Lives at status.ipfs.io Other name suggestions? |
How about |
build.ipfs.io? status and dashboard are a bit too generic |
How about |
added @harlantwood as contrib. |
Closing this issue, moved to ipfs-inactive/project-repos#1 |
We have a bunch of projects using CI.
It would be cool, possibly useful too, to have a single page that gathered them all together. Something like:
http://ci.pivotallabs.com/
Which is an instance of this rails app:
https://github.com/pivotal/projectmonitor
Works with Circle CI, Travis and others. Could run on a free heroku instance (or wherever).
Alternatively, people who care about the overall health of multiple/all builds could pull down status messages to local notifications with CCTray, BuildNotify, etc ( some info on that for Circle here: https://circleci.com/docs/polling-project-status ).
In any case, we should probably add passing/failing badges to the projects' READMEs, so you could see build health there.
We could leave it as is: build failures should notify the committers, and if you want to check, you can probably peruse IPFS builds in Circle or Travis.
Thoughts? I vote for # 3 + # 1, in that order, with optional # 2 encouragement / instructions.
The text was updated successfully, but these errors were encountered: