Record the git ID used for the build in the log
Metadata
Current evaluation
Feature request to log the git revision used when building a part from a git source in the snapcraft build log, useful when builds fail and no manifest is available. No maintainer response or labels in ~4.5 years.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and zero maintainer comments in 1628 days. The craft-parts git_source.py code (lines 330-497) confirms the resolved commit is not explicitly logged after clone/checkout — only the git commands themselves are logged at debug level. This is a legitimate feature request that needs a maintainer to decide whether to implement it in craft-parts or snapcraft.
Impact:
35
Quick Win:
24.5
Staleness:
85
Complexity:
30
Confidence:
70
Support Request:
10
Issue body
Currently the gnome sdk build a libsecret part from git, I'm trying to figure out which revision was current at the time of the last snap build but that information doesn't seem to be available?
The build log has those information
Pulling libsecret
+ snapcraftctl pull
Cloning into '/build/gnome-3-38-2004-sdk/parts/libsecret/src'...
[07/Jan/2022:17:00:37 +0000] "CONNECT gitlab.gnome.org:443 HTTP/1.1" 200 327888 "-" "git/2.25.1"
'libgnome-games-support' has dependencies that need to be staged: libsecret
Skipping pull libsecret (already ran)
Building libsecret
+ snapcraftctl build
The snap/manifest.yaml has the information but it would be nice if the build log had it also, especially in case where the build is failing and where we don't have a manifest available
One way would be to call 'git reflog' or an equivalent after the cloning
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
24.5
Staleness:
85
Complexity:
30
Confidence:
70
Support Request:
10
|
needs triage | Feature request to log the git revision used when building a part from a git source in the snapcraft build log, useful when builds fail and no manifest is available. No maintainer response or labels in ~4.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Feature request to log the git commit ID used for building libsecret during snapcraft builds, currently only available in manifest.yaml. Issue remains open with no maintainer response or activity for over 4 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to record the git commit ID in build logs for debugging. The issue has been inactive for over 4 years with no maintainer feedback or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to log the git commit ID used for building libsecret in snapcraft logs. Currently unlabelled and inactive for over four years with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
75
Support Request:
10
|
needs triage | Request to log the git commit ID used for building dependencies directly in the build output to aid debugging failed builds. Unassessed, unlabelled, and inactive for over 4 years. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.