Record the git ID used for the build in the log
Metadata
Current evaluation
Build logs omit the resolved Git commit for branch-based part sources, making failed-build reproduction harder; no maintainer triage or implementation is recorded.
Suggested action: needs triage
Reason: The body provides a concrete log excerpt, desired outcome, and suggested solution, but the issue has no labels, maintainer comments, or implementation discussion. Current craft-parts code resolves HEAD into source details for unconstrained git sources but does not visibly log the resulting commit.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
23
Complexity:
28
Confidence:
88
Actionability:
76
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
23
Complexity:
28
Confidence:
88
Actionability:
76
|
needs triage | Build logs omit the resolved Git commit for branch-based part sources, making failed-build reproduction harder; no maintainer triage or implementation is recorded. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
20
Complexity:
35
Confidence:
89
Actionability:
80
|
needs triage | Request to log the resolved Git revision for Git-sourced parts in build output, so failed builds can be diagnosed without snap/manifest.yaml; remains untriaged. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
24
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. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.