You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .yamato/_triggers.yml
+38-38Lines changed: 38 additions & 38 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@
24
24
# Nightly:
25
25
# This test validates same subset as pull_request_trigger with addition of mobile/console tests and webgl builds
26
26
# Runs daily on develop (local configuration)
27
-
# Includes all test types but only on 6000.2 (latest supported editor).
27
+
# Includes all test types but only on {{ validation_editors.default }} (latest supported editor).
28
28
# Adds platform-specific and APV validation
29
29
30
30
# Weekly:
@@ -72,21 +72,21 @@ pr_code_changes_checks:
72
72
# Run API validation to early-detect all new APIs that would force us to release new minor version of the package. Note that for this to work the package version in package.json must correspond to "actual package state" which means that it should be higher than last released version
73
73
- .yamato/vetting-test.yml#vetting_test
74
74
75
-
# Run package EditMode and Playmode package tests on 6000.2 (latest supported editor) and an older supported editor (2022.3) (2022.3 will soon be a minimum supported editor)
# Run package EditMode and Playmode package tests on {{ validation_editors.default }} (latest supported editor) and an {{ validation_editors.minimal }} supported editor
# Run testproject EditMode and Playmode project tests on 6000.2 (latest supported editor) and an older supported editor (2022.3) (2022.3 will soon be a minimum supported editor)
# Run testproject EditMode and Playmode project tests on {{ validation_editors.default }} (latest supported editor) and an {{ validation_editors.minimal }} supported editor
# Run tools integration tests EditMode and Playmode tests on 6000.2 (latest supported editor) and an older supported editor (2022.3) (2022.3 will soon be a minimum supported editor)
# Run tools integration tests EditMode and Playmode tests on {{ validation_editors.default }} (latest supported editor) and an {{ validation_editors.minimal }} supported editor
# Run standalone test. We run it only on Ubuntu since it's the fastest machine, and it was noted that for example distribution on macOS is taking 40m since we switched to Apple Silicon
88
88
# Coverage on other standalone machines is present in Nightly job so it's enough to not run all of them for PRs
# Run all tests on 6000.2 (latest supported editor) on nightly basis.
117
+
# Run all tests on {{ validation_editors.default }} (latest supported editor) on nightly basis.
118
118
# Same subset as pull_request_trigger with addition of mobile/desktop/console tests and webgl builds
119
-
# Those tests are all running on 6000.2 (latest supported editor) since it's daily and running all of them would add a lot of overhead
119
+
# Those tests are all running on {{ validation_editors.default }} (latest supported editor) since it's daily and running all of them would add a lot of overhead
120
120
develop_nightly:
121
-
name: "\U0001F319 [Nightly] Run All Tests [6000.2 and 2022]"
121
+
name: "\U0001F319 [Nightly] Run All Tests [{{ validation_editors.default }} and {{ validation_editors.minimal }}]"
122
122
triggers:
123
123
recurring:
124
124
- branch: develop
@@ -129,38 +129,38 @@ develop_nightly:
129
129
- .yamato/vetting-test.yml#vetting_test
130
130
# Run project standards to verify package/default project
# Run package EditMode and Playmode tests on desktop platforms on 6000.2 (latest supported editor) and 2022.3 (2022.3 will soon be a minimum supported editor)
# Run project EditMode and PLaymode tests on desktop platforms on 6000.2 (latest supported editor) and 2022.3 (2022.3 will soon be a minimum supported editor)
# Run package EditMode and Playmode tests on desktop platforms on {{ validation_editors.default }} (latest supported editor) and {{ validation_editors.minimal }}
# Run project EditMode and PLaymode tests on desktop platforms on {{ validation_editors.default }} (latest supported editor) and {{ validation_editors.minimal }}
# Run API validation to early-detect all new APIs that would force us to release new minor version of the package. Note that for this to work the package version in package.json must correspond to "actual package state" which means that it should be higher than last released version
157
157
- .yamato/vetting-test.yml#vetting_test
158
158
159
159
160
160
# Run all tests on weekly bases
161
161
# Same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
162
162
# It's not running wrench jobs since those will run either way in nightly test run
163
-
# This in contrast to nightly checks will run tests on all editors (not only 6000.2). Running those on weekly basis and 6000.2 (latest supported editor) tests nightly should be a good balance between making sure that tests are passing and overhead of running lots of tests
163
+
# This in contrast to nightly checks will run tests on all editors (not only {{ validation_editors.default }}). Running those on weekly basis and {{ validation_editors.default }} (latest supported editor) tests nightly should be a good balance between making sure that tests are passing and overhead of running lots of tests
0 commit comments