← Back to issue list

Send build-started timestamp to store

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1835403
Type
issue
State
closed
Author
~cjwatson
Labels
—
Created
Updated
Closed

Current evaluation

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.

Resolution: closed resolved

Reason: PR #2650 was merged as commit b31299e39, adding built_at to the snap-push parameters sourced from the manifest's snapcraft-started-at key; the code and unit tests (tests/unit/store/test_client.py::test_notify_upload_built_at) are present in the tree. The reporter closed the Launchpad bug pointing at that PR.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Following up on bug 1806658, "snapcraft push" should send the recorded timestamp when the build was started to the store, in order that it can be stored and compared with other builds when using the new "push with release intent" feature. It just needs to add a built_at entry to the snap-push parameters, with the value set to an ISO 8601 timestamp.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved 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.
stealth/space-bunny-alpha — closed resolved Implemented via PR #2650, merged as commit b31299e39 ("store: send snapcraft-started-at in push requests"), which adds the recorded build-start timestamp to snap push parameters as built_at in ISO 8601 form.
stealth/space-bunny-alpha — closed resolved Build-start timestamp forwarding was implemented in commit b31299e39; later PR #4261 (c96290b) fixed uploads to read it from snap/manifest.yaml.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The feature to send a build-started timestamp via snapcraft push was never added and remains unimplemented.
qwen/qwen3.6-35b-a3b — — Abandoned. The request to send a build-started timestamp to the store via snapcraft push was closed without implementation or submitted pull requests.

Update history

Date Change
created

Related work

  • Likely Fixed By: canonical/snapcraft#2650 (confidence 95%)

    Merged PR implementing built_at in push requests; cited by the reporter in the closing comment

  • Related To: snapcraft (launchpad)#1806658 (confidence 60%)

    Original bug this issue follows up on (push with release intent)

Related issues

Issue Project State Summary Similarity
#2650 store: send snapcraft-started-at in push requests snapcraft merged Merged #2650 as b31299e39, sending snapcraft-started-at in Store push requests so release requests can be ordered by build start time.
84%
#1806658 Record timestamp when build was started snapcraft (launchpad) closed Build-start timestamp support was added to snap/manifest.yaml by snapcore/snapcraft PR #2559, merged as commit 1c283cc30.
77%
#2559 manifest: expose snapcraft-started-at snapcraft merged Merged PR #2559 via commit 1c283cc30, exposing snapcraft-started-at in manifest.yaml for ordering Snap Store processing.
73%