[Buildroot] Changes in the Buildroot autobuilders

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Mon Jun 17 07:49:58 UTC 2013

Dear Maxime Ripard,

On Mon, 17 Jun 2013 09:45:35 +0200, Maxime Ripard wrote:

> > Ok. This will require a little bit of work, because until now, the
> > autobuild.buildroot.org machine, which sends the daily e-mails, was not
> > using the Buildroot source code at all to do its job. So either the
> > slave build machines will have to submit the list of maintainers of the
> > failing package as part of the tarball they submit to
> > autobuild.buildroot.org, or autobuild.b.o will have to look at the
> > Buildroot source code to find the maintainers of the failing package.
> > 
> > Either way, it will not be immediate to implement.
> Maybe having a make pkg-maintainers target that would output the list of
> mails for a package maintainer would be a more reasonable thing to do.

Of course, if the solution of <pkg>_MAINTAINERS proposed by Yann is
adopted, we should have a corresponding "make show-<pkg>-maintainers"
target to display the maintainers for a given package. However...

> That would allow the autobuilders to not have some knowledge of the
> buildroot source code, while we remain free to change the "maintainer
> implementation" at any point in time.

... that doesn't solve the entire problem. For now, the slaves (doing
the builds) do not know what is the reason of the build failure. The
analysis of the log file to find out which package failed is currently
done only on the autobuild.b.o machine. But this machine doesn't have
access to the corresponding Buildroot source code to execute the "make
show-<pkg>-maintainers". So, we would have to change the logic of what
is done on the build slaves, but it's ok, it can be done. It's just not

Best regards,

Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.

More information about the buildroot mailing list