ci(cmakev2): run the buildv2 tests only if the buildv2 label is set

Currently, the buildv2 tests are initiated using the same patterns as
the tests for the current build system. This means that any change in
the current build system will also trigger the buildv2 tests. Initially,
it might be wise not to block the CI for changes in the current build
system in case there is an issue with buildv2. Therefore, let's
explicitly start the buildv2 tests only when the buildv2 label is set.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>
This commit is contained in:
Frantisek Hrbata
2025-10-15 09:10:14 +02:00
committed by BOT
parent 67c8d97280
commit e65fc5ee09
4 changed files with 17 additions and 2 deletions

View File

@@ -256,7 +256,9 @@ pytest_build_system:
parallel: 3
pytest_buildv2_system:
extends: .test_build_system_template
extends:
- .test_build_system_template
- .rules:labels:buildv2
parallel: 3
script:
- ${IDF_PATH}/tools/ci/test_configure_ci_environment.sh

View File

@@ -76,3 +76,7 @@
- if-schedule-test-build-system-windows
patterns:
- build_system_win
"labels:buildv2":
labels:
- buildv2

View File

@@ -276,6 +276,9 @@
.if-label-build: &if-label-build
if: '$BOT_LABEL_BUILD || $CI_MERGE_REQUEST_LABELS =~ /^(?:[^,\n\r]+,)*build(?:,[^,\n\r]+)*$/i'
.if-label-buildv2: &if-label-buildv2
if: '$BOT_LABEL_BUILDV2 || $CI_MERGE_REQUEST_LABELS =~ /^(?:[^,\n\r]+,)*buildv2(?:,[^,\n\r]+)*$/i'
.if-label-docker: &if-label-docker
if: '$BOT_LABEL_DOCKER || $CI_MERGE_REQUEST_LABELS =~ /^(?:[^,\n\r]+,)*docker(?:,[^,\n\r]+)*$/i'
@@ -364,6 +367,12 @@
- <<: *if-dev-push
changes: *patterns-downloadable-tools
.rules:labels:buildv2:
rules:
- <<: *if-revert-branch
when: never
- <<: *if-label-buildv2
.rules:labels:nvs_coverage:
rules:
- <<: *if-revert-branch

View File

@@ -140,7 +140,7 @@ pytest_build_system_win_minimal_cmake:
pytest_buildv2_system_win:
extends:
- .test_build_system_template_win
- .rules:labels:windows_pytest_build_system
- .rules:labels:buildv2
parallel: 2
needs: []
tags: [windows-build, brew]