Skip to contentSkip to conversation

CI: Add "allyesconfig" to one of the build jobs

PATCH In review Tom Rini 1 participant 2 messages Dec 31, 2025 – Jan 6

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

PATCH 1/1 CI: Add "allyesconfig" to one of the build jobs

Now that we can have "make allyesconfig" build and link, add this type of build to the job which builds host tools as well. In GitLab, make this job rather than binman testsuite be the job which unblocks the next stage of the pipeline. This is because we had been using that job for "sandbox builds", and now that we have an explicit test for that, we should use it.

---
Technically, this still requires:
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
to be applied first. I will pick that up before applying.

---
 .azure-pipelines.yml |  8 ++++++--
 .gitlab-ci.yml       | 10 +++++++---
 2 files changed, 13 insertions(+), 5 deletions(-)
.azure-pipelines.yml +6 -2
index 25b0e4c985c8..46655776ffad 100644
@@ -128,8 +128,8 @@ stages:
       - script: |
           ./tools/buildman/buildman --maintainer-check
 
-  - job: tools_only
-    displayName: 'Ensure host tools and env tools build'
+  - job: allyesconfig_and_tools
+    displayName: 'Ensure allyesconfig, tools-only and envtools build'
     pool:
       vmImage: $(ubuntu_vm)
     container:
@@ -137,6 +137,10 @@ stages:
       options: $(container_option)
     steps:
       - script: |
+          # Allow pipefail because of how we use 'yes' here.
+          set +o pipefail;
+          yes 0 | make allyesconfig oldconfig all -j$(nproc)
+          make mrproper
           make tools-only_config tools-only -j$(nproc)
           make mrproper
           make tools-only_config envtools -j$(nproc)
.gitlab-ci.yml +7 -3
index 08bea0dd2342..b9843c4ff265 100644
@@ -32,7 +32,7 @@ stages:
 .buildman_and_testpy_template: &buildman_and_testpy_dfn
   stage: test.py
   retry: 2 # QEMU may be too slow, etc.
-  needs: [ "Run binman, buildman, dtoc, Kconfig and patman testsuites" ]
+  needs: [ "Build allyesconfig, tools-only and envtools" ]
   before_script:
     # Clone uboot-test-hooks
     - git config --global --add safe.directory "${CI_PROJECT_DIR}"
@@ -195,10 +195,14 @@ Check for configs without MAINTAINERS entry:
     - ./tools/buildman/buildman --maintainer-check
 
 # Ensure host tools build
-Build tools-only and envtools:
+Build allyesconfig, tools-only and envtools:
   extends: .testsuites
   script:
-    - make tools-only_config tools-only -j$(nproc);
+    # Allow pipefail because of how we use 'yes' here.
+    - set +o pipefail;
+      yes 0 | make allyesconfig oldconfig all -j$(nproc);
+      make mrproper;
+      make tools-only_config tools-only -j$(nproc);
       make mrproper;
       make tools-only_config envtools -j$(nproc)
 
Signature · 1 line
2.43.0
author
#1 lore raw
Quoted 8 lines · Tom Rini

Now that we can have "make allyesconfig" build and link, add this type of build to the job which builds host tools as well. In GitLab, make this job rather than binman testsuite be the job which unblocks the next stage of the pipeline. This is because we had been using that job for "sandbox builds", and now that we have an explicit test for that, we should use it.

[...]

Applied to u-boot/master, thanks!

[1/1] CI: Add "allyesconfig" to one of the build jobs

      commit: 1d59479362c7f6a681a2b3c14e97edff7c0f5a7c
Signature · 1 line
Tom