Provide Snapshot Manifests for Each Build
With so many builds available, it is a must to provide with each build manifests specifying from what source tree it was built, as well as exact revisions used to build, to allow complete reproducibility.
For every Android build I would like to automatically generate a snapshot manifest. After syncing the default manifest this manifest would be created. This snapshot manifest would be listed on the build page (listed on https:/
Blueprint information
- Status:
- Complete
- Approver:
- Zach Pfeffer
- Priority:
- High
- Drafter:
- Paul Sokolovsky
- Direction:
- Approved
- Assignee:
- Paul Sokolovsky
- Definition:
- Approved
- Series goal:
- Accepted for 2011q2
- Implementation:
- Implemented
- Milestone target:
- 11.06
- Started by
- Paul Sokolovsky
- Completed by
- Paul Sokolovsky
Related branches
Related bugs
Bug #793474: Create/export "release" (pinned revs) manifest for Android builds | Fix Released |
Sprints
Whiteboard
Headline: For each Android platform build, a source and release manifests are now provided together with download tarballs, allowing to easily look up components used in particular build and 100% reproduce it elsewhere.
[asac 2011, Jul 10]: Definition: Drafting -> thats wrong; a project must not make any progress during drafting in theory. Something with almost all items done must be approved at least; tentatively approving: Please ensure a good headline Lands as first line in blueprint summary that can be used to summarize this feature in market compatible achievement of this spec.
Use repo manifest -r to produce revision-pinned manifest. Caveat: it should be done using the original, not mirrored, manifest.
Work Items
Work items:
Export out/*.xml as build artfacts: DONE
Export input manifest as source-
Make and export revision-pinned manifest as pinned-
Tweak naming and source manifest availability as needed: DONE