Skip to contentSkip to conversation

CI: Run scripts/check_maintainers_files.sh in the existing MAINTAINERS job

PATCH New Tom Rini 1 participant 1 message Aug 21

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

PATCH 1/1 CI: Run scripts/check_maintainers_files.sh in the existing MAINTAINERS job

Rename the existing job that does some checking of MAINTAINERS file contents already to be a little clearer that it's doing two things now, and then also run scripts/check_maintainers_files.sh in this job.

---
The overhead any CI system has on spinning up another worker means that it's noticeably more time consuming to make this job standalone than it is to repurpose an existing job.

---
 .azure-pipelines.yml | 3 ++-
 .gitlab-ci.yml       | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)
.azure-pipelines.yml +2 -1
index 015fc15d5c29..5130058925d5 100644
@@ -90,7 +90,7 @@ stages:
           make infodocs
 
   - job: maintainers
-    displayName: 'Ensure all configs have MAINTAINERS entries'
+    displayName: 'Check all configs are in MAINTAINERS and validate MAINTAINERS'
     pool:
       vmImage: $(ubuntu_vm)
     container:
@@ -99,6 +99,7 @@ stages:
     steps:
       - script: |
           ./tools/buildman/buildman --maintainer-check
+          ./scripts/check_maintainers_files.sh
 
   - job: allyesconfig_and_tools
     displayName: 'Ensure allyesconfig, tools-only and envtools build'
.gitlab-ci.yml +2 -2
index 9831dd61bc18..e08068f1cbf5 100644
@@ -189,11 +189,11 @@ docs:
     - make htmldocs KDOC_WERROR=1
     - make infodocs
 
-# ensure all configs have MAINTAINERS entries
-Check for configs without MAINTAINERS entry:
+Check all configs are in MAINTAINERS and validate MAINTAINERS:
   extends: .testsuites
   script:
     - ./tools/buildman/buildman --maintainer-check
+    - ./scripts/check_maintainers_files.sh
 
 # Ensure host tools build
 Build allyesconfig, tools-only and envtools:
Signature · 1 line
2.43.0