Enabling Google binaries in LAVA builds

Registered by Tony Mansson

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:
milestone icon 2012.02
Started by
Paul Larson
Completed by
Paul Larson

Sprints

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://code.launchpad.net/~linaro-infrastructure/linaro-android-build-tools/trunk so it should be running in android jobs from now on

Meta:
Headline: A new action android_install_binaries can be used to apply binary drivers for builds that need them
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://people.linaro.org/~vishalbhoj/install-binaries-4.0.3.sh for hints about how to deploy the binaries: DONE
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

This blueprint contains Public information 
Everyone can see this information.