[docs] how to run charmcraft as part of a CI?
Metadata
Current evaluation
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as resolved. Maintainers confirmed GitHub Actions and documentation for CI workflows now exist, addressing the request to pack and publish charms automatically. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #203 GitHub Actions template in charmcraft | charmcraft | closed | Rejected. The team decided against embedding a GitHub Actions CI template in charmcraft init to avoid polluting new projects with provider-specific files. Documentation was suggested as the preferred alternative. | |
| #31 feat: charmcraft actions | craft-actions | merged | Merged changes adding two GitHub Actions: charmcraft/setup installs Charmcraft and LXD, while charmcraft/pack builds charms. Approved by two reviewers with passing CI checks, the update adds 299 lines across six files to streamline workflows. | |
| #49 ci: test the charmcraft actions in more places | craft-actions | merged | Merged after two approvals and passing all CI checks. The update expands the continuous integration pipeline to test charmcraft actions across additional build environments, modifying a single file with minor configuration changes. |