-
Notifications
You must be signed in to change notification settings - Fork 29
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
Implement comprehensive test before release #2536
Comments
@balhoff I would like to just copy paste your QC pipeline into the Uberon build process. Can you point me to the makefile again? |
(the one you do the merge of the various master branches) |
So this actually runs in github ci.. tbh, wouldn't it be better if we ran that exact action? Otherwise you have to remember to inform us :D I think actions cannot send emails (I went through that rabbit whole once, so I am not going there again), but could we have it create an issue on Ubergraph (or anywhere else) that tags the entire tech team (@shawntanzk @ubyndr @anitacaron and @matentzn)? We can also install this action in one of our repos, whatever is best |
I will keep running it in Ubergraph, since integration is the focus for that repo, but you could run it elsewhere, especially if you want to trigger by commit instead of the daily schedule. Creating an issue is a good idea, although it runs every day. How should we stop it from making a new issue every day? |
Of course it should only create an issue if it fails! |
(comment on an issue if one already exists) |
I think if it runs daily, and it just comments on an issue tagging us all, than we will have done the world a big service. I would love extending that to other ontologies moving forward. |
This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken. |
This issue has not seen any activity in the past 6 months; it will be closed automatically one year from now if no action is taken. |
Person that is responsible for release should run a comprehensive set of test (we can turn on checks/CI that we turned off)
That way we get informed before release rather than after
This should be a single command (following what Jim has done)
The text was updated successfully, but these errors were encountered: