Automate the build
Automate the build so that all of the release test can be done without human input.
This is the first step in automation. The parameters are:
* A fixed OE core revision (stored as a tarball?)
* A fixed gcc-linaro release version/tarball
* Changing meta-linaro scripts
Later blueprints will cover tracking tip of all three projects.
Using LAVA plus cbuild or Jenkins as a driver, let the release manager update the SRC_URI in the git repo and spawn the release test build. Have the results end up in the LAVA dashboard.
Do all builds on tcserver01 (porter). We'll look at the cloud later.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Hope
- Priority:
- Medium
- Drafter:
- Michael Hope
- Direction:
- Approved
- Assignee:
- Ken Werner
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Michael Hope
- Completed by
- Michael Hope
Related branches
Related bugs
Sprints
Whiteboard
Meta:
Headline: N/A
Acceptance: N/A
Roadmap id: TCWG2011-
Integrate with LAVA providing we can run exactly the same scripts on a laptop for debugging.
Script the bitbake, OE meta layer, and Linaro meta layer setup.
Script the configuration including setting the release tarball URL and GCC preferred version.
Script the build and result capture, especially the log, any ICEs, and the final size
Done via cbuild.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
