On Sat, Apr 14, 2012 at 8:13 PM, Alexander Sack asac@linaro.org wrote:

On Sat, Apr 14, 2012 at 4:29 PM, Alexander Sack asac@linaro.org wrote:

...

On Sat, Apr 14, 2012 at 2:41 PM, Christian Robottom Reis <kiko@linaro.org

...

wrote:

...

I think there's a standard link missing from CI pages such as

https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linux-linaro-3.1_pand...

to the output directory at

http://snapshots.linaro.org/kernel-hwpack/TI-working-tree/TI-working-tree_ti...

Is that right? For some background, we got this inquiry on IRC:

<slado> rsalveti: are there prebuilt linaro kernels for ubuntu that have hdmi fixes described in bug 919378?

I went to look at the bug and then figured the latest CI build might have the code included. Indeed it does:

https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linux-linaro-3.1_pand...

However, I couldn't find a way of getting the binary generated from the build, and had to actually use my rapidly deteriorating memory to get to snapshots.linaro.org, where I had to also go through a confusing set of directories to get to what I think is the actual build.

We don't export the .deb package itself. What we export is the complete hwpack for such "pure" upstream CI jobs: http://ci.linaro.org/kernel_hwpack/ (in this case: http://ci.linaro.org/kernel_hwpack/TI-working-tree/TI-working-tree_tilt-linu...) ... can you find that build there?

(I don't know about the retention policy on that place atm.)

And yes, this location is definitely not the real one: consider it an unofficial place until we have figured how we want to generally map the ci output into a reasonable snapshots hierarchy for ubuntu rootfs, hwpacks and hwpacks coming out of our mainline CI job types.

Yes having hwpacks on the ci* was a solution taken up when there was no other place to store the hwpacks.

BTW, this is already happening on the ubuntu rootfs/hwpack side: we are moving our rootfs production and hwpack production for our Ubuntu LEB to ci.linaro.org and as part of that I am sure we are inventing such a hierarchy mapping as we speak. I can imagine that whatever we do there for the official LEB hwpacks should be easily adaptable for our pure mainline focused CI jobs.

We are moving to snapshots.linaro.org and the hierarchy is evolving as

moving to s.l.o was done recently.

-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog

On 14 April 2012 18:02, Christian Robottom Reis kiko@canonical.com wrote:

On Sat, Apr 14, 2012 at 04:29:26PM +0200, Alexander Sack wrote:

...

...

http://snapshots.linaro.org/kernel-hwpack/TI-working-tree/TI-working-tree_ti...

Is that right? For some background, we got this inquiry on IRC:

[...]

...

We don't export the .deb package itself. What we export is the complete hwpack for such "pure" upstream CI jobs: http://ci.linaro.org/kernel_hwpack/(in this case: http://ci.linaro.org/kernel_hwpack/TI-working-tree/TI-working-tree_tilt-linu...) ... can you find that build there?

Note the link I provided above ;-) The immediate question is why isn't this linked to from the CI page?

Publishing from CI to snapshots has been done recently. In the long term, ci.linaro.org will have a frontend like we do for android-build to make it easier to have various information (LAVA tests result, etc...). In the meantime, it's up to the CI job maintainer to update the job description and provide useful information like a link to snapshots (now added).

On Sat, Apr 14, 2012 at 06:59:53PM +0300, Fathi Boudra wrote:

On 14 April 2012 18:02, Christian Robottom Reis kiko@canonical.com wrote:

...

On Sat, Apr 14, 2012 at 04:29:26PM +0200, Alexander Sack wrote:

...

...

http://snapshots.linaro.org/kernel-hwpack/TI-working-tree/TI-working-tree_ti...

Is that right? For some background, we got this inquiry on IRC:

[...]

...

We don't export the .deb package itself. What we export is the complete hwpack for such "pure" upstream CI jobs: http://ci.linaro.org/kernel_hwpack/(in this case: http://ci.linaro.org/kernel_hwpack/TI-working-tree/TI-working-tree_tilt-linu...) ... can you find that build there?

Note the link I provided above ;-) The immediate question is why isn't this linked to from the CI page?

Publishing from CI to snapshots has been done recently. In the long term, ci.linaro.org will have a frontend like we do for android-build to make it easier to have various information (LAVA tests result, etc...). In the meantime, it's up to the CI job maintainer to update the job description and provide useful information like a link to snapshots (now added).

Can't we somehow populate that automatically for all standard-ish kernel CI jobs?

Hello Alexander,

Thanks a lot for helping with ci queries in my absence.

On Sat, Apr 14, 2012 at 7:59 PM, Alexander Sack asac@linaro.org wrote:

On Sat, Apr 14, 2012 at 2:41 PM, Christian Robottom Reis kiko@linaro.orgwrote:

...

I think there's a standard link missing from CI pages such as

https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linux-linaro-3.1_pand...

to the output directory at

http://snapshots.linaro.org/kernel-hwpack/TI-working-tree/TI-working-tree_ti...

Is that right? For some background, we got this inquiry on IRC:

<slado> rsalveti: are there prebuilt linaro kernels for ubuntu that have hdmi fixes described in bug 919378?

I went to look at the bug and then figured the latest CI build might have the code included. Indeed it does:

https://ci.linaro.org/jenkins/job/TI-working-tree_tilt-linux-linaro-3.1_pand...

However, I couldn't find a way of getting the binary generated from the build, and had to actually use my rapidly deteriorating memory to get to snapshots.linaro.org, where I had to also go through a confusing set of directories to get to what I think is the actual build.

We don't export the .deb package itself. What we export is the complete hwpack for such "pure" upstream CI jobs: http://ci.linaro.org/kernel_hwpack/ (in this case: http://ci.linaro.org/kernel_hwpack/TI-working-tree/TI-working-tree_tilt-linu...) ... can you find that build there?

No the hwpack would be absent on the ci.linaro.org because the job does not copy the hwpack to ci.linaro.org anymore.

(I don't know about the retention policy on that place atm.)

The hwpacks are not deleted as of now, but we are coming up with a retention policy for obvious disk space reasons.

Short term I see two things that would be really important:

1. a really easy to find link to the LAVA job submitted

This has been planned since quite sometime, but has always been down in the list since something else always took more priority. I will work on this at the earliest. Raised a bug to track this https://bugs.launchpad.net/linaro-ci/+bug/982836.

2. good display of the meta information of the build/lava job submitted

which would include the link to the hwpack (as that is what is passed to LAVA as one artifact) as well as information about the git source and commit (and we could make a link to gitweb out of it when visualizing this job).

Ultimately, we want to have a way to have all meta-information for all

steps of a CI job nicely visualized (e.g. automerging, auto buiding, validating, etc.).

Do you mean we should have all this information as part of each job that

is run on ci.linaro.org as meta information listed above is already available on validation.linaro.org.

Anyway, we should start thinking about visualizing CI jobs and make them navigatable soon. I don't want to see us making the mistake again to wait for a nice UI until all the plumming is done. That approach just leave lots of value on the floor! I am sure Andy, Ricardo and Danilo are already thinking about this though :).

-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog

---

linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev