Port All Kernel CI Jobs to use central bzr code

[asac, Sep 1, 2011]: example comment; use these to report on key achievements, roadblocks, exception process step updates etc.
[deepti, Sep 14, 2011]: Linux next repository is not available on kernel.org anymore and there is no other alternative location where it can be found. Hence the build of linux-next is blocked.
[asac, Sep 14, 2011]: looks good. maybe tweak headline to refer to which trees and defconfigs we build instead of the plain number (yes, that was coming from me :)).
[deepti, Sep15, 2011]: The arm-soc for-next lava-test executions is blocked for the exynos4 defconfig on origen board as there are no origen boards available in validation lab.
[james-w, Sep 16, 2011] Beagle testing in LAVA is blocked by bug 850770
[deepti, Sep21, 2011] Bug 850770 is fixed now
[deepti, Sep21 2011] The linux-next tree is available @ git://github.com/sfrothwell/linux-next.git and the linux-next builds are in progress now
[deepti, Sep28 2011] The work items related to the exynos4 defconfig lava execution is BLOCKED because there is no origen board available in the validation lab to test the kernel build. Since this is a lack of infrastructure and are blocked currently due to unavailability of the board we can move this to the new BP to be achieved for the next milestone or when the hardware is assumed to be available for testing.
[deepti, Sep28 2011] The Work item for verifying the linux(linus) is set to POSTPONE because of the bug Bug #859473: "Illegal instruction" hints when run stream and posixtestsuite. The investigations for the same are still under progress and hence the item would need to be postponed. The linux(linus) builds are failing during the LAVA test execution side only after the Sep23 builds and hence these issues seems to be induced after sep22 in the linux(linus) tree. Here is the link to one of the successful test execution before it started failing due to the above bug http://validation.linaro.org/lava-server/dashboard/streams/anonymous/ci-linux/bundles/c1e64b9186ca3e55de11744c063798d2771e023e/. Hence I think the bug can be postponed to be resolved for the 11.10 release and we can change this BP to be implemented otherwise.
[asac, Oct 6, 2011]: confirmed implemented.

Headline: All 12 Linaro Kernel CI builds have been successfully ported to a better codebase that allows larger scale deployment and better team maintenance of centralized code. These include: 4 trees (linaro linux 3.0 , arm-soc, linux (master), linux-next and arm-soc) using 3 defconfigs (omap2 for beagle, omap2 for panda and exynos4 for origen)

Acceptance: All Linaro CI Builds are using the bzr code snippet introduced by the jenkins-scripts-in-bzr blueprints; After doing this, no regression are observed at the kernel build, package and hwpack creation; job submission. job execution side.

Work items:
collect all defconfig and trees that kernel WG wants to track : DONE
Note down success/fail state (and note down error log snippets for fails) for all CI stage (build, hwpack submit, scheduler run, lava tests) so you can later verify that the behavior of jobs has not been changed by this migration: DONE
Add new job for the linaro linux using omap2 defconfig to work on Panda board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linaro linux using omap2 defconfig to work on Beagle board, make use of the bzr code snippet for the jobs : DONE
Add new job for the linaro linux using exynos4 defconfig to work on origen board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux (linus) using omap2 defconfig to work on Panda board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux (linus) using omap2 defconfig to work on Beagle board, make use of the bzr code snippet for the jobs : DONE
Add new job for the linux (linus) using exynos4 defconfig to work on origen board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux arm-soc using omap2 defconfig to work on Panda board, make use of the bzr code snippet for the jobs : DONE
Add new job for the linux arm-soc using omap2 defconfig to work on Beagle board, make use of the bzr code snippet for the jobs : DONE
Add new job for the linux arm-soc using exynos4 defconfig to work on origen board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux for-next using omap2 defconfig to work on Panda board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux for-next using omap2 defconfig to work on Beagle board, make use of the bzr code snippet for the jobs: DONE
Add new job for the linux for-next using exynos4 defconfig to work on origen board, make use of the bzr code snippet for the jobs: DONE
Validate the build for linaro linux using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro linux using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro linux using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: DONE
Validate the build for linux (linus) using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linux (linus) using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linux (linus) using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: DONE
Validate the build for linaro arm-soc using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro arm-soc using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro arm-soc using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: DONE
Validate the build for linaro for-next using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro for-next using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the build for linaro for-next using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: DONE
Validate the lava test execution for linaro linux using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linaro linux using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linaro linux using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: BLOCKED
Validate the lava test execution for linux arm-soc using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linux arm-soc using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linux arm-soc using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: BLOCKED
Validate the lava test execution for linux (linus) using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : POSTPONED
Validate the lava test execution for linux (linus)using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : POSTPONED
Validate the lava test execution for linux (linus) using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: BLOCKED
Validate the lava test execution for linux for-next using omap2 defconfig to work on Panda board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linux for-next using omap2 defconfig to work on Beagle board , verify there are no regression caused by using the bzr snippet : DONE
Validate the lava test execution for linux for-next using exynos4 defconfig to work on origen board , verify there are no regression caused by using the bzr snippet: BLOCKED
[asac] Validate Acceptance criteria is met, set BP state to implemented and get team PM or TL to sign off that they cross checked delivery by dropping a comment to whiteboard: DONE