Update omero-zarr-pixel-buffer to 0.6.0-rc1 #459
Conversation
|
Tested with pilot-idr0173. Looks good to me. But we should deploy that on idr-testing and do a proper stress test with accessing images directly from s3 (vs goofys mount). What is the best strategy there? As @khaledk2 is using it for search engine related dev. Only run idr-omero / idr-readonly playbooks to apply change or completely re-spawn idr-testing? /cc @sbesson . |
| become: yes | ||
| get_url: | ||
| url: "{{ glencoe_artifactory_baseurl }}/{{ item.group }}/{{ item.name }}/{{ item.version }}/{{ item.name }}-{{ item.version }}.jar" | ||
| dest: "{{ omero_ms_image_region_folder }}/lib/{{ item.name }}.jar" |
There was a problem hiding this comment.
As mentioned at the weekly IDR meeting, the JARs under the micro-service lib folder are versioned so the existing omero-zarr-pixel-buffer JAR might need to be removed as well to ensure the correct version is picked up at deployment time.
Alternatively https://github.com/ome/omero-ms-image-region could be updated to consume the 0.6.0-rc1 version of omero-zarr-pixel-buffer and cut a release candidate that could be used in these playbooks
There was a problem hiding this comment.
Thanks. Yes, I think the alternative approach makes actually more sense than this PR. I'll remove the last commit again.
|
Replaced by #460. |
2 participants
See title.