Push release images to OCI registry from Forgejo Actions #587

Closed
opened 2024-12-17 12:55:07 +00:00 by potyarkin · 4 comments
Member

Currently OCI images are built and pushed to DockerHub manually by release engineer:

Lines 121 to 135 in e0ce59f
# Build clean Docker image
image:
@echo "⇒ Build FrostFS S3 Gateway docker image "
@docker build \
--build-arg REPO=$(REPO) \
--build-arg VERSION=$(VERSION) \
--build-arg GOFLAGS=$(GOFLAGS) \
--rm \
-f .docker/Dockerfile \
-t $(HUB_IMAGE):$(HUB_TAG) .
# Push Docker image to the hub
image-push:
@echo "⇒ Publish image"
@docker push $(HUB_IMAGE):$(HUB_TAG)

This can and should be automated, example.

Implementation will likely switch to buildah because it works better when executed inside another container.

Currently OCI images are built and pushed to DockerHub manually by release engineer: https://git.frostfs.info/TrueCloudLab/frostfs-s3-gw/src/commit/e0ce59fd32beb9274e48adf1c52d41292ceeafd5/Makefile#L121-L135 This can and should be automated, [example](https://git.frostfs.info/TrueCloudLab/action-env/src/branch/master). Implementation will likely switch to buildah because it works better when executed inside another container.
potyarkin added the
enhancement
Infrastructure
labels 2024-12-17 12:55:07 +00:00
potyarkin self-assigned this 2024-12-17 12:55:07 +00:00
Author
Member

Status update:
Two PRs in flight: #590 should be merged first, then #588 (tagged WIP until unblocked by #590)

**Status update:** Two PRs in flight: #590 should be merged first, then #588 (tagged WIP until unblocked by #590)
Author
Member

Now that #588 is merged we can execute the full pipeline from a release tag.

Unfortunately, we can't trigger a retroactive build for existing tags because none of them contain the workflow file in their git tree. @alexvanin, would you be willing to push something like v0.32.1-pre for current master? Or should we better wait for the next tag to occur naturally?

In any case, I'll start preparing similar PRs to other repos.

Now that #588 is merged we can execute the full pipeline from a release tag. Unfortunately, we can't trigger a retroactive build for existing tags because none of them contain the workflow file in their git tree. @alexvanin, would you be willing to push something like `v0.32.1-pre` for current master? Or should we better wait for the next tag to occur naturally? In any case, I'll start preparing similar PRs to other repos.
Owner
Yay, I think we can close this issue: * https://git.frostfs.info/TrueCloudLab/frostfs-s3-gw/actions/runs/4858/jobs/0 * https://git.frostfs.info/TrueCloudLab/-/packages/container/frostfs-s3-gw/0.33.0-pre
Author
Member

I've sent similar PRs to other repos. Closing this one because it's done.

I've sent similar PRs to other repos. Closing this one because it's done.
alexvanin added this to the v0.32.1 milestone 2025-01-16 13:58:05 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-s3-gw#587
No description provided.