Can't easily unambiguously determine which build gets released

Bug #993986 reported by Zach Pfeffer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android
Fix Released
Wishlist
Unassigned

Bug Description

If you look at:

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob-12.04-release/#build=4

...you currently have to

git clone git://android.git.linaro.org/platform/manifest.git
cd manifest/
git checkout linaro-android-12.04-release

...then look at the log to get the list of commits that were used to release. But there's no direct link to say which exact commit was used in

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob-12.04-release/#build=4

To be sure, you'd need to check the pinned-manifest.xml from the source build against the source-manifest.xml of the release build. If the manifests line up your good. Yo may have to check a few of the builds on the release branch to confirm, which sucks.

Fathi Boudra (fboudra)
Changed in linaro-android:
assignee: nobody → Fathi Boudra (fboudra)
milestone: none → 12.05
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Zach Pfeffer (pfefferz) wrote :

Putting in backlog for evaluation

Changed in linaro-android:
milestone: 12.05 → backlog
Fathi Boudra (fboudra)
Changed in linaro-android:
milestone: backlog → none
Fathi Boudra (fboudra)
Changed in linaro-android:
assignee: Fathi Boudra (fboudra) → nobody
Revision history for this message
Milosz Wasilewski (mwasilew) wrote :

pinned-manifest.xml is produced for each build now. Closing.

Changed in linaro-android:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.