Push release images to OCI registry from Forgejo Actions #587
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#587
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently OCI images are built and pushed to DockerHub manually by release engineer:
# 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.
Status update:
Two PRs in flight: #590 should be merged first, then #588 (tagged WIP until unblocked by #590)
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.
Yay, I think we can close this issue:
I've sent similar PRs to other repos. Closing this one because it's done.