[#1591] Build and host OCI images on our own infra #1591
No reviewers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1591
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "potyarkin/frostfs-node:feature/oci-image-pipeline"
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?
Similar to TrueCloudLab/frostfs-s3-gw#587 this PR introduces a CI pipeline that builds Docker images and pushes them to our selfhosted registry.
Discussion points:
Should we execute
make images
for every commit in every PR? I do that in other repos (reasons explained here), but frostfs-node has the largest CI suite and is the most frequently executed one. Feels wrong to make it larger (and possibly increase wait times).For now I've disabled image builds on PRs because as it turns out that would be the slowest CI job in frostfs-node. //cc @fyrchik
d49cbb8faa
tofeadcbbc5b
WIP: [#1591] Build and host OCI images on our own infrato [#1591] Build and host OCI images on our own infrafeadcbbc5b
toae23fdc80a