adoroszlai commented on PR #29: URL: https://github.com/apache/ozone-docker/pull/29#issuecomment-2359052492
Thanks @smengcl for the review. I have pushed this to branch [`ozone-1.4.0-rocky`](https://github.com/apache/ozone-docker/commits/ozone-1.4.0-rocky), and similar changes for other versions, to trigger automated image builds. The new images are published with tags `1.4.0-rocky`, ..., `1.0.0-rocky` (see https://hub.docker.com/r/apache/ozone/tags) Tested the new images with Ozone CI: https://github.com/adoroszlai/ozone/actions/runs/10923350102 However, only `xcompat` and `upgrade` acceptance tests exercise these images. Other tests use `ozone-runner` with the current Ozone code. Old Ozone smoketests may not be fully compatible with the new OS (e.g. usage of `yum install` in S3 tests in some old Ozone versions). We cannot fix that without overwriting parts of existing Ozone release in the Docker image -- I think we should avoid that. I wonder which way we should proceed: (1) keep the old images with existing content, and start using the new images with new tags, OR (2) overwrite old images with new content? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
