Enable CI for auto build and validation for Linux Linaro

Registered by Ricardo Salveti

Discuss the list of flavours that should be tested on linux-linaro, and enable builds for each specific flavours, also making sure they are properly tested with LAVA.

Propose a vew for the CI jobs, in a way the results can be easily consumed from a simple web interface (improving/changing current CI view at LAVA).

Blueprint information

Status:
Complete
Approver:
Ricardo Salveti
Priority:
High
Drafter:
Ricardo Salveti
Direction:
Approved
Assignee:
Avik Sil
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 12.04
Started by
Ricardo Salveti
Completed by
David Zinman

Related branches

Sprints

Whiteboard

[rsalveti, Apr 2, 2012] I know most of the work is already in process, but it's good to sync and check what are the remaining pieces, and make sure they are part of this blueprint.
[aviksil, Apr 26, 2012] Synced up with zyga, he is planning to work on passing device tree data for test image, for 12.05 cycle
[dzin, Apr 27, 2012] Postponed items broken out into new blueprint.

Meta:
Headline: CI builds for all supported flavours at Linux Linaro are now enabled, and can be visualized at validation.linaro.org/lava-server/kernel-ci-views/index
Acceptance: Build jobs for all defined flavour in place at Jenkins, with test runs available at LAVA and results published at the CI view.

(?)

Work Items

Work items:
Sync with Avik, Andrey, Deepti and Ricardo to understand the remaining work to be done: DONE
Work with John and Andrey to generate a Ubuntu LEB config fragment (with all distro-related options we'd like to have at every kernel package available at our lebs): POSTPONED
Work with Andrey and Deepti to make sure all the CI builds are using the new config provided by Andrey: POSTPONED
Change the upstream deb-pkg build rule to also build and include the device tree related files: DONE
Check why the extra patch used to support kernel cross build with deb-pkg is not yet upstream, and see if that can be upstreameble (or at least contained at a topic to Andrey): DONE
Work with LAVA folks to see what would be needed to change LAVA to understand a device tree file properly: DONE

This blueprint contains Public information 
Everyone can see this information.