[docs] how to run charmcraft as part of a CI?
Metadata
Current evaluation
Closed as addressed: canonical/craft-actions#31 (commit 91513c1) added Charmcraft setup and pack actions, and a maintainer confirmed CI packing and publishing were now supported.
Resolution: closed resolved
Reason: canonical/craft-actions#31 merged as commit 91513c1, adding official Charmcraft setup and pack actions. Before closing, sergiusens noted that actions and methods for CI packing and publishing were now available.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Hello,
We use GitHub actions to pack our charms, deploy in a test environment to run some final tests, and publish it to latest/edge.
but with the recent changes, our CI is broken we are struggling to build the charms in there. Could you provide an example of how to:
- pack the charms as part of CI
- publish to a channel automatically
Thanks!
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Closed as addressed: canonical/craft-actions#31 (commit 91513c1) added Charmcraft setup and pack actions, and a maintainer confirmed CI packing and publishing were now supported. | |
| stealth/space-bunny-alpha | — | closed resolved | Closed as addressed: maintainers said official actions and methods now covered CI packing and publishing. canonical/craft-actions#31 added Charmcraft setup and pack actions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requested CI documentation for packing and publishing charms. Maintainers initially proposed creating dedicated GitHub Actions. Closed after official GitHub Actions and documentation were implemented, resolving the integration request. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. Official GitHub Actions and documentation now provide CI integration guidance for packing and publishing charms, resolving the request. | |
| qwen/qwen3.6-35b-a3b | — | — | CI automation request for charmcraft was closed after maintainers confirmed GitHub Actions and publishing workflows now exist. The suggested tools were implemented, resolving the broken pipeline. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as resolved. Maintainers initially proposed creating dedicated documentation and GitHub Actions. Later confirmed that existing GitHub Actions now support automated charm packing and publishing, making the request obsolete. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/craft-actions#31
(confidence 96%)
Merged PR adding official Charmcraft setup and pack actions for CI workflows.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #49 ci: test the charmcraft actions in more places | craft-actions | merged | Merged PR #49 in commit a8e5310, expanding Charmcraft action CI coverage across more Ubuntu architectures, channels, and pinned-revision runs. | |
| #31 feat: charmcraft actions | craft-actions | merged | Merged in commit 91513c1, adding charmcraft/setup to install Charmcraft and LXD and charmcraft/pack to run setup and package charms. | |
| #1851 How-to doc for charmcraft test | charmcraft | open | Documentation request from a maintainer to write a how-to guide for the undocumented `charmcraft test` command. Open with no labels, assignee, or maintainer triage; only an automated Jira-sync bot comment (CRAFT-3957). | |
| #132 test: update charm integration test | craft-actions | merged | Merged in canonical/craft-actions#132 (54f7849), updating the charm pack integration test to use another simple charm after the previous Juju fixture was removed. | |
| #105 feat: charmcraft/pack with typescript | craft-actions | merged | Merged PR canonical/craft-actions#105 rewrote charmcraft/pack in TypeScript to match the other pack actions (CRAFT-5205); approved by 2 reviewers, all CI (setup/pack/test-action-code, run-rockcraft-pack-action) passing, +20585/-138 across 14 files. | |
| #249 `charmcraft build` will let you build a charm that won't deploy | charmcraft | closed | Closed by facundobatista as a duplicate, tracking all build-time sanity checks (incl. config.yaml/actions.yaml validity) in the umbrella issue charmcraft#27; later implemented by merged PR #556 (a585aec6). | |
| #203 GitHub Actions template in charmcraft | charmcraft | closed | Rejected generating a GitHub Actions CI file from charmcraft init; on 2023-10-09, a maintainer confirmed “we decided not to do this,” favoring documentation. | |
| #2518 fix: get non-store CI working on Charmcraft 2.7 | charmcraft | merged | Merged #2518, correcting Charmcraft 2.7 non-store CI setup without application changes; companion permissions update: canonical/canonical-repo-automation#537. |