-
Notifications
You must be signed in to change notification settings - Fork 13
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
Design questions #1
Comments
Re omero-test-daemon-c7-docker, it would make sense to re-use it from a historical perspective, considering the former as version I would vote for keeping the What are the pros and cons of running |
I will make sense to re-use if https://github.com/openmicroscopy/omero-test-daemon-c7-docker if possible for the name I agree with @sbesson we should keep omero- as a prefix. |
I've renamed this repo to omero-test-infra and the following 4 PRs are green:
I was hoping to extract the PyTest command and make use of ome/openmicroscopy#5585 but it's too difficult to consume the devspace OMERO.server build. (Here we need a decoupled My proposal would be to merge all 4 of those, perform a release where appropriate, and then consider this version |
Few decisions that have been made over scattered conversations (open for veto):
|
app-build already exists. it is currently used to run the tests |
I had to make various modifications to use test-infra for figure and iviewer |
Changes to have iviewer and figure work with test-infra |
Current implementation assumes that the scripts to test are in a folder |
Changes have been made in #3 to handle scripts not directly under |
Consider more configuration options for apps e.g. |
omero-test-infra
?.omeroci/test-data
be run in a client docker or the server docker?travis-folds
everywhere?TODO:
Dockerfile
in lib-docker (et al) configuration for multiple build systems (mvn, gradle)test-data
tosetup
The text was updated successfully, but these errors were encountered: