From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH buildroot-test 00/10] add gitlab-ci jobs to the daily-mail
Date: Thu, 5 Sep 2019 23:48:49 +0200 [thread overview]
Message-ID: <20190905234849.0aeb11b0@windsurf> (raw)
In-Reply-To: <20190829132348.1603-1-victor.huesca@bootlin.com>
Hello Victor,
On Thu, 29 Aug 2019 15:23:38 +0200
Victor Huesca <victor.huesca@bootlin.com> wrote:
> Victor Huesca (10):
> utils/daily-mail: new data: gitlab-ci jobs
> utils/daily-mail: new gitlab-ci data: defconfigs
> utils/daily-mail: new gitlab-ci data: runtime tests
> utils/daily-mail: add defconfig support in developers notifications
> utils/daily-mail: add runtime tests support in developers
> notifications
> utils/daily-mail: prepare the mail formatting to support gitlab-ci
> results
> utils/daily-mail: add formatting for defconfig results
> utils/daily-mail: add formatting for runtime-test results
> utils/daily-mail: add argument for gitlab-ci related data
> utils/daily-mail: enable gitlab-ci emails
Thanks for this patch series! I have made a number of changes, and
applied it.
The main changes are:
- More filtering of pipelines: only failed pipelines are retrieved
- Earlier filtering of pipelines: we can filter pipelines by branch
and status before getting the details for each pipeline
- Removal of the job duration in the e-mails, it is not a very useful
information IMO
- Further splitting of some of the patches
So, hopefully this Saturday we should see e-mails about defconfig
failures, since we have at least one still failing on master.
Thanks a lot for this work!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-09-05 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 13:23 [Buildroot] [PATCH buildroot-test 00/10] add gitlab-ci jobs to the daily-mail Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 01/10] utils/daily-mail: new data: gitlab-ci jobs Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 02/10] utils/daily-mail: new gitlab-ci data: defconfigs Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 03/10] utils/daily-mail: new gitlab-ci data: runtime tests Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 04/10] utils/daily-mail: add defconfig support in developers notifications Victor Huesca
2019-09-03 14:27 ` Titouan Christophe
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 05/10] utils/daily-mail: add runtime tests " Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 06/10] utils/daily-mail: prepare the mail formatting to support gitlab-ci results Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 07/10] utils/daily-mail: add formatting for defconfig results Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 08/10] utils/daily-mail: add formatting for runtime-test results Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 09/10] utils/daily-mail: add argument for gitlab-ci related data Victor Huesca
2019-08-29 13:23 ` [Buildroot] [PATCH buildroot-test 10/10] utils/daily-mail: enable gitlab-ci emails Victor Huesca
2019-09-05 21:48 ` Thomas Petazzoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190905234849.0aeb11b0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox