Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 RFC] support/scripts: don't build board defconfigs with Gitlab's pipelines trigged on tag
Date: Wed, 17 Nov 2021 22:19:51 +0100	[thread overview]
Message-ID: <87fsruv5s8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20211109220328.388872-1-romain.naour@gmail.com> (Romain Naour's message of "Tue, 9 Nov 2021 23:03:28 +0100")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

 > Currently when a tag is added to the Buildroot git tree, the gitlab-ci
 > create a pipeline with several hundred of jobs (~750) to build all
 > defconfigs and execute the Buildroot testsuite.

 > However, there is only a limited number of gitlab-ci runner (9 runners)
 > and some jobs reach the timeout limit (24h) while waiting for a runner
 > [1]. Indeed, the Buildroot project doesn't use the Gitlab's shared
 > runners.

 > In addition to the pipeline created when a new tag is added to the
 > git repository, two pipelines are created each weeks to execute the
 > Buildroot testsuite (on monday [2]) and build all defconfigs (on
 > Thursday [3]).

 > At some point there are too many jobs waiting in gitlab due board
 > defconfigs builds. Indded a board defconfig requires a lot of time
 > (~30min) compared to other jobs in order to build a toolchain and a
 > kernel linux along with a basic rootfs. There is currently 262
 > defconfigs.

 > This is even worse when several pipelines are trigged at the same
 > time (new git tag and scheduled pipeline trigger).

 > In order to reduce the number of long jobs, don't build board
 > defconfigs with pipelines trigged on tag, keeping only the runtime
 > tests and the Qemu's defconfigs.

 > [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/1758966541
 > [2] https://gitlab.com/buildroot.org/buildroot/-/pipelines/404035190
 > [3] https://gitlab.com/buildroot.org/buildroot/-/pipelines/401685550

 > Signed-off-by: Romain Naour <romain.naour@gmail.com>
 > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
 > Cc: Yann E. MORIN <yann.morin.1998@free.fr>
 > Cc: Arnout Vandecappelle <arnout@mind.be>
 > ---
 > v2: improve commit log

 > I would like to keep Qemu runtime testing when a tag is added because
 > it test the toolchain provided by default by Buildroot on several
 > architectures.

Committed to 2021.02.x and 2021.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2021-11-17 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 22:03 [Buildroot] [PATCH v2 RFC] support/scripts: don't build board defconfigs with Gitlab's pipelines trigged on tag Romain Naour
2021-11-10  9:34 ` Yann E. MORIN
2021-11-11  8:25 ` Yann E. MORIN
2021-11-11 10:02   ` Thomas Petazzoni
2021-11-11 10:15     ` Yann E. MORIN
2021-11-11 11:05       ` Romain Naour
2021-11-11 13:55       ` Thomas Petazzoni
2021-11-16 19:27 ` Arnout Vandecappelle
2021-11-17 21:19 ` Peter Korsgaard [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=87fsruv5s8.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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