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
+16-18Lines changed: 16 additions & 18 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 default editor (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,15 +72,15 @@ 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 default editor (latest supported editor) and an older supported editor
75
+
# 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 default editor (latest supported editor) and an older supported editor
79
+
# 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 default editor (latest supported editor) and an older supported editor
83
+
# Run tools integration tests EditMode and Playmode tests on {{ validation_editors.default }} (latest supported editor) and an {{ validation_editors.minimal }} supported editor
# Run all tests on default editor (latest supported editor) on nightly basis.
112
+
# Run all tests on {{ validation_editors.default }} (latest supported editor) on nightly basis.
115
113
# Same subset as pull_request_trigger with addition of mobile/desktop/console tests and webgl builds
116
-
# Those tests are all running on default editor (latest supported editor) since it's daily and running all of them would add a lot of overhead
114
+
# 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
117
115
develop_nightly:
118
-
name: "\U0001F319 [Nightly] Run All Tests [default and 2022]"
116
+
name: "\U0001F319 [Nightly] Run All Tests [{{ validation_editors.default }} and {{ validation_editors.minimal }}]"
# Run package EditMode and Playmode tests on desktop platforms on default editor (latest supported editor) and {{ validation_editors.minimal }}
130
+
# 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 default editor (latest supported editor) and {{ validation_editors.minimal }}
133
+
# 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,7 +155,7 @@ develop_nightly:
157
155
# Run all tests on weekly bases
158
156
# Same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
159
157
# It's not running wrench jobs since those will run either way in nightly test run
160
-
# This in contrast to nightly checks will run tests on all editors (not only default). Running those on weekly basis and default editor (latest supported editor) tests nightly should be a good balance between making sure that tests are passing and overhead of running lots of tests
158
+
# 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
# In theory this job also runs package tests, but we don't want to use it as default since is heavier (because of added coverage analysis) and coverage is not changing that often
0 commit comments