chore: Update CI to use charmcraftcache - #174
Merged
Merged
Conversation
dariofaccin
approved these changes
May 25, 2026
🤖 Backport labels populatedLabels to this pull request were added automatically by the When the PR is merged, backport PRs according to the labels will be automatically created. To skip the backport creation, remove any unneeded labels before merging the PR. |
🤖 Backport labels populatedLabels to this pull request were added automatically by the When the PR is merged, backport PRs according to the labels will be automatically created. To skip the backport creation, remove any unneeded labels before merging the PR. |
MattiaSarti
approved these changes
May 27, 2026
The ci.yaml reusable workflow's build and release jobs request 'actions: read' (needed by charmcraftcache), but the caller job in release.yaml did not grant this permission, causing a startup failure. Add permissions: actions: read to the ci-tests job.
|
Successfully created backport PR for |
mvlassis
added a commit
that referenced
this pull request
May 28, 2026
* chore: Update CI to use charmcraftcache * Add back on_pull_request.yaml for backport label population * ci: always collect juju status * fix: Grant actions: read to ci-tests job in release workflow The ci.yaml reusable workflow's build and release jobs request 'actions: read' (needed by charmcraftcache), but the caller job in release.yaml did not grant this permission, causing a startup failure. Add permissions: actions: read to the ci-tests job. * fix: Grant contents: read to ci-tests job in release workflow (cherry picked from commit d15f0a8) Co-authored-by: Manos Vlassis <57320708+mvlassis@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Summary
This PR updates the CI to utilize charmcraftcache, by using actions from data-platform-workflows. The ci.yaml is very similar to the structure we have in our multi-repo charms, for example see https://github.com/canonical/knative-operators/blob/main/.github/workflows/ci.yaml.
Base issue: canonical/bundle-kubeflow#1429