← Back to issue list

snapcraft trggers unnecessary pulls from unrelated file modifications

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1793471
Type
issue
State
open
Author
~aleks.bogdanov
Labels
18.10-build-caching
Created
Updated
Closed
—

Current evaluation

Unresolved proposal for .snapignore to prevent IDE and .git changes from invalidating local-source pulls and rebuilds; current code has no matching support and the issue has had no discussion.

Suggested action: keep open

Reason: The report identifies a concrete trigger—.git or IDE changes causing unnecessary source pulls and rebuilds—and the 18.10-build-caching label shows it was categorized. No matching .snapignore implementation or resolving commit was found, though the absence of an exact reproducer, proposed format, and investigation of existing ignore mechanisms leaves some uncertainty.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 10 Complexity: 55 Confidence: 78 Actionability: 58

Issue body

when working in an InteliJ IDEA based IDE or VSCode, or even simply having changes in .git directory, `snapcraft` marks stages as stale, which causes unnecessary re-pulls and re-builds, which slows down e.g npm packaging. I propose to add .snapignore file support, to allow developers to exclude files included in a snap and as such known to not invalidate packaging steps.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 10
Complexity: 55
Confidence: 78
Actionability: 58
keep open Unresolved proposal for .snapignore to prevent IDE and .git changes from invalidating local-source pulls and rebuilds; current code has no matching support and the issue has had no discussion.
stealth/space-bunny-alpha
Impact: 50
Quick Win: 10
Complexity: 65
Confidence: 88
Actionability: 55
needs triage Proposed .snapignore support to prevent IDE and .git changes from invalidating build stages and causing unnecessary source pulls and rebuilds; awaiting maintainer triage.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 16
Staleness: 95
Complexity: 60
Confidence: 60
Support Request: 10
close stale Feature request to add .snapignore support so IDE and .git changes stop marking snapcraft stages stale and triggering unnecessary re-pulls/rebuilds. Open since 2018 with label 18.10-build-caching, zero comments, no maintainer engagement for ~8 years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 45
Confidence: 90
Support Request: 15
close stale Proposes adding .snapignore support to prevent IDE and git changes from triggering unnecessary snapcraft rebuilds. Unanswered for over 7 years with no maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 40
Confidence: 90
Support Request: 15
close stale Request to add .snapignore support to prevent IDE and .git changes from triggering unnecessary snapcraft rebuilds. No maintainer activity or comments in nearly 8 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 60
Confidence: 85
Support Request: 15
close stale Proposes adding .snapignore support to prevent IDE and git changes from triggering unnecessary snapcraft re-pulls and re-builds. Issue has seen no activity in nearly 8 years.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#1583718 snapcraft command doesn't include expected changes snapcraft (launchpad) closed Local source edits now trigger refreshed pull/build steps, fixing stale packaged files; snapcraft#2167 was merged in commit 39c4c39f1.
71%