commands/build: output charms to cwd when using provider (CRAFT-359)
Metadata
Current evaluation
Merged in canonical/charmcraft#438 via f73def1c, fixing provider builds to output charms in the current project directory and retrieve builds targeted outside it.
Resolution: closed resolved
Reason: PR #438 was approved and merged in commit f73def1c, with implementation commit 7b2e529f. It makes in-project provider builds output to the current working directory and uses the container home directory for retrievable outputs targeting other directories.
Evaluated by: mr-cal-bot
No scores available.
Issue body
If building in project directory, use the project path as the working
directory. The output charms will be placed in the correct directory
without needing retrieval. If outputing to a directory other than the
charm project directory, we need to output the charm outside the
project directory and can retrieve it when complete. Use the home
directory for this output inside the container.
Signed-off-by: Chris Patterson <chris.patterson@canonical.com>
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/charmcraft#438 via f73def1c, fixing provider builds to output charms in the current project directory and retrieve builds targeted outside it. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in charmcraft#438: provider builds now place charms in the cwd, using a home-directory output path when the build targets a directory outside the project. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged after two approvals and passing CI. The change updates build commands to output charms directly to the current working directory when using a provider, simplifying file placement and retrieval. Modified five files with 177 additions and five deletions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Updates the build command to output charms to the current working directory when using a provider, simplifying file placement and retrieval. Resolves CRAFT-359. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #514 `charmcraft build` silently omits files called out in `charmcraft.yaml` if executed from an external directory | charmcraft | closed | Fixed by merged PR canonical/charmcraft#525 (merge commit 0d78f540), which runs the parts lifecycle from the project directory so relative globbed paths resolve during external builds. | |
| #541 charm_builder: build dependencies locally (CRAFT-537) | charmcraft | merged | Merged in charmcraft#541 via 0d14d8a2: charm_builder now builds dependencies locally in a persistent staging venv, avoiding binary dependencies and repeat rebuilds during repacks. | |
| #402 providers: introduce charmcraft base configuration (CRAFT-261) | charmcraft | merged | Merged in charmcraft#402 via 481525e5, adding craft-providers and a Charmcraft buildd configuration that installs pip, setuptools, and injects the host Charmcraft snap. |