← Back to issue list

Support snap parallel installs

View original Github issue

Metadata

Project
craft-application
Number
#411
Type
issue
State
closed
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Parallel-installed snap injection was fixed by PR #467 (commit 77a3582b); #411 was closed as fixed, with a separate craft-providers gap noted.

Resolution: closed resolved

Reason: PR #467 was merged as commit 77a3582b to inject aliased, parallel-installed snaps into the build environment. Maintainer mr-cal closed #411 stating this craft-application portion was fixed while identifying a separate craft-providers parsing gap.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done If the application is installed as a snap, we need to be able to copy that same parallel install's revision into the provider rather than the default (un-instanced) revision. ### Why it needs to get done https://github.com/canonical/charmcraft/issues/1770

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Parallel-installed snap injection was fixed by PR #467 (commit 77a3582b); #411 was closed as fixed, with a separate craft-providers gap noted.
stealth/space-bunny-alpha — closed resolved Parallel-installed snap propagation is fixed in craft-application (#411); maintainers closed this as resolved, while noting a separate craft-providers name-parsing gap.
qwen/qwen3.6-35b-a3b — — Closed. The initial fix was merged into craft-application, but full parallel snap support requires a follow-up update in craft-providers to correctly parse snap names with underscores.
qwen/qwen3.6-35b-a3b — — Closed. Resolved in craft-application, but superseded by a pending craft-providers fix. The provider update will split snap names on underscores to correctly inject parallel revisions into build environments.

Update history

No update history recorded yet.

Related work

Related issues

Issue Project State Summary Similarity
#5085 fix: allow parallel installations of signed snapcraft snaps snapcraft merged Merged PR #5085 fixed parallel installation of signed Snapcraft snaps, resolving #4683 and #4927; #5087 backported the fix to hotfix/7.5.
79%
#4088 providers: allow parallel installations when not running as a snap snapcraft merged Merged PR #4088 as commit cb6f3857e, adding a snap-runtime check so non-snap installations can run in parallel.
75%
#4683 Cannot use parallel installations of snapcraft if a non-aliased version is not installed snapcraft closed Fixed by merged PR #5085 (main) and backported via #5087 to hotfix/7.5 (7.5.7); craft-providers now inject the aliased snapcraft snap correctly. Upstream bug tracked in craft-application#411.
75%
#5087 fix: allow parallel installations of signed snapcraft snaps (7.5) snapcraft merged Merged into hotfix/7.5 and released in 7.5.7, fixing parallel installs of signed or store-installed Snapcraft; resolves #4683 and #4927.
74%
#4084 providers: inject current snapcraft snap into instances snapcraft merged Merged PR #4084 as commit b852f9ac8, injecting the current Snapcraft snap into provider instances so parallel-installed instances can build core22 snaps.
73%
#4927 Parallel installation of snapcraft not passed to LXD instance snapcraft closed Parallel-installed (signed) snapcraft was not passed to the LXD build instance. Fixed by merged PR #5085 and backported via #5087 to hotfix/7.5, shipped in 7.5.7; also tracks upstream craft-application#411.
73%
#1770 charmcraft snap doesn't work with snap parallel installs charmcraft closed Fixed by merged PR canonical/charmcraft#1950 (commit 2399ddf8), which enabled Charmcraft to work with parallel-installed snaps and added regression coverage.
72%
#5509 Odd behaviour with parallel snapcraft installs snapcraft closed Closed as unreproducible: maintainer could not reproduce parallel-install failure after experimental.parallel-instances was re-set; reporter pointed to a snapd bug, filed as LP bug #2111940.
71%