reactive plugin: call `charm build` with `-v`
Metadata
Current evaluation
Fixed by merged PR #2021 (commit 7129d57e): the reactive plugin adds --verbose to charm build unless an explicit verbosity or log level is supplied.
Resolution: closed resolved
Reason: PR #2021 was merged and explicitly fixes #924. Commit 7129d57e makes charm build verbose by default while respecting user-provided verbosity and log-level arguments.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Hi,
Trying to debug a build/pack issue, https://github.com/canonical/charmcraft/issues/923, I'm trying to compare output from a failed and previously successful one:
https://launchpadlibrarian.net/631398435/buildlog_charm_ubuntu_focal_amd64_haw-test_BUILDING.txt.gz
https://launchpadlibrarian.net/632662139/buildlog_charm_ubuntu_focal_amd64_testing_BUILDING.txt.gz
Unfortunately, there isn't much output from the `charm build` step when a charm is successfully built so it makes it quite hard:
```
:: proof: I: all charms should provide at least one thing
:: charm tool execution command=['charm', 'proof']
:: charm tool execution WARNING: returncode=100
:: charm tool execution command=['charm', 'build', '-o', PosixPath('/home/buildd/haw-test/build/parts/charm/build')]
:: charm tool execution WARNING: returncode=100
Running step STAGE for part 'charm'
Execute action
Running step PRIME for part 'charm'
Execute action
Check result: language [attribute] unknown (The charm is written with Python.; see more at https://juju.is/docs/sdk/charmcraft-analyzers-and-linters#heading--language).
Check result: framework [attribute] unknown (None; see more at https://juju.is/docs/sdk/charmcraft-analyzers-and-linters#heading--framework).
Creating the package itself
Created 'haw-test_ubuntu-20.04-amd64.charm'.
```
Any chance we can call `charm build` with `-v` / `--verbose` when `charmcraft pack` is called with `--verbosity trace`?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2021 (commit 7129d57e): the reactive plugin adds --verbose to charm build unless an explicit verbosity or log level is supplied. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2021 (commit 7129d57e) makes reactive builds pass --verbose to charm build unless an explicit verbosity or log level is provided. | |
| stealth/space-bunny-alpha | — | closed resolved | Reactive builds now invoke charm verbosely for verbose Craft CLI output; fixed by merged PR #2021 (commit 7129d57e). | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2021 (commit 7129d57e): the reactive plugin now runs charm build in verbose mode while respecting explicit verbosity arguments. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #2021, commit 7129d57e, which added verbose `charm build` execution to the reactive plugin. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after triage and internal ticket creation. Implementation guidance was provided to pass verbose flags to charm calls when verbosity is trace or debug. No fix or pull request was merged. | |
| qwen/qwen3.6-35b-a3b | — | — | Triaged and an internal ticket was created. Implementation guidance was provided, but the issue remains closed without a confirmed fix or merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Triaged and tracked via internal ticket CRAFT-3424. Implementation guidance was provided to conditionally pass verbose flags to charm commands, but the feature remains unaddressed. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2021
(confidence 100%)
Merged PR implementing the requested verbose charm build behavior and explicitly linked as fixing #924.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2021 feat(reactive): run charm build in verbose mode | charmcraft | merged | Merged PR #2021 (commit 7129d57e): the reactive plugin now auto-appends --verbose to `charm build` unless the user set a log level, fixing #924. | |
| #863 reactive_plugin: Support arguments to charm build command | charmcraft | merged | Merged in charmcraft PR #863 via commit a5f200b1, adding reactive-charm-build-arguments so the reactive plugin can pass options to charm build; fixes #809. | |
| #809 Reactive plugin doesn't allow for other `charm` cli arguments. | charmcraft | closed | Resolved by merged PR #863 (merge commit a5f200b1): reactive builds can now pass charm build options such as --layer-index via reactive-charm-build-arguments. | |
| #804 The reactive plugin is not correctly checking if `charm` failed | charmcraft | closed | Fixed in merged PR #869 (commit 7046f61d), adding negative-return-code handling and return-code logging for both charm invocations. | |
| #2194 Builds of charm using reactive plugin produces different config option | charmcraft | closed | Fixed by merged PR #2245 (commit aa28f0dc): reactive-generated config.yaml is no longer overwritten, preserving options such as snapd_refresh. | |
| #610 many: add reactive charm plugin | charmcraft | closed | PR #610 (charm-tools-based reactive plugin) was closed unmerged on 2021-12-14 by sergiusens in favor of #613, which reimplemented the plugin on the charm tool (CRAFT-699) and merged as 32c8650a. | |
| #869 reactive_plugin: Properly check returncode from charm tool | charmcraft | merged | Merged in commit 7046f61d (merge ecce30c6), fixing reactive_plugin to validate the charm tool return code and always log it; resolves #804. | |
| #866 reactive_plugin: Fix charm tools version validation | charmcraft | merged | Merged PR #866 as commit 35ec089e (merge c40c30c2), replacing brittle charm-tools version parsing with JSON output and fixing #864. | |
| #613 plugins: reactive using charm tool (CRAFT-699) | charmcraft | merged | Merged PR #613 (merge commit 32c8650a, branch charm-tools-plugin) added the reactive charm plugin built on the charm tool, implementing CRAFT-699; 11 files, +499/-8. |