-
Notifications
You must be signed in to change notification settings - Fork 1
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
Build and Publish Rocks workflows #2
Closed
addyess
wants to merge
10
commits into
main
from
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
Closed
Build and Publish Rocks workflows #2
addyess
wants to merge
10
commits into
main
from
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 18, 2024 19:33
6041fdc
to
b33a6c8
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 18, 2024 19:34
b33a6c8
to
91b693c
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
16 times, most recently
from
January 21, 2024 23:31
a39c407
to
5e6c36c
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 22, 2024 00:06
5e6c36c
to
da88c85
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
5 times, most recently
from
January 22, 2024 19:05
8ac132b
to
882f9d4
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 22, 2024 19:23
882f9d4
to
1fb5726
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 22, 2024 19:56
7fb19c8
to
9fc47a3
Compare
addyess
commented
Jan 22, 2024
.github/workflows/build_rock.yaml
Outdated
working-directory: ${{ inputs.working-directory }} | ||
build-rocks: | ||
name: Build rocks | ||
uses: addyess/operator-workflows/.github/workflows/build_rocks.yaml@KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cannot merge until this is first merged
canonical/operator-workflows#243
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 24, 2024 03:36
ba2db7d
to
3cf0245
Compare
addyess
force-pushed
the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
from
January 24, 2024 14:05
3cf0245
to
ef24197
Compare
addyess
deleted the
KU-52-reuse-gh-actions-from-canonical-to-build-amd-64-rocks-and-push-to-ghcr
branch
January 26, 2024 03:26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚧 Do not merge until this is first merged 🚧
canonical/operator-workflows#243
Using the
operator-workflows
actionbuilds and push the rock to a repository
packages
Determine the next available patch tag for the image (eg
-ck2
)Create a multiarch manifest for the images pushed with this new tag
How
each rock in the repo produces a list of metadata for the built images.
The action scripts
Assemble Image Tags
find the next best patch version matching the base version in the rockcraft.yaml'sversion
fieldFor instance, if the rockcraft
cilium:1.0.0
is built, each platform with produce an imagecilium:<filehash-sum>-<arch>
image.This actions searches all the image tags starting with
canonical/cilium:1.0.0-
. If there are none, the sum of all those tags is 0 indicating this is the 0th patch rev. If the sum is 20, this is the 20th patch rev.The multi-arch manifest created will be
canonical:cilium:1.0.0-ck0
in which the referenced images will be annotated for their correct architecture.