Enabling Google binaries in LAVA builds
AOSP contain binaries behind EULA click-through that needs to be used in LAVA. This BP is about enabling that.
It should be possible to either programmatically accept the EULA or to arrange so that the information that the EULA is already accepted is persistent.
Blueprint information
- Status:
- Complete
- Approver:
- Paul Larson
- Priority:
- Essential
- Drafter:
- Paul Larson
- Direction:
- Approved
- Assignee:
- Paul Larson
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
- Implemented
- Milestone target:
- 2012.02
- Started by
- Paul Larson
- Completed by
- Paul Larson
Whiteboard
[pwlars 2012.02.14] This is now deployed on the server and I've tested it there. Sent an email to see about getting it added to the necessary android runs after coming out of ci
[pwlars 2012.02.22] Paul S from infrastructure got this merged in https:/
Meta:
Headline: A new action android_
Acceptance: A job can be submitted that calls an action to apply binary drivers for android
Work Items
Work items:
Look at script on http://
Build our own binary tarball to pull from for jobs run in LAVA: DONE
Add a dispatcher action to let the user choose to deploy these binaries: DONE
Figure out how to prove they work, and test locally: DONE
Make sure the extra action gets added to lava template for selected android builds: DONE