Start CI loop for TI LT kernels

Note that we'd want this to use http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git as the git URL.

Atm, ci.linaro.org is unreliable (being looked into), so we'll probably hold out adding more jobs to it until we resolve the flakiness (over the next few days). If your request is more urgent than that, please let us know.

TI is waiting on this to start an evaluation of the CI loops for their use. I'd like this done as soon as possible.

Created job "Test TI working tree". First one I've ever created. Can someone check it over.

The configuration of the job looks fine except as a good practise is not to include space in the job names.
Instead please use hypen/underscroe( "-", "_") in the job names.

Apparently, there seems to be build error, during make modules, see here
https://ci.linaro.org/jenkins/view/All%20CI/job/Test-TI-working-tree_panda-omap4plus/3/console

Can you make sure if this is not the problem with the tree ?

Thanks!!!
Deepti.

Andy tells me we should use the omap_5430evm_defconfig for both OMAP4/OMAP5 now. I have made this change to the "Test-TI-working-tree_panda-omap4plus" job.

I see you changed the name of the job. Is there a naming convention I should follow?

Note that we'd want this to use http://git.linaro.org/git-ro/landing-teams/working/ti/kernel.git as the git URL.

This doesn't seem to work, it is not up to date. From the logs:

+ git describe --match=v*
+ sed -e s/^v//
+ echo -omap_5430evm-linaro-lt-omap4+ sed -e s/_/-/g
+ export kernel_version=2.6.38.6-3130-g6a913ea-omap-5430evm-linaro-lt-omap4

git describe --match='v*' returns v2.6.38.6-3130-g6a913ea

I had Dave Long check this in his tree (about a week old):
git describe --match='v*' returns v3.3-rc7-721-g96468e8

How does this get updated?

Solved the above problem. I had a second git branch specified in the UI, and it was blank. Deleting it fixed the problem.

Solved two more problems:

1) In the Jenkins config for the SCP, there's an option to the effect of "run from master". Andy Doan pointed out that this has to be selected, the copy cannot run from the slaves. The checkbox is buried under the very last "advanced" tab in the SSH section. The check box is actually labelled "Always SSH from master".

2) Had the board type incorrectly set to panda_sd. Is there a list of correct board types and hardware pack types to use?

Noticed one more thing: I ran three jobs almost one after the other when testing. Noticed the copy of the hardware packs takes longer and longer; cause it was copying 1, then 2 then 3 hardware packs. Is there a way to force a cleanup between jobs I am missing?

On Sat, Mar 24, 2012 at 3:01 AM, Scott Bambrough
<email address hidden>wrote:

> Solved two more problems:
>
> 1) In the Jenkins config for the SCP, there's an option to the effect of
> "run from master". Andy Doan pointed out that this has to be selected,
> the copy cannot run from the slaves. The checkbox is buried under the
> very last "advanced" tab in the SSH section. The check box is actually
> labelled "Always SSH from master".
>
> 2) Had the board type incorrectly set to panda_sd. Is there a list of
> correct board types and hardware pack types to use?
>
>
The name of the boards needs to be referred to how lava names them.
We have the following valid board names

panda , beaglexm, origen, mx53loco, imx51, snowball_sd, vexpress-a9

> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/959632
>
> Title:
> Start CI loop for TI LT kernels
>
> Status in Linaro Continuous Integration:
> Triaged
>
> Bug description:
> git tree URL: git://git.linaro.org/landing-teams/working/ti/kernel.git
> git branch: tilt-tracking
>
> kernel configs: omap4_defconfig
> Build frequency: daily for now.
> root file system image: nano
> testing required: build + boot to console
> Importance: High
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-ci/+bug/959632/+subscriptions
>

--
Thanks and Regards,
Deepti

On Sat, Mar 24, 2012 at 3:02 AM, Scott Bambrough
<email address hidden>wrote:

> Noticed one more thing: I ran three jobs almost one after the other when
> testing. Noticed the copy of the hardware packs takes longer and
> longer; cause it was copying 1, then 2 then 3 hardware packs. Is there
> a way to force a cleanup between jobs I am missing?
>

Sure you can do that by checking the "Discard Old Builds", but this would
delete console output, build artifacts.
But we would not want the console output to be deleted.
This option should be used when you want to discard very old builds which
no longer keep any relevance.
So the easiest way to do it is by explicitly deleting hwpacks in your jobs
execute commands.

>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/959632
>
> Title:
> Start CI loop for TI LT kernels
>
> Status in Linaro Continuous Integration:
> Triaged
>
> Bug description:
> git tree URL: git://git.linaro.org/landing-teams/working/ti/kernel.git
> git branch: tilt-tracking
>
> kernel configs: omap4_defconfig
> Build frequency: daily for now.
> root file system image: nano
> testing required: build + boot to console
> Importance: High
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linaro-ci/+bug/959632/+subscriptions
>

--
Thanks and Regards,
Deepti

https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linaro-android-3.1_panda-omap4plus/ created. Waiting for first build.

The only difference between this new build and the test build (https://ci.linaro.org/jenkins/view/All%20CI/job/Test-TI-working-tree_panda-omap4plus) is the kernel config is set to omap4_defconfig, as requested in the bug set up rather than omap_5430evm_defconfig.

Sorry, that should have been https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linux-linaro-3.1_panda-omap4plus/

TI related jobs available under the view https://ci.linaro.org/jenkins/view/TI%20Landing%20Team%20CI%20Builds/.

Thanks!!!
Deepti.