Allow to "inject" tarballs with host toolchains, etc. into builds

Registered by Paul Sokolovsky

For an Android platform build, allow to specify list of tarballs to be downloaded and unpacked into well-known place on build slave. These tarballs may contain e.g. adhoc host toolchains to be used to build particular components. NOTE: This is NOT about putting proprietary target drivers into target images.

Blueprint information

Status:
Complete
Approver:
Данило Шеган
Priority:
Medium
Drafter:
Paul Sokolovsky
Direction:
Approved
Assignee:
James Tunnicliffe
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2012.02
Started by
David Zinman
Completed by
David Zinman

Sprints

Whiteboard

[pfalcon 2011-11-28]
The idea is to have build config var like:

EXTERNAL_TARBALL="http://foo.com/ball1.tar.gz;http://foo.com/ball2.tar.bz2"

which would download specified tarballs, then expand them to well-known, stable location. It may download and expand into Jenkins workspace (which has enough space for it), but path to the workspace is dependent on job name, so it's not "stable". So, I would suggest additionally create /tmp/<tarball_basename> symlinks.

[dzin Jan 27, 2012] Moving to next cycle

Meta:
Headline:
Android Build service now allows developers to use arbitrary tools (e.g. toolchains of different versions) in a build.

Acceptance:
It is possible to use 2 different toolchains in a build.

(?)

Work Items

Work items:
Finalize option name: DONE
Finalize stable path scheme: DONE
Implement: DONE
Test: DONE
Document: DONE

This blueprint contains Public information 
Everyone can see this information.