Hey
I'd like to propose moving our Hudson stuff to Launchpad hosted
branches. This would be useful to:
* share our stuff, perhaps in common repos across hudson instances (see
below)
* have everybody follow best practices of keeping as much as possible
under a VCS
* help move/factor hudson instances (e.g. factor two instances in one,
move from home server or cloud to Linaro/Canonical IS datacenter)
I see two ways to approach this problem:
* each team owns a hudson instance, and stores its config and scripts
in the team's namespace; this doesn't encourage factoring instances
together though
* we create a virtual team of people caring for hudson stuff, e.g.
~linaro-hudson-hackers, and we put branches below that
We will need to keep the hudson configs private because they might hold
private data like hudson's secret key or the userdb, perhaps with some
private bzr branches? or can we move to openid and avoid storing
the other secret keys already?
The branch with build script would of course be public.
We could have some cron committing each config (changed from the web
UI) hourly, and pushing it to LP, and a cron pulling the latest version
of the scripts hourly (or a special hudson job which does either).
For scripts, we'd have to agree on some conventions such as namespaces
for Android build scripts (e.g. android-list-changes), hudson job
definitions (e.g. job-build-u-boot, or job-build-android).
Two things which might slow us down if we want to proceed:
* Hudson might get renamed due to the situation with Oracle
* getting private branches
* we need some kind of Launchpad accounts for the hudson instances to
commit stuff
Paul, James, Michael Hudson, (Alexander?), and anybody, what are your
thoughts?
Cheers,
--
Loïc Minier
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
