← Back to issue list

ci: only require CHARMCRAFT_AUTH for store spread

View original Github issue

Metadata

Project
charmcraft
Number
#1075
Type
pull request
State
merged
Author
sergiusens
Labels
—
Created
Updated
Closed

Current evaluation

Merged CI workflow updates that restrict CHARMCRAFT_AUTH requirements to store tests only. General tests run independently, while store tests are limited to Ubuntu 22.04, marked manual, and reduced in repetition. Three files modified.

Suggested action: —

No scores available.

Issue body

Separate the logic into two in the Github Actions Workflow to always run spread for the general tests, while limiting store tests to having CHARMCRAFT_AUTH in GHA Secrets. The required environment has been moved to the store suite in spread. Also making it run less test repetition by limiting them to Ubuntu 22.04 and avoiding it being run in the main testing phase for spread by marking them as manual.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Merged CI workflow updates that restrict CHARMCRAFT_AUTH requirements to store tests only. General tests run independently, while store tests are limited to Ubuntu 22.04, marked manual, and reduced in repetition. Three files modified.
qwen3.6-35b-a3b-mtp-q6 — — Merged CI updates restricting CHARMCRAFT_AUTH to store spread tests only. General spread tests run unconditionally. Store tests moved to a manual suite, limited to Ubuntu 22.04, and reduced in repetition to optimize the pipeline.
qwen3.6-35b-a3b-mtp-q6 — — Merged. CI workflow now separates general spread tests from store tests. Store tests require CHARMCRAFT_AUTH, run only on Ubuntu 22.04, and are marked manual to reduce repetition and skip the main spread phase.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
72%