[Buildroot] [RFC] Getting run-time / defconfig testing maintainers feedback of failures

[Thomas Petazzoni <thomas.petazzoni@bootlin.com>]

Hello Matt,

On Wed, 6 Feb 2019 08:14:37 -0600
Matthew Weber <matthew.weber@rockwellcollins.com> wrote:

> Has there been any ideas or proposals so far for giving more
> visibility to the CI failures?  I definitely want to contribute if
> there is something in progress, otherwise here's a proposal..........
> 
> One idea I had been throwing around was since you can personally fork
> Buildroot in Gitlab and have your own personal Gitlab-runners doing
> the CI builds.  Once the per job trigger series[1] merges, I'd like to
> proposed adding a manual section which talks about the following
> 1) How a user can setup a Buildroot fork on Gitlab
> 2) Enable it to follow the main Gitlab Buildroot repo
> 3) Create cron jobs for their test cases
> 4) Manage notifications to track build failures
> 5) Notes on Gitlab-runner setup
> 
> This doesn't replace the main CI testing and reporting, however it
> would put more ownership of defconfigs/run-time test fixing on others.

My idea, which puts less burden on the shoulder of individual
contributors is to extend the daily-mail script [1] that is used today
to send autobuilder results. The extension would consist in using the
Gitlab CI API to analyze the results of the last pipelines, and if
there's a failure on a defconfig or test, mail the corresponding
person. Thanks to this, we would have a single mail per day sent out
(to the mailing list and to participants) with autobuilder failures and
gitlab CI failures.

What do you think ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com