Linaro Android Build Tools

Merge lp://qastaging/~mwhudson/linaro-android-build-tools/more-job-info-in-artifacts into lp://qastaging/linaro-android-build-tools

more-job-info-in-artifacts
Merge into trunk

Proposed by Michael Hudson-Doyle on 2011-08-24

Status:	Merged
Merged at revision:	301
Proposed branch:	lp://qastaging/~mwhudson/linaro-android-build-tools/more-job-info-in-artifacts
Merge into:	lp://qastaging/linaro-android-build-tools
Diff against target:	26 lines (+7/-1) 2 files modified build-scripts/post-build-lava.py (+6/-0) control/update-artifacts.mangle (+1/-1)
To merge this branch:	bzr merge lp://qastaging/~mwhudson/linaro-android-build-tools/more-job-info-in-artifacts
Related bugs:	Link a bug report

Reviewer	Review Type	Date Requested	Status
Linaro Infrastructure		2011-08-24	Pending
Review via email: mp+72667@code.qastaging.launchpad.net

Description of the change

Hi,

This branch changes ./build-scripts/post-build-lava.py to create an artifact with machine readable information about the job that was submitted to lava. I have a linaro-android-frontend branch and lava changes that use this to display a nice table in the build page about the results.

I should admit that I haven't tested this at all. Hope it works! :-)

Cheers,
mwh

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-08-24:

Immediate issue:

> }, open('out/lava-job-info'))

should be open(..., 'w').

We have sandbox support now, so can test it before deploying.

lp://qastaging/~mwhudson/linaro-android-build-tools/more-job-info-in-artifacts updated on 2011-08-24

302. By Michael Hudson-Doyle on 2011-08-24: open file for writing

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2011-08-24:

On Wed, 24 Aug 2011 07:22:34 -0000, Paul Sokolovsky <email address hidden> wrote:
> Immediate issue:
>
> > }, open('out/lava-job-info'))
>
> should be open(..., 'w').

Haha, thanks. Fixed.

> We have sandbox support now, so can test it before deploying.

Good point. I'll talk to you about this at some point :-) Is it easy to
deploy a custom frontend branch too?

Cheers,
mwh

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-08-24:

On Wed, 24 Aug 2011 09:12:24 -0000
Michael Hudson-Doyle <email address hidden> wrote:

[]
> Good point. I'll talk to you about this at some point :-) Is it easy
> to deploy a custom frontend branch too?

Well, it's possible. Sandbox creation script deploys from trunk, so
just need to login to a box and re-deploy needed branch after that.

>
> Cheers,
> mwh
>

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

lp://qastaging/~mwhudson/linaro-android-build-tools/more-job-info-in-artifacts updated on 2011-08-26

303. By Michael Hudson-Doyle on 2011-08-26: merge trunk

Revision history for this message

Michael Hudson-Doyle (mwhudson) wrote on 2011-08-26:

Hi, I think this branch is ready for deployment now. I tested it by creating a job:

https://android-build.linaro.org/builds/~mwhudson/test-lava-integration

and changing it in jenkins to use the build-tools branch. It seems to have worked. I deployed the needed scheduler and dashboard changes early, so all that remains is to land this, run the mangle script to update the artifact list and do a deploy of linaro-android-frontend, and all should be happiness :-)

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-08-29:

Creating a sandbox to test (my unrelated changes too).