-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Build OCI image for each supported Erlang major version #3143
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
Conversation
Command `make push` pushes an image tagged VERSION where VERSION in our oci.yaml corresponds to the Git commit SHA. `make push IMAGE_TAG=<additional tag>` pushes two images: 1. tag VERSION 2. tag <additional tag> (branch name in oci.yaml) Before this commit, the same image got pushed 3 times as seen in https://github.com/rabbitmq/rabbitmq-server/pull/3137/checks?check_run_id=2885095969: docker push ***/rabbitmq:46f6d81ad06a9b0b34a791a7fd078c45d66e1196 docker push ***/rabbitmq:46f6d81ad06a9b0b34a791a7fd078c45d66e1196 docker push ***/rabbitmq:46f6d81ad06a9b0b34a791a7fd078c45d66e1196 docker push ***/rabbitmq:faster-binding-recovery After this commit we expect the follwing pushes: docker push ***/rabbitmq:46f6d81ad06a9b0b34a791a7fd078c45d66e1196 docker push ***/rabbitmq:faster-binding-recovery
1. with minimum required Erlang 2. with maximum supported Erlang
Hm maybe instead of min/max we could have max, max-1 and max-2. We currently support only 23 and 24 but I think that is unusual and we typically support up to 3 major versions? |
as suggested by @lhoguin. Right now (June 2021), we support only Erlang 23 and 24. In future, we might support 3 Erlang major versions.
This is useful when iterating on and testing the oci.yaml.
Good idea @lhoguin. I pushed a commit implementing that. |
We support two series and when we can, three for a 3 month long transition period. Still, N and N-1 is a good naming pattern to follow 👍 |
Can someone backport to |
rabbitmq/rabbitmq-server#3143 enables us to run system tests against latest rabbitmq-server master ensuring we're compatible with our Erlang supported versions as documented in https://www.rabbitmq.com/which-erlang.html
Build OCI image for each supported Erlang major version (cherry picked from commit f46a267)
Build OCI image for each supported Erlang major version (cherry picked from commit f46a267)
Backported to |
It includes the Erlang/OTP version since #3143 Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
It includes the Erlang/OTP version since #3143 Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
As requested by @gerhard in #2777 (comment), auto-build OCI images for both Erlang 23 and 24.
Therefore, this job will create two images
Each image will have two tags
For example, for Git commit SHA
1111aaa
and branch namemain
, the following two docker images and four tags will be pushed to DockerHub:1111aaa-otp-min
(image 1)main-otp-min
(image 1)1111aaa-otp-max
(image 2)main-otp-max
(image 2)(While we could have used tag
main-otp-24.0.2
instead ofmain-otp-max
, I prefer the latter option since we can use that stable tag when specifying the RabbitMQ image in pipelines or LREs.)Needs to be backported to
v3.9.x
andv3.8.x
.