← Back to issue list

Record timestamp when build was started

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1806658
Type
issue
State
closed
Author
~cjwatson
Labels
19.04 19.04-blue
Created
Updated
Closed

Current evaluation

Build-start timestamp support was added to snap/manifest.yaml by snapcore/snapcraft PR #2559, merged as commit 1c283cc30.

Resolution: closed resolved

Reason: A maintainer linked snapcore/snapcraft PR #2559 as the implementation. Commit 1c283cc30, titled "manifest: expose snapcraft-started-at (#2559)", added the RFC3339 build-start metadata requested here.

Evaluated by: mr-cal-bot

No scores available.

Issue body

To make the process of automatically releasing snaps to the store from Launchpad (and presumably other similar automated systems) more reliable, we need to keep track of the time when each snap build started. This will allow the store to ensure that older builds don't accidentally supersede newer builds, even if the push-and-release of an older build was retried after an earlier failure. As a prerequisite for this, snapcraft should record the timestamp when the build was started somewhere in snap/manifest.yaml, as an RFC3339-formatted timestamp. This timestamp should also be overrideable in some way (e.g. an environment variable) so that automated build systems that wrap snapcraft can record the start of their overall build job rather than just when snapcraft started.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Build-start timestamp support was added to snap/manifest.yaml by snapcore/snapcraft PR #2559, merged as commit 1c283cc30.
stealth/space-bunny-alpha — closed resolved Feature landed: snapcraft now records an RFC3339 build start timestamp in snap/manifest.yaml as snapcraft-started-at, overridable via environment. Implemented by PR #2559, merged as commit 1c283cc30.
stealth/space-bunny-alpha — closed stale Closed as abandoned without a recorded resolution; matching Launchpad #1806658 also closed without comments after prolonged inactivity.
qwen/qwen3.6-35b-a3b — — Closed without comments or resolution. The request to record an overridable RFC3339 build start timestamp in snap/manifest.yaml was abandoned.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The feature request to record the build start timestamp in snap/manifest.yaml as an RFC3339 value, overridable via environment variable, was abandoned.
qwen/qwen3.6-35b-a3b — — Closed without comments. Feature request to record build start timestamps in snap/manifest.yaml was abandoned.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The feature request to record the build start timestamp in snap/manifest.yaml was abandoned, as no resolution or merge occurred.
qwen3.6-35b-a3b-mtp-q6 — — Closed without implementation or comments. The feature to record build start timestamps in snap/manifest.yaml was not addressed or merged. The request appears abandoned or superseded.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#2559 (confidence 99%)

    The linked PR was merged as commit 1c283cc30 and adds snapcraft-started-at metadata.

Related issues

Issue Project State Summary Similarity
#1835403 Send build-started timestamp to store snapcraft (launchpad) closed Implemented by canonical/snapcraft PR #2650 ("store: send snapcraft-started-at in push requests"), merged as commit b31299e39. 'snapcraft push' now reads snapcraft-started-at from the manifest and sends it as built_at in the notify-upload request.
77%