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
ci: setting maximum supported editor for NGOv1.X (#3584)
This PR addresses the fact that NGOv1.X will be deprecated in editors
after 6000.3. Because of that we can stop running release tests for
6000.3 and the same with our usual CI
On top of that I needed to move I moved BuildAutomation files since
those were preventing recipes regeneration via ./regenerate.bat and
corrected paths where needed
## Backport
No backport is required since this is not affecting NGOv2.X
# 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
21
21
- .yamato/vetting-test.yml#vetting_test
22
22
@@ -31,22 +31,22 @@ run_all_package_tests:
31
31
{% endfor -%}
32
32
33
33
34
-
# Runs all package tests on trunk editor
35
-
run_all_package_tests_trunk:
36
-
name: Run All Package Tests [Trunk only]
34
+
# Runs all package tests on 6000.2 editor (latest supported editor)
# 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 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 tools integration tests EditMode and Playmode tests on trunk and an older supported editor (2022.3) (2022.3 will soon be a minimum supported editor)
56
+
# 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 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
61
61
# Coverage on other standalone machines is present in Nightly job so it's enough to not run all of them for PRs
@@ -71,51 +71,51 @@ pull_request_trigger:
71
71
- drafts: false
72
72
73
73
74
-
# Run all tests on trunk on nightly basis.
74
+
# Run all tests on 6000.2 (latest supported editor) on nightly basis.
75
75
# Same subset as pull_request_trigger with addition of mobile/desktop/console tests and webgl builds
76
-
# Those tests are all running on trunk editor (since it's daily and running all of them would add a lot of overhead)
76
+
# 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
77
77
develop_nightly:
78
-
name: "\U0001F319 [Nightly] Run All Tests [Trunk and 2021]"
78
+
name: "\U0001F319 [Nightly] Run All Tests [6000.2 and 2022]"
79
79
triggers:
80
80
recurring:
81
81
- branch: develop
82
82
frequency: daily
83
83
rerun: always
84
84
dependencies:
85
85
# 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 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
112
112
- .yamato/vetting-test.yml#vetting_test
113
113
114
114
115
115
# Run all tests on weekly bases
116
116
# Same subset as develop_nightly but runs per all supported editors as well as executes code coverage test and runs project standards per project
117
117
# It's not running wrench jobs since those will run either way in nightly test run
118
-
# This in contrast to nightly checks will run tests on all editors (not only trunk). Running those on weekly basis and trunk tests nightly should be a good balance between making sure that tests are passing and overhead of running lots of tests
118
+
# 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
# 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