Tags: hazelcast/hazelcast-docker
Tags
Fix `publish-rhel` [5.3.8] (#1000) The [action failed](https://github.com/hazelcast/hazelcast-docker/actions/runs/15868710042) with: > .github/scripts/publish-rhel.sh: line 32: VERSION: unbound variable The root cause was that when #968 was backported, there were _additional_ `5.3.8`-specific changes it wasn't accounting for (e.g. #799 which was _not_ backported from `5.3.z` -> `5.3.8`). Fixed by copying _wholesale_ the `5.3.z` `publish-rhel` script. [Example execution](https://github.com/hazelcast/hazelcast-docker/actions/runs/15869851560).
Fix RHEL build failure due to backport error [5.4.1] (#989) There was a [RHEL build failure](https://github.com/hazelcast/hazelcast-docker/actions/runs/15559031202) caused by an error introduced into _only_ `5.4.1` due to a backport conflict. Addressed by copying the problematic functions from the `5.4.z` script. [Example (successful) execution](https://github.com/hazelcast/hazelcast-docker/actions/runs/15564480718).
Add `warning` and `notice` support to `logging.functions.sh` (#986) Required to support hazelcast/hazelcast-mono#4484
Bump redhat/ubi9-minimal from 9.5 to 9.6 in /hazelcast-enterprise (#982)
Automate retagging process when release branches change (#955) When a release branch (`5.5.5`) is changed, the corresponding tag needs to be recreated also - which is a manual step. Instead, we can automate this process via a GitHub action that: - identifies if the `push` is to a release branch (not a maintenance branch) - checks a tag _already_ exists (the scope of this action is to retag, not to _release_ a branch) - perform the existing retagging procedure Note - this is a sticking-plaster over an imperfect process. Testing performed in a scratch-repo: - skipping: - [`main`](https://github.com/JackPGreen/backport-test/actions/runs/14894149859) - [maintenance branch](https://github.com/JackPGreen/backport-test/actions/runs/14894189254) - [retagging on `5.5.6` release branch](https://github.com/JackPGreen/backport-test/actions/runs/14894111197/job/41832985389) --------- Co-authored-by: Nishaat Rajabali <12186256+nishaatr@users.noreply.github.com>
Ensure RHEL action logs are retained on `workflow_dispatch` [DI-455] (#… …937) The action _should_ always save the pod logs as an artifact, but this only seems to be working for [`push` events](https://github.com/hazelcast/hazelcast-docker/actions/runs/14509209616/job/40704149787), but [not `workflow_dispatch`](https://github.com/hazelcast/hazelcast-docker/actions/runs/14629659767/job/41049298059). Updated to be consistent with how [we do the docker logs](https://github.com/hazelcast/hazelcast-docker/blob/5db07f32540697db42470704372d26bdff2440a7/.github/workflows/tag_image_push.yml#L220-L231). [Example `workflow_dispatch` execution](https://github.com/hazelcast/hazelcast-docker/actions/runs/14638499440). Post-merge actions: - [ ] backport _Partially addresses_: [DI-455](https://hazelcast.atlassian.net/browse/DI-455) [DI-455]: https://hazelcast.atlassian.net/browse/DI-455?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Update `README` links (#919) MC Docker and Helm chart links are incorrect.
PreviousNext