-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello everyone.
With the help of Paul Larson we now have a Launch Control PPA. Currently it does not have the most interesting package (dashboard) but we're slowly getting there.
The ppa is at: https://edge.launchpad.net/~linaro-infrastructure/+archive/launch-control
I have created a daily build of the first package: python-linaro-json. This package contains the JSON utilities that I've developed for launch control. As soon as the dust settles out and I'm comfortable with packaging I'll release and upload a non-daily build. (Q: what is the best way do to that with launchpad?)
Next in the queue for that PPA is a python package for working with dashboard bundle files (extracted from the current dashboard code base). I hope that those two packages can make it to natty eventually and help the nice folks in Ubuntu QA to produce test results not as unstructured text files but as bundle files. Hopefully this will allow them to store those files as they currently do and later on decide to either push them to a dashboard instance of their choice or convert them to launchpad subunit format (yes! it's _should_ be possible to convert all data to subunit) once that is ready for production.
Feedback welcome :-)
Best regards ZK
On Thu, 04 Nov 2010 16:01:09 +0100, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello everyone.
With the help of Paul Larson we now have a Launch Control PPA. Currently it does not have the most interesting package (dashboard) but we're slowly getting there.
The ppa is at: https://edge.launchpad.net/~linaro-infrastructure/+archive/launch-control
I have created a daily build of the first package: python-linaro-json. This package contains the JSON utilities that I've developed for launch control. As soon as the dust settles out and I'm comfortable with packaging I'll release and upload a non-daily build. (Q: what is the best way do to that with launchpad?)
I'm not quite sure what you're asking here, but I think one good practice is to have a 'dailies' ppa (e.g. ~linaro-infrastructure/+archive/launch-control-dailies) and a separate releases ppa (which might be named like the current one) that you upload releases to manually.
Cheers, mwh
On Fri, 05 Nov 2010 10:33:40 +1300, Michael Hudson michael.hudson@canonical.com wrote:
separate releases ppa (which might be named like the current one) that you upload releases to manually.
Or trigger recipe builds in to manually.
Thanks,
James
On Thu, 04 Nov 2010 17:55:46 -0400, James Westby james.westby@canonical.com wrote:
On Fri, 05 Nov 2010 10:33:40 +1300, Michael Hudson michael.hudson@canonical.com wrote:
separate releases ppa (which might be named like the current one) that you upload releases to manually.
Or trigger recipe builds in to manually.
I was thinking that for releases, you'd want a non-native package. But maybe that's just being picky :-)
Cheers, mwh