Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile a Matrix Showing Implementations' Adherence to the Suite #20

Closed
Julian opened this issue Jan 29, 2013 · 7 comments
Closed

Compile a Matrix Showing Implementations' Adherence to the Suite #20

Julian opened this issue Jan 29, 2013 · 7 comments

Comments

@Julian
Copy link
Member

Julian commented Jan 29, 2013

See json-schema-org/json-schema-org.github.io#16

@nickl- nickl- mentioned this issue Jan 29, 2013
@nickl-
Copy link
Contributor

nickl- commented Jan 29, 2013

This is where the changes to the list of implementations reached so far:

Screen Shot 2013-01-30 at 12 51 49 AM

All github information being pulled from site at real time.

Have you given the storage of matrix results any thought? I played around with a way to capture unit test results from travis, as well as anyone else running a test and keeping revisions of the results with totals etc on github itself.

It can be accomplished with the [github database api[(http://developer.github.com/v3/git/) and you can see the results from some initial bashing at the problem can be seen here https://github.com/Respect/Foundation/issues/26#issuecomment-12614405 works like a charm.

This information we can then pull into the table results in a similar fashion.

Savvy?

@fge
Copy link
Contributor

fge commented Jan 30, 2013

Uh, I cannot read this table at all :/

And the version of my library reported is "prehistoric" as well. OK, I update it at a frantic pace, but care to explain what the different columns mean?

@Julian
Copy link
Member Author

Julian commented Feb 15, 2013

I haven't thought about how to do this yet, no. json-schema.org is hosted on github which limits how dynamic we can be I guess. Have to think about this more. Welcome to hear more comments.

@iainbeeston
Copy link
Contributor

I'm a bit late to the party, but could you use a build server (eg Travis-ci) to run the test suite then push the results to the github site (via an api) which could then save them to the database for rendering later?

@iainbeeston
Copy link
Contributor

Or better yet, set up an api to receive results, and issue each project with a secret key to access the api. Then get them to push their own results as part of their regular build. Might be a lot easier to maintain that way

@handrews
Copy link
Contributor

Perhaps close this in favor of json-schema-org/website#125 on the grounds of keeping all info about implementations in one place (the web site)?

@Julian
Copy link
Member Author

Julian commented Sep 25, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants