Skip to contentSkip to conversation

support/scripts: reduce the number of jobs created when a tag is added

RFC New Romain Naour 1 participant 1 message Nov 14, 2020

lore
Share & tools
lore
#0 lore raw

RFC 1/1 support/scripts: reduce the number of jobs created when a tag is added

Currently when a tag is added to the Buildroot git tree, the gitlab-ci create 613 jobs. This trigger the error "pipeline job activity limit exceeded" and created jobs are stuck indefinitely (we need to restart manually a job to execute the pipeline).

In order to reduce the number of jobs created, we keep only the runtime tests and the Qemu's defconfigs.

Cc Thomas Petazzoni <[email protected]>
Cc Yann E. MORIN <[email protected]>
Cc Arnout Vandecappelle <[email protected]>

---
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.

---
 support/scripts/generate-gitlab-ci-yml | 3 +++
 1 file changed, 3 insertions(+)
support/scripts/generate-gitlab-ci-yml +3 -0
index 4d979dd819..eaa3b226aa 100755
@@ -36,6 +36,9 @@ gen_tests() {
              )
 
     if [ -n "${CI_COMMIT_TAG}" ]; then
+        # When a tag is added to the Buildroot git tree, we want
+        # to run the runtime tests and only testing Qemu defconfigs.
+        defconfigs=( $(cd configs; LC_ALL=C ls -1 qemu_*_defconfig) )
         do_basics=true
         do_defconfigs=base
         do_runtime=true
Signature · 1 line
2.25.4