← Back to issue list

multiple parts with same git repo makes build checkout out redundant repos

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1608932
Type
issue
State
open
Author
~adam-stokes
Labels
conjure sources
Created
Updated
Closed
—

Current evaluation

Confirmed, low-priority build inefficiency: parts using the same Git URL each clone the tree. No fix or newer reproduction is documented.

Suggested action: keep open

Reason: Maintainer ~elopio confirmed the redundant checkouts, marked the report confirmed and low priority, and noted that sharing sources would require lifecycle and link support. The exact snapcraft.yaml reproducer makes the inefficiency clear, but the implementation tradeoff remains unresolved and there is no evidence of a fix or grounds for age-based closure.

Evaluated by: mr-cal-bot

Impact: 31 Quick Win: 5 Complexity: 73 Confidence: 90 Actionability: 61

Issue body

snapcraft.yaml: name: conjure-up version: 2.0.0.7 summary: Package runtime for conjure-up spells description: > This package provides conjure-up, an interface to installing spells that provide the user with an end to end walkthrough experience for installing and using big software. confinement: strict apps: conjure-up: command: conjure-up python3: command: python3 shell: command: bash parts: conjure: plugin: python3 source: https://github.com/ubuntu/conjure-up.git source-type: git requirements: parts/conjure/src/requirements.txt stage-packages: - juju - bsdtar - coreutils - lxd-client - lxd - jq - charm-tools - charm - python3-glanceclient - python3-neutronclient - python3-openstackclient conjure-configs: plugin: copy source: https://github.com/ubuntu/conjure-up.git source-type: git files: etc/conjure-up.conf: etc/conjure-up.conf share/keyword-definitions.yaml: usr/share/conjure-up/keyword-definitions.yaml share/hooklib: usr/share/conjure-up/hooklib Running snapcraft build will result in each part having their own copy of the git tree even though they are identical. This is on snapcraft 2.13.1

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 31
Quick Win: 5
Complexity: 73
Confidence: 90
Actionability: 61
keep open Confirmed, low-priority build inefficiency: parts using the same Git URL each clone the tree. No fix or newer reproduction is documented.
stealth/space-bunny-alpha
Impact: 30
Quick Win: 5
Complexity: 70
Confidence: 92
Actionability: 58
keep open Identical git sources are checked out separately for every part; maintainers confirmed the inefficiency as low priority and said sharing would require lifecycle and link support.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 9
Complexity: 50
Confidence: 60
Actionability: 60
keep open Snapcraft clones the same git repository redundantly for multiple parts referencing it, wasting build time and disk space. Issue is open with no maintainer response.
qwen/qwen3.8-27b
Impact: 25
Quick Win: 15
Staleness: 95
Complexity: 40
Confidence: 60
Support Request: 10
close stale snapcraft 2.13.1: parts sharing the same git source each get their own checkout instead of a shared cache. No maintainer activity for ~9.5 years; the 2.x series is EOL and modern craft-parts-based snapcraft uses a shared source cache.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 45
Confidence: 85
Support Request: 10
close stale Snapcraft checks out identical git repositories redundantly across multiple parts, causing unnecessary build overhead. The report is nearly a decade old with no maintainer interaction or updates.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 30
Confidence: 85
Support Request: 10
close stale Reports redundant git checkouts when multiple snapcraft parts reference the same repository. Open for over nine years with zero maintainer interaction. The referenced version is deprecated and the build system rewritten, making this report irrelevant.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 25
Confidence: 90
Support Request: 10
close stale Report of redundant git checkouts when multiple snapcraft parts reference the same repository. Issue is over 9 years old with no maintainer response or activity.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.