esp-idf/.gitlab/ci/dependencies/dependencies.yml

.all_targets: &all_targets
  - esp32
  - esp32s2
  - esp32s3
  - esp32c3
  - esp32c2
  - esp32c6
  - esp32h2
  - esp32p4

.target_test: &target_test
  - example_test
  - custom_test
  - component_ut

##############
# Build Jobs #
##############
"build":
  labels:
    - build
  patterns:
    - build_components
    - build_system
    - downloadable-tools
  included_in:
    - build:target_test
    - build:check

# -------------------
# Specific Build Jobs
# -------------------
"build:docker":
  labels:
    - build
    - docker
  patterns:
    - docker
    - submodule
    - build_system
    - downloadable-tools

"build:macos":
  labels:
    - build
    - macos
    - macos_test  # for backward compatibility
  patterns:
    - build_system
    - build_macos
    - downloadable-tools

# ---------------------------
# Add patterns to build rules
# ---------------------------
"patterns:template-app":
  patterns:
    - build_template-app
  included_in:
    - build:target_test

"patterns:build-check":
  patterns:
    - build_check
  included_in:
    - build:check

# ---------------
# Build Test Jobs
# ---------------
"build:{0}-{1}":
  matrix:
    - *target_test
    - *all_targets
  labels:
    - build
  patterns:
    - build_components
    - build_system
    - build_target_test
    - downloadable-tools
  included_in:
    - "build:{0}"
    - build:target_test

####################
# Target Test Jobs #
####################
"test:{0}-{1}":
  matrix:
    - *target_test
    - *all_targets
  labels: # For each rule, use labels <test_type> and <test_type>-<target>
    - "{0}"
    - "{0}_{1}"
    - target_test
  patterns: # For each rule, use patterns <test_type> and build-<test_type>
    - "{0}"
    - "build-{0}"
  included_in: # Parent rules
    - "build:{0}"
    - "build:{0}-{1}"
    - build:target_test

# -------------
# Special Cases
# -------------

# To reduce the specific runners' usage.
# Do not create these jobs by default patterns on development branches
# Can be triggered by labels or related changes
"test:{0}-{1}-{2}":
  matrix:
    - *target_test
    - *all_targets
    - - wifi      # pytest*wifi*
      - ethernet  # pytest*ethernet*
      - sdio      # pytest*sdio*
      - usb       # USB Device & Host tests
      - adc       # pytest*adc*
      - i154
      - flash_multi
      - ecdsa
      - nvs_encr_hmac
  patterns:
    - "{0}-{1}-{2}"
    - "{0}-{2}"
    - "target_test-{2}"
  labels:
    - "{0}_{1}"
    - "{0}"
    - target_test
  included_in:
    - "build:{0}-{1}"
    - "build:{0}"
    - build:target_test

# For example_test*flash_encryption_wifi_high_traffic jobs
# set `INCLUDE_NIGHTLY_RUN` variable when triggered on development branches
"test:example_test-{0}-include_nightly_run-rule":
  matrix:
    - - esp32
      - esp32c3
  specific_rules:
    - "if-example_test-ota-include_nightly_run-rule"
  included_in:
    - "build:example_test-{0}"
    - "build:example_test"
    - build:target_test

# For i154 runners
"test:example_test-i154":
  patterns:
    - "example_test-i154"
    - "target_test-i154"
  labels:
    - target_test
    - example_test
  included_in:
    - "build:example_test-esp32s3"
    - "build:example_test-esp32c6"
    - "build:example_test-esp32h2"
    - "build:example_test"
    - build:target_test

"test:host_test":
  labels:
    - host_test
  patterns:
    - host_test

"test:submodule":
  labels:
    - submodule
  patterns:
    - submodule

#################################
# Triggered Only By Labels Jobs #
#################################
"labels:nvs_coverage": # host_test
  labels:
    - nvs_coverage

"labels:windows_pytest_build_system":
  labels:
    - windows
  specific_rules:
    - if-schedule-test-build-system-windows
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`.all_targets: &all_targets`
			`- esp32`
			`- esp32s2`
			`- esp32s3`
			`- esp32c3`
