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: Adding minimal supported editor specific tests and improving trigger jobs coverage (#3409)
This PR aims to add minimal supported editor (6000.0) specific tests so
we can differentiate between those and trunk tests as well as adding
more variations to PR trigger job.
Additionally it introduces _**run_quick_checks**_ job that was added as
a requirement for package_pack and project_pack jobs. It will run as a
first check (also on PR trigger) to catch any basic errors (PVP and
project standards) and ONLY IF this job will pass, the rest of PR
trigger job dependencies will be executed.
This way provides faster feedback loop for developers and allow to
minimize resource usage when unnecessary
Failing result may look like this

Where we can see that many jobs failed but in reality we can see that
only PVP jobs failed and others were never executed and failed due to
their dependencies
## Backport
This is specific change to develop-2.0.0 branch but it's somewhat
reflected in
#3408
# 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.
9
+
# 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.
{% if platform.name != "mac" -%} # There is an error about "Light baking could not be started because no valid OpenCL device could be found". Tracked in MTT-11726
# 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
18
18
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
24
24
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
# 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.
# 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.
43
+
# This job will FIRST run "run_quick_checks" jobs (defined in _run-all.yml) since it's the dependency of project pack jobs which is on the lowest dependency tier. This runs the fastest checks (like PVP or code standards) and ONLY IF those pass it will run the rest of the tests.
44
+
# This optimization allows to speed up feedback look for any "obvious" errors and save resources.
45
+
# Since standards job is a part of initial checks it's not present as direct dependency here
# 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)
# Run project EditMode and PLaymode project tests on minimum supported editor (6000.0 in case of NGOv2.X)
56
+
- .yamato/_run-all.yml#run_all_project_tests_6000
57
+
# 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.
- npm install upm-ci-utils@stable -g --registry https://artifactory.prd.cds.internal.unity3d.com/artifactory/api/npm/upm-npm # upm-ci is not preinstalled on the image so we need to download it
0 commit comments