Record timestamp when build was started

Bug #1806658 reported by Colin Watson on 2018-12-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Wishlist
Sergio Schvezov

Bug Description

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.

tags: added: 19.04
Changed in snapcraft:
status: New → Triaged
importance: Undecided → Wishlist
assignee: nobody → Sergio Schvezov (sergiusens)
milestone: none → 3.1
Changed in snapcraft:
milestone: 3.1 → none
tags: added: 19.04-blue
Changed in snapcraft:
milestone: none → 3.5
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: Triaged → In Progress
Sergio Schvezov (sergiusens) wrote :

Let's create a new task for supporting the store api side (added candy for snapcraft).

Changed in snapcraft:
status: In Progress → Fix Committed
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers