Continuous Integration of Android Builds
Many Android distributions use a continuous integration loop to release code. This flow starts with patch submission to a Gerrit server. After the patch has been reviewed it gets automatically merged with other orthogonal changes into a test build. The test build is programmed onto a target and validation is run against the target. If the change passes each gate it is accepted into the build.
Work items listed here superceed similar work items listed on:
https:/
https:/
https:/
Blueprint information
- Status:
- Not started
- Approver:
- Zach Pfeffer
- Priority:
- Undefined
- Drafter:
- Zach Pfeffer
- Direction:
- Needs approval
- Assignee:
- Zach Pfeffer
- Definition:
- New
- Series goal:
- Accepted for 2011q2
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This topic is in support of the following goals
P1.1, Android LEB, Essential, Provide a Linaro optimised build of Android, Android
As an Android developer I would like to use Gerrit to manage review of my changes.
linaro-
As an Android developer I would like my change to be automatically merged into a test build.
linaro-
As an Android developer I would like the test build to be automatically deployed to all targets.
linaro-
As an Android developer I would like the test build to be tested on every target.
linaro-
As an Android developer I would like my change to be included in all mainlines that it was tested on.
linaro-
As a lawyer I would like to ensure that every change is legally acceptable.
linaro-
As an Android upstreamer I would like an easy way to automatically track my change to its upstream destination after it has been merged into the mainline.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