esp8684: rename target to esp32c2 2022-01-17 21:32:56 -05:00			`- esp32c2`
ci: Enable esp32c6 example, test_apps, and unit tests CI build stage 2022-10-27 06:55:07 -04:00			`- esp32c6`
ESP32H2: Add small CI test for ESP32H2 2022-12-28 22:00:42 -05:00			`- esp32h2`
feat(esp32p4): introduced new target esp32p4, supported hello_world 2023-07-27 03:10:50 -04:00			`- esp32p4`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
			`.target_test: &target_test`
			`- example_test`
			`- custom_test`
			`- component_ut`

ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`##############`
			`# Build Jobs #`
			`##############`
			`"build":`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`labels:`
			`- build`
			`patterns:`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- build_components`
			`- build_system`
ci: trigger build jobs from changes in tools.json 2022-08-30 11:11:19 -04:00			`- downloadable-tools`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`included_in:`
			`- build:target_test`
ci(rules): add patterns fast template app Update pre-check job rules 2023-07-14 08:15:50 -04:00			`- build:check`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`# -------------------`
			`# Specific Build Jobs`
			`# -------------------`
			`"build:docker":`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`labels:`
			`- build`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- docker`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`patterns:`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- docker`
ci: updates rules to trigger docker build on submodules change 2022-08-09 07:48:29 -04:00			`- submodule`
ci: trigger build jobs from changes in tools.json 2022-08-30 11:11:19 -04:00			`- build_system`
			`- downloadable-tools`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
			`"build:macos":`
			`labels:`
			`- build`
			`- macos`
			`- macos_test # for backward compatibility`
			`patterns:`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- build_system`
ci(rules): add patterns fast template app Update pre-check job rules 2023-07-14 08:15:50 -04:00			`- build_macos`
ci: trigger build jobs from changes in tools.json 2022-08-30 11:11:19 -04:00			`- downloadable-tools`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
ci(rules): add patterns fast template app Update pre-check job rules 2023-07-14 08:15:50 -04:00			`# ---------------------------`
			`# Add patterns to build rules`
			`# ---------------------------`
			`"patterns:template-app":`
			`patterns:`
			`- build_template-app`
			`included_in:`
			`- build:target_test`

			`"patterns:build-check":`
			`patterns:`
			`- build_check`
			`included_in:`
			`- build:check`

ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`# ---------------`
			`# Build Test Jobs`
			`# ---------------`
			`"build:{0}-{1}":`
			`matrix:`
			`- *target_test`
			`- *all_targets`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`labels:`
			`- build`
			`patterns:`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- build_components`
			`- build_system`
ci: set build target test apps rules 2022-02-11 02:53:46 -05:00			`- build_target_test`
ci: trigger build jobs from changes in tools.json 2022-08-30 11:11:19 -04:00			`- downloadable-tools`
ci: split assign tests 2022-01-06 10:21:21 -05:00			`included_in:`
			`- "build:{0}"`
ci: fix target_test label usage 2022-01-06 10:24:03 -05:00			`- build:target_test`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00
			`####################`
			`# Target Test Jobs #`
			`####################`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`"test:{0}-{1}":`
			`matrix:`
			`- *target_test`
			`- *all_targets`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`labels: # For each rule, use labels <test_type> and <test_type>-<target>`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`- "{0}"`
			`- "{0}_{1}"`
ci: fix target_test label usage 2022-01-06 10:24:03 -05:00			`- target_test`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`patterns: # For each rule, use patterns <test_type> and build-<test_type>`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`- "{0}"`
			`- "build-{0}"`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`included_in: # Parent rules`
ci: split assign tests 2022-01-06 10:21:21 -05:00			`- "build:{0}"`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`- "build:{0}-{1}"`
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`- build:target_test`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`# -------------`
			`# Special Cases`
			`# -------------`
ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00
CI: improve target test rules for ethernet and wifi tests 2022-07-17 09:43:41 -04:00			`# To reduce the specific runners' usage.`
			`# Do not create these jobs by default patterns on development branches`
			`# Can be triggered by labels or related changes`
CI: reduce usage of sdio runners 2022-07-22 03:02:00 -04:00			`"test:{0}-{1}-{2}":`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`matrix:`
CI: reduce usage of sdio runners 2022-07-22 03:02:00 -04:00			`- *target_test`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`- *all_targets`
fix(ci): optimize build rules patterns add a script to check build-components-patterns in rules.yml 2023-09-08 00:45:19 -04:00			`- - wifi # pytestwifi`
ci: small cleanup for the dependencies.yml 2023-04-09 20:57:42 -04:00			`- ethernet # pytestethernet`
			`- sdio # pytestsdio`
