Closed timosachsenberg closed 1 year ago
We do that. For every push every file. For every PR only changed files.
just to make sure 1. and 2.?
In theory we should cover the binder functionality in the pyopenms tests. If binder breaks due to outside changes in Openms, then the pyopenms tests were not good enough.
You can try to trigger them from e.g. an Openms action but it will be hard to catch. No one will look in this repo here.
hmm I think we need to find a way to monitor the outcome of these actions. CDash seems to be a bit restricted in this regards. Maybe we should look for (additional) dashboard that just shows a traffic light and links back to the action log.
Yes but I am not sure if this tracks cross-repo
maybe something REST based that can be triggered with curl or similar to report the outcome
I think the correct way would be to have specific openms versions to be used. As part of the specification. So when this gets updated here, it will be tested again.
And to release Openms more often.
Check for common errors: