← Back to issue list

Add GitHub workflow that builds and tests the fetch-operator charm

View original Github issue

Metadata

Project
fetch-service
Number
#225
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Maintainer task (lengau) to add a CI workflow that builds the fetch-operator charm and runs `charmcraft test` with charmcraft.yaml pinned to the current fetch-service commit; still unimplemented.

Suggested action: needs triage

Reason: The request is still unimplemented: `.github/workflows/` contains only tests.yaml, tics.yaml, cla-check.yaml, sync-to-launchpad.yaml and security-scan.yaml, grep for 'fetch-operator' returns no matches, and `git log --grep fetch-operator` finds no commits. The issue has no labels, no assignee and only an autogenerated Jira-sync bot comment, so no maintainer triage is recorded. However the scope is ambiguous — "adjust the charmcraft.yaml file to use the specific commit we're building from" does not say which key to patch or how fetch-service is consumed by fetch-operator, which will need clarification before implementation.

Evaluated by: mr-cal-bot

Impact: 42 Quick Win: 11 Complexity: 55 Confidence: 82 Actionability: 58

Issue body

### What needs to get done Add a GitHub workflow that builds [fetch-operator](https://github.com/canonical/fetch-operator) and tests it using `charmcraft test`. The workflow should adjust the charmcraft.yaml file to use the specific commit we're building from ### Why it needs to get done The fetch operator is one of the two biggest use cases of the fetch service.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 42
Quick Win: 11
Complexity: 55
Confidence: 82
Actionability: 58
needs triage Maintainer task (lengau) to add a CI workflow that builds the fetch-operator charm and runs `charmcraft test` with charmcraft.yaml pinned to the current fetch-service commit; still unimplemented.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 12
Complexity: 52
Confidence: 84
Actionability: 68
needs triage Maintainer task (2022): add a GitHub workflow that builds canonical/fetch-operator with a pinned commit in charmcraft.yaml and runs `charmcraft test`. Still no such workflow exists in .github/workflows (only tests/tics/security/cla/launchpad).
stealth/space-bunny-alpha
Impact: 52
Quick Win: 26
Complexity: 33
Confidence: 80
Actionability: 76
needs triage Requested fetch-operator charm CI remains unimplemented and untriaged: build the pinned commit, update charmcraft.yaml, and run charmcraft test.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 28
Staleness: 85
Complexity: 30
Confidence: 65
Support Request: 20
close stale Feature request to add GitHub workflow for building and testing the fetch-operator charm using charmcraft test. Issue is 715 days old with no maintainer engagement or labels.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#203 Add fetch-operator charmcraft tests fetch-service closed Closed unimplemented with no resolving PR or commit; the sole comment created internal ticket CRAFT-3304, and fetch-operator Charmcraft tests were not added.
73%