tinyusb: Add TinyUSB example tests 2022-07-22 04:20:21 -04:00			`- usb # USB Device & Host tests`
ci: small cleanup for the dependencies.yml 2023-04-09 20:57:42 -04:00			`- adc # pytestadc`
ieee802154: add 154 lib CI initialization. 2022-09-27 05:22:34 -04:00			`- i154`
ci: add pattern for esp flash 2023-02-01 23:45:05 -05:00			`- flash_multi`
ci: Add patterns and target-tests for `ecdsa_efuse` runner 2023-04-06 02:50:44 -04:00			`- ecdsa`
nvs_flash: Extended test-app and host tests for the HMAC-based NVS encr-keys protection scheme 2023-04-16 02:11:11 -04:00			`- nvs_encr_hmac`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`patterns:`
CI: reduce usage of sdio runners 2022-07-22 03:02:00 -04:00			`- "{0}-{1}-{2}"`
			`- "{0}-{2}"`
			`- "target_test-{2}"`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`labels:`
CI: reduce usage of sdio runners 2022-07-22 03:02:00 -04:00			`- "{0}_{1}"`
			`- "{0}"`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`- target_test`
			`included_in:`
CI: reduce usage of sdio runners 2022-07-22 03:02:00 -04:00			`- "build:{0}-{1}"`
			`- "build:{0}"`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`- build:target_test`

CI: improve target test rules for ethernet and wifi tests 2022-07-17 09:43:41 -04:00			`# For example_test*flash_encryption_wifi_high_traffic jobs`
			# set `INCLUDE_NIGHTLY_RUN` variable when triggered on development branches
			`"test:example_test-{0}-include_nightly_run-rule":`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`matrix:`
			`- - esp32`
			`- esp32c3`
			`specific_rules:`
CI: improve target test rules for ethernet and wifi tests 2022-07-17 09:43:41 -04:00			`- "if-example_test-ota-include_nightly_run-rule"`
CI: add specific job rules 2022-07-08 05:47:59 -04:00			`included_in:`
			`- "build:example_test-{0}"`
			`- "build:example_test"`
			`- build:target_test`

openthread:add openthread CI 2022-08-16 22:57:39 -04:00			`# For i154 runners`
			`"test:example_test-i154":`
			`patterns:`
ieee802154: add ieee802154 component CI 2022-10-25 04:47:52 -04:00			`- "example_test-i154"`
openthread:add openthread CI 2022-08-16 22:57:39 -04:00			`- "target_test-i154"`
			`labels:`
			`- target_test`
			`- example_test`
			`included_in:`
			`- "build:example_test-esp32s3"`
openthread: add ci for esp32c6 2023-01-11 04:11:32 -05:00			`- "build:example_test-esp32c6"`
openthread: add openthread ci for ESP32-H2 2023-03-08 22:46:07 -05:00			`- "build:example_test-esp32h2"`
openthread:add openthread CI 2022-08-16 22:57:39 -04:00			`- "build:example_test"`
			`- build:target_test`

ci(rules): auto generate rules.yml labels titles and rules Also simplified the labels and ci - Remove label regular_test, weekend_test - Remove apply_job_filter - check_submodule_sync: only run on protected branch 2021-02-08 23:31:38 -05:00			`"test:host_test":`
			`labels:`
			`- host_test`
			`patterns:`
			`- host_test`

feat(ci): run check_submodule_sync_with_file_patterns 2021-02-22 23:32:12 -05:00			`"test:submodule":`
			`labels:`
			`- submodule`
			`patterns:`
			`- submodule`

ci(rules): improve rules with build files changed under components folder - drop target test run with build pattern - for unit_test on c3, use labels only 2021-02-22 03:53:37 -05:00			`#################################`
			`# Triggered Only By Labels Jobs #`
			`#################################`
ci: fix label only dependencies 2021-07-20 02:08:13 -04:00			`"labels:nvs_coverage": # host_test`
			`labels:`
			`- nvs_coverage`
ci: run pytest_build_system_win only with labels and schedule pipeline 2023-12-07 05:15:55 -05:00
			`"labels:windows_pytest_build_system":`
			`labels:`
			`- windows`
			`specific_rules:`
			`- if-schedule-test-build-system-windows`