From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] .gitlab-ci.yml: add trigger per type of job
Date: Sun, 9 Dec 2018 21:29:21 +0100 [thread overview]
Message-ID: <20181209212921.3897992e@windsurf> (raw)
In-Reply-To: <20181028235839.22472-2-ricardo.martincoski@gmail.com>
Hello,
On Sun, 28 Oct 2018 20:58:37 -0300, Ricardo Martincoski wrote:
> Currently the user has 2 sets of jobs that can be triggered on a GitLab
> pipeline.
> - to trigger all defconfigs, all runtime tests and all check-* jobs:
> $ git tag <name>
> $ git push gitlab <name> # currently 260 jobs
> - to trigger only the check-* jobs:
> $ git push gitlab HEAD:<name> # currently 4 jobs
>
> This is not much versatile, so the user ends up hand-editing the
> .gitlab-ci.yml in order to trigger some subsets, even the common ones,
> for instance all runtime tests.
>
> Add 2 more subsets that can be triggered based on the name of the
> branch pushed.
> - to trigger all defconfigs and all check-* jobs:
> $ git push gitlab HEAD:<name>-defconfigs # currently 192 jobs
> - to trigger all runtime tests and all check-* jobs:
> $ git push gitlab HEAD:<name>-runtime-tests # currently 72 jobs
>
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
This commit was applied by Arnout a while ago:
https://git.buildroot.org/buildroot/commit/?id=f177fd66e47879a72bb678a2de7ce658410cc4b9.
But apparently, the notification was not sent to the mailing list, and
the patchwork state was not updated. This mail does the former, and I'm
going to the latter :-)
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-09 20:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 23:58 [Buildroot] [PATCH 0/3] .gitlab-ci.yml: add trigger per job and per type of job Ricardo Martincoski
2018-10-28 23:58 ` [Buildroot] [PATCH 1/3] .gitlab-ci.yml: add trigger " Ricardo Martincoski
2018-12-09 20:29 ` Thomas Petazzoni [this message]
2018-10-28 23:58 ` [Buildroot] [PATCH 2/3] Makefile: offload .gitlab-ci.yml generation Ricardo Martincoski
2018-12-09 20:32 ` Thomas Petazzoni
2018-10-28 23:58 ` [Buildroot] [PATCH 3/3] .gitlab-ci.yml: add trigger per job Ricardo Martincoski
2018-12-09 20:59 ` Thomas Petazzoni
2019-01-16 22:57 ` Ricardo Martincoski
2018-12-10 13:30 ` Matthew Weber
2018-12-13 16:55 ` Matthew Weber
2019-01-09 14:57 ` Matthew Weber
2019-01-11 2:52 ` Ricardo Martincoski
2019-01-16 22:45 ` [Buildroot] [PATCH v2] " Ricardo Martincoski
2019-01-18 10:21 ` Arnout Vandecappelle
2019-01-20 20:21 ` Ricardo Martincoski
2019-01-21 1:11 ` [Buildroot] [PATCH v3 0/5] .gitlab-ci.yml: rework and " Ricardo Martincoski
2019-01-21 1:11 ` [Buildroot] [PATCH v3 1/5] .gitlab-ci.yml: use "extends" keyword Ricardo Martincoski
2019-02-06 10:53 ` Arnout Vandecappelle
2019-01-21 1:11 ` [Buildroot] [PATCH v3 2/5] .gitlab-ci.yml: use "include" keyword Ricardo Martincoski
2019-02-06 10:59 ` Arnout Vandecappelle
2019-04-08 3:22 ` Ricardo Martincoski
2019-01-21 1:11 ` [Buildroot] [PATCH v3 3/5] .gitlab-ci.yml: reorder jobs Ricardo Martincoski
2019-01-21 1:11 ` [Buildroot] [PATCH v3 4/5] .gitlab-ci.yml: prepare to reuse scripts Ricardo Martincoski
2019-01-21 1:11 ` [Buildroot] [PATCH v3 5/5] .gitlab-ci.yml: add trigger per job Ricardo Martincoski
2019-04-08 3:22 ` [Buildroot] [PATCH v4 0/3] .gitlab-ci.yml: rework and " Ricardo Martincoski
2019-04-08 3:22 ` [Buildroot] [PATCH v4 1/3] .gitlab-ci.yml: reorder jobs Ricardo Martincoski
2019-04-13 13:43 ` Arnout Vandecappelle
2019-04-08 3:22 ` [Buildroot] [PATCH v4 2/3] .gitlab-ci.yml: prepare to reuse scripts Ricardo Martincoski
2019-04-08 3:22 ` [Buildroot] [PATCH v4 3/3] .gitlab-ci.yml: add trigger per job Ricardo Martincoski
2019-04-13 13:46 ` Arnout Vandecappelle
2019-04-22 1:27 ` Ricardo Martincoski
2019-04-22 7:19 ` Arnout Vandecappelle
2019-05-01 13:54 ` Arnout Vandecappelle
2018-10-31 9:13 ` [Buildroot] [PATCH 0/3] .gitlab-ci.yml: add trigger per job and per type of job Thomas Petazzoni
2018-11-02 4:22 ` Ricardo Martincoski
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=20181209212921.3897992e@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