← Back to issue list

reactive plugin: call `charm build` with `-v`

View original Github issue

Metadata

Project
charmcraft
Number
#924
Type
issue
State
closed
Author
hloeung
Labels
good first issue
Created
Updated
Closed

Current evaluation

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.

Suggested action:

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
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.
qwen3.6-35b-a3b-mtp-q6 Closed and abandoned. Maintainers triaged the request, created an internal ticket, and provided implementation guidance, but no fix was merged.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2021 feat(reactive): run charm build in verbose mode charmcraft merged Merged after two approvals and passing CI. Automatically adds the --verbose flag to charm build arguments when no log level is specified, ensuring verbose output is captured in logs. Resolves issue #924.
77%
#863 reactive_plugin: Support arguments to charm build command charmcraft merged Added reactive-charm-build-arguments to pass custom flags to the charm build command. Merged after approval and passing CI, resolving issue #809.
74%
#804 The reactive plugin is not correctly checking if `charm` failed charmcraft closed Incorrect charm return code validation in the reactive plugin was abandoned and closed without a fix. No pull requests or follow-up actions were recorded.
72%
#2194 Builds of charm using reactive plugin produces different config option charmcraft closed Closed without resolution. Maintainers acknowledged the charmcraft 3 reactive plugin incorrectly strips deprecated config options, but no fix was implemented.
72%
#809 Reactive plugin doesn't allow for other `charm` cli arguments. charmcraft closed Closed without resolution. The reactive plugin could not pass custom charm CLI arguments like --layer-index. Despite user requests for reproducible builds and binary wheel support, the feature was abandoned due to inactivity.
72%
#610 many: add reactive charm plugin charmcraft closed Closed and superseded by pull request #613. The reactive charm plugin was replaced rather than merged.
71%