Skip to content

Commit d295f92

Browse files
committed
Updated trigger jobs with minimal supported editor
1 parent eefe774 commit d295f92

File tree

1 file changed

+52
-39
lines changed

1 file changed

+52
-39
lines changed

.yamato/_triggers.yml

Lines changed: 52 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -2,55 +2,60 @@
22
---
33

44
# DESCRIPTION--------------------------------------------------------------------------
5-
# This configuration defines three main CI trigger patterns:
6-
# 1. Pull Request Validation: Validation performed on PR basis
7-
# 2. Nightly Development: Test set run nightly (validates most important test cases)
8-
# 3. Weekly Full Validation: Test set run weekly (validates all test cases to prevent any suprises)
9-
# Each pattern represents different balance between validation depth, execution time and CI resource usage
5+
# This configuration defines three main CI trigger patterns:
6+
# 1. Pull Request Validation: Validation performed on PR basis
7+
# 2. Nightly Development: Test set run nightly (validates most important test cases)
8+
# 3. Weekly Full Validation: Test set run weekly (validates all test cases to prevent any surprises)
9+
# Each pattern represents different balance between validation depth, execution time and CI resource usage
1010

1111
# TRIGGER PATTERNS-------------------------------------------------------------------
12-
# Pull Request:
13-
# This test validaes Standards, Package tests, Project tests and Desktop standalone tests to ensure that main platforms are covered
14-
# Triggers on PRs to develop, develop-2.0.0, and release branches
15-
# Focuses on critical validation paths that we should validate before merging PRs
16-
# Cancels previous runs on new commits
17-
# Excludes draft PRs
12+
# Pull Request:
13+
# This test validates Standards, Package tests, Project tests and Desktop standalone tests to ensure that main platforms are covered
14+
# Triggers on PRs to develop, develop, and release branches
15+
# Focuses on critical validation paths that we should validate before merging PRs
16+
# Cancels previous runs on new commits
17+
# Excludes draft PRs
1818

19-
# Nightly:
20-
# This test validaes same subset as pull_request_trigger with addition of mobile/console tests and webgl builds
21-
# Runs daily on develop-2.0.0 (local configuration)
22-
# Includes all test types but only on trunk. TODO: Add validation for minimum supported editor in nightly
23-
# Adds platform-specific and APV validation
19+
# Nightly:
20+
# This test validates same subset as pull_request_trigger with addition of mobile/console tests and webgl builds
21+
# Runs daily on develop (local configuration)
22+
# Includes all test types but only on trunk.
23+
# Adds platform-specific and APV validation
2424

25-
# Weekly:
26-
# This test validaes same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
27-
# Runs across all supported editor versions
28-
# Includes code coverage analysis
29-
# Validates all projects and standards
25+
# Weekly:
26+
# This test validates same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
27+
# Runs across all supported editor versions
28+
# Includes code coverage analysis
29+
# Validates all projects and standards
3030

3131
# CONFIGURATION STRUCTURE--------------------------------------------------------------
32-
# Jobs configurations are generated by ensuring that all dependencies are successful.
33-
# The dependencies are taken from _run-all.yml file where we can gather multiple tests into proper sets
32+
# Jobs configurations are generated by ensuring that all dependencies are successful.
33+
# The dependencies are taken from _run-all.yml file where we can gather multiple tests into proper sets
3434

3535
# QUALITY CONSIDERATIONS---------------------------------------------------------------
3636
# It's important to ensure that all dependencies exist (this can be verified in Yamato) since a modification in parameters may result in a given job not being generated, and thus we will not be able to run such erroneous job.
3737

3838

39-
4039
#-----------------------------------------------------------------------------------
4140

4241
# Run all relevant tasks when a pull request targeting the develop or release branch is created or updated.
42+
# In order to have better coverage we run desktop standalone tests with different configurations which allows to mostly cover for different platforms, scripting backends and editor versions.
4343
pull_request_trigger:
4444
name: Pull Request Trigger (develop, develop-2.0.0, & release branches)
4545
dependencies:
46-
# Run project standards to verify package/default project
46+
# Run project standards to verify package/default project. This is fine to just run for trunk
4747
- .yamato/project-standards.yml#standards_ubuntu_testproject_trunk
48-
# Run package EditMode and Playmode tests on desktop platforms on trunk
48+
# Run package EditMode and Playmode package tests on trunk
4949
- .yamato/_run-all.yml#run_all_package_tests_trunk
50-
# Run project EditMode and PLaymode tests on desktop platforms on trunk
50+
# Run package EditMode and Playmode package tests on minimum supported editor (6000.0 in case of NGOv2.X)
51+
- .yamato/_run-all.yml#run_all_package_tests_6000
52+
# Run project EditMode and PLaymode project tests on trunk
5153
- .yamato/_run-all.yml#run_all_project_tests_trunk
52-
# Run one standalone test to make sure there are no obvious issues with most common platform (for example --fail-on-assert option is not present with package/project tests)
53-
- .yamato/desktop-standalone-tests.yml#desktop_standalone_test_testproject_win_il2cpp_trunk
54+
# Run project EditMode and PLaymode project tests on minimum supported editor (6000.0 in case of NGOv2.X)
55+
- .yamato/_run-all.yml#run_all_project_tests_6000
56+
# Run standalone test with mixture of parameters to make sure there are no obvious issues with most common platform (for example --fail-on-assert option is not present with package/project tests). We run 2 different combinations with different platform/editor/scripting backend.
57+
- .yamato/desktop-standalone-tests.yml#desktop_standalone_test_testproject_mac_il2cpp_trunk
58+
- .yamato/desktop-standalone-tests.yml#desktop_standalone_test_testproject_win_mono_6000.0
5459
triggers:
5560
cancel_old_ci: true
5661
pull_requests:
@@ -60,37 +65,45 @@ pull_request_trigger:
6065
- "develop-2.0.0"
6166
- "/release\/.*/"
6267
- drafts: false
63-
68+
6469

6570
# Run all tests on trunk on nightly basis.
6671
# Same subset as pull_request_trigger with addition of mobile/desktop/console tests and webgl builds
6772
# Those tests are all running on trunk editor (since it's daily and running all of them would add a lot of overhead)
6873
develop_nightly:
69-
name: "\U0001F319 [Nightly] Run All Tests [Trunk]"
74+
name: "\U0001F319 [Nightly] Run All Tests [Trunk and 6000]"
7075
triggers:
7176
recurring:
7277
- branch: develop-2.0.0
7378
frequency: daily
7479
rerun: always
7580
dependencies:
7681
# Run project standards to verify package/default project
77-
- .yamato/project-standards.yml#standards_ubuntu_testproject_trunk
82+
- .yamato/project-standards.yml#standards_win_testproject_trunk
83+
- .yamato/project-standards.yml#standards_ubuntu_testproject_6000.0
7884
# Run APV jobs to make sure the change won't break any dependants
7985
- .yamato/wrench/preview-a-p-v.yml#all_preview_apv_jobs
80-
# Run package EditMode and Playmode tests on desktop platforms on trunk
86+
# Run package EditMode and Playmode tests on desktop platforms on trunk and 6000.0
8187
- .yamato/_run-all.yml#run_all_package_tests_trunk
82-
# Run project EditMode and PLaymode tests on desktop platforms on trunk
88+
- .yamato/_run-all.yml#run_all_package_tests_6000
89+
# Run project EditMode and PLaymode tests on desktop platforms on trunk and 6000.0
8390
- .yamato/_run-all.yml#run_all_project_tests_trunk
84-
# Run Runtime tests on desktop players on trunk
91+
- .yamato/_run-all.yml#run_all_project_tests_6000
92+
# Run Runtime tests on desktop players on trunk and 6000.0 editors
8593
- .yamato/_run-all.yml#run_all_project_tests_desktop_standalone_trunk
86-
# Run Runtime tests on mobile players on trunk
94+
- .yamato/_run-all.yml#run_all_project_tests_desktop_standalone_6000
95+
# Run Runtime tests on mobile players on trunk and 6000.0 editors
8796
- .yamato/_run-all.yml#run_all_project_tests_mobile_standalone_trunk
88-
# Run Runtime tests on console players on trunk
97+
- .yamato/_run-all.yml#run_all_project_tests_mobile_standalone_6000
98+
# Run Runtime tests on console players on trunk and 6000.0 editors
8999
- .yamato/_run-all.yml#run_all_project_tests_console_standalone_trunk
90-
# Build player for webgl platform on trunk
100+
- .yamato/_run-all.yml#run_all_project_tests_console_standalone_6000
101+
# Build player for webgl platform on trunk and 6000.0 editors
91102
- .yamato/_run-all.yml#run_all_webgl_builds_trunk
92-
# Build player for webgl platform on trunk
103+
- .yamato/_run-all.yml#run_all_webgl_builds_6000
104+
# Build player for webgl platform on trunk and 6000.0 editors
93105
- .yamato/project-updated-dependencies-test.yml#updated-dependencies_testproject_NGO_ubuntu_trunk
106+
- .yamato/project-updated-dependencies-test.yml#updated-dependencies_testproject_NGO_win_6000.0
94107

95108

96109
# Run all tests on weekly bases

0 commit comments

Comments
 (0)