Moving build configurations into git
paul.sokolovsky at linaro.org
Thu Dec 22 13:13:41 UTC 2011
On Mon, 19 Dec 2011 11:37:27 -0600
Zach Pfeffer <zach.pfeffer at linaro.org> wrote:
> Right now we have many build configurations. For example,
Do you mean "many", or "long", or "changing too often"?
> I'd like to move this into a git in 12.01.
> Does this seem feasible?
Well, let's remember why we have build configuration process as it is
now - to have it both flexible and extensible, and yet easy for any
Linaro engineer (not only from Android team, but also from Validation,
Kernel, etc.) to start using and use it. So, if we'll add "config from
git" support, we'll still need to keep current "easy edit by hand"
approach. Then, we'll have to approaches, with usual issues - more
stuff to maintain, more stuff for folks to remember, harder to use/more
chance of errors.
So, what are specific factors to call for adding that "config from
git"? If it's access control, I'd like to remind that we have special
"linaro-android-official-builders" group, only its members can edit
official builds. By limiting that group to 2-3 people for each release
process, there can be better change tracking. And only of keeping
explicit change log for (some) build configs is crucially required
feature, than IMHO it's worth to complicate process with additional
Otherwise, technically, I don't see big problems with implementing
that (at least in the simplest way), but that depends on more detailed
spec for how it should look/work.
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
More information about the linaro-android