ci: use charmcraft from the store for weekly spread runs
Metadata
Current evaluation
Merged a CI update that switches weekly spread runs to pull charmcraft from the store instead of building a snap. This saves build time as edge sync delays are rare. Approved by two reviewers and passed all checks.
Suggested action: —
No scores available.
Issue body
The only reason this would be different is if there happened to be a commit to main that hasn't pushed to edge yet, but that would be very rare and is not worth the extra time we spend building the snap.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a CI update that switches weekly spread runs to pull charmcraft from the store instead of building a snap. This saves build time as edge sync delays are rare. Approved by two reviewers and passed all checks. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI update to use charmcraft from the store for weekly spread runs instead of building a snap. This reduces build overhead, as edge store updates are infrequent and unlikely to cause discrepancies. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a CI update to use charmcraft from the store for weekly spread runs, eliminating local snap build time. The rare edge case of unpushed main commits is accepted as a trade-off. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #388 Charmcraft pack cannot run in a CI? | charmcraft | closed | CI build failures were resolved by switching to the charmcraft classic snap on the edge channel, bypassing strict confinement restrictions. The issue was closed after the user confirmed the workaround fixed the build process. | |
| #2436 ci: check charms generated by `charmcraft init` | charmcraft | merged | Merged a dedicated CI spread test validating linting and unit tests for charms generated by charmcraft init across kubernetes and machine profiles. Approved by two reviewers, passes CI checks, and adds 25 lines of test configuration. | |
| #1950 fix: make charmcraft work with snap parallel installs | charmcraft | merged | Merged to resolve issue #1770, enabling charmcraft to operate with snap parallel installs. Approved by two reviewers, the update modifies five files with 55 additions and 15 deletions. | |
| #2518 fix: get non-store CI working on Charmcraft 2.7 | charmcraft | merged | Merged to fix non-store CI configuration for Charmcraft 2.7. Adjusted test setup and permissions without altering application functionality. Approved by two reviewers and integrated alongside a companion permissions update. | |
| #522 providers: add support to install Charmcraft snap from store (CRAFT-502) | charmcraft | merged | Merged after approval and passing CI. Adds support to install the Charmcraft snap from the Snap Store instead of injecting the host snap. Channel selection is configurable via CHARMCRAFT_INSTALL_SNAP_CHANNEL. Includes Windows test updates. |