-
Notifications
You must be signed in to change notification settings - Fork 209
First steps toward OBO Dashboard #1069
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
Conversation
I know this is going to be a never ending story, but I would strongly encourage at least internal logical consistency to be added. This really trips up OBO wide integration; not that is enough (it is a baby step), but it is really important. |
On the Operations call today agree to merge the progress so far. We'll continue discussion and track updates in #1076. @beckyjackson please fix the conflicts and then I'll merge. |
First pass at automated checks for OBO Foundry principles. See a test version here:
http://obo-dashboard-test.ontodev.com/
Some have been discussed so far:
1 - #1019 [discussed]
2 - #1018 [discussed]
3 - #1017 [discussed]
4 - #1016 [discussed]
5 - #1015
6 - #1010
7 - #981
8 - #1009
9 - #1008
11 - #1007
12 - #1006
16 - #1020
These checks run on Jenkins, where a zip folder containing the results is archived: https://build.obolibrary.io/job/obofoundry/job/OBOFoundry.github.io/job/dashboard/
A full build takes 6 to 7 hours.
Documentation pages have been added for each automated check. They can be accessed from their principle page.