-
Notifications
You must be signed in to change notification settings - Fork 14
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
Deploy OMERO.server 5.6.9 on pilot IDR instance #380
Conversation
This should now be deployed onto |
The last commit has been deployed on Looking into recreating |
This is now deployed on |
Thanks @sbesson . I wonder, is there actually a reliable way to check it, e.g. |
From OMERO.py 5.13 moving forward, |
👍 The omero-server-jar apparently still is 5.6.5, but maybe that's fine: |
This should contain the minimal set of changes to deploy the recently released OMERO.server 5.6.7 alongside OMEZarrReader 0.3.1. |
Definitely |
Upgraded, if you want to give it a try |
1 similar comment
Upgraded, if you want to give it a try |
Thank you, I have idr0011 re-import in progress now. |
this was a success, I would say that @dgault 's fix is working on idr0011, thanks |
Now deployed on |
@sbesson Just discussed with @dgault the possibility of including ome/ZarrReader#41, which hopefully will allow us to import NGFF without chunks? |
The Ansible infrastructure downloads the JAR from a public location like the OME Artifactory. This is not straightforward to adapt as this work is currently at the Pull Request level. If you are interested in testing the artifact, it should be more direct and more efficient to deploy it manually on the pilot of your choice. Simply replace the JARs under |
The last state of this PR was deployed on |
As discussed earlier today, merging this for the initial deployment of |
Not intended for production usage yet (this will require a wider discussion and planning aroudn the upgrade of the OMERO.server as well as Bio-Formats)