Track and Build the Tip Toolchain

Registered by Zach Pfeffer on 2011-08-29

Today we wait nearly the entire month to integrate a new toolchain. This can cause a great deal of risk and stress at the end of the cycle when we attempt to integrate the new toolchain. To derisk and destress the end of cycle crunch, it would be useful to simply build and track tip.

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
High
Drafter:
Paul Sokolovsky
Direction:
Approved
Assignee:
Paul Sokolovsky
Definition:
Pending Approval
Series goal:
Accepted for 2011q2
Implementation:
Implemented
Milestone target:
milestone icon 11.10
Started by
Paul Sokolovsky on 2011-10-08
Completed by
Paul Sokolovsky on 2011-10-17

Related branches

Sprints

Whiteboard

Notes:
[pfalcon 2011-10-04] Proposed implementation:
Add build config param (TBD) which will produce toolchain tarball without time/ver-stamps. Then, latest good build will be accessible with "permalink" like https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-bzr/lastSuccessfulBuild/artifact/build/out/android-toolchain-eabi-4.6-daily-linux-x86.tar.bz2
[pfalcon 2011-10-05]
Ok, config param is TOOLCHAIN_TARBALL, which allows to specify any (static) tarball name, which is the most flexible way it seems.
Done: https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-4.6-bzr/lastSuccessfulBuild/artifact/build/out/android-toolchain-eabi-4.6-daily-linux-x86.tar.bz2
I guess it makes no sense to apply that to 4.5 toolchain build - it's not used in such config, and keeping timestamped builds is a boon.
[pfefferz]
It will be useful to be able to keep local workaround patches on our git to ensure that the toolchain can be used while more perminate changes are sent to the toolchain group.
[pfalcon] ^^^ - ??

Headline:
Linaro's Android distribution can now base builds off a tip toolchain build

Acceptance:
A reference to the tip toolchain build that we can reference in daily builds and a way to map that reference to the particular build that its referring too.

(?)

Work Items

Work items:
Produce a stable toolchain URL: DONE
Describe how to find out actual toolchain version/build used for particular platform build: DONE
Consider ways to automate used toolchain build mapping: DONE
Experiment with Jenkins fingerprinting for automated toolchain build mapping: DONE
Setup Jenkins fingerprinting for automated toolchain build mapping: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.