8ea6eead60
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> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| .. | ||
| config-fragments | ||
| dependencies | ||
| docker | ||
| download | ||
| gnuconfig | ||
| kconfig | ||
| legal-info | ||
| libtool | ||
| misc | ||
| scripts | ||
| testing | ||