|
1 | | -{% metadata_file .yamato/project.metafile %} |
| 1 | +{% metadata_file .yamato/project.metafile %} # All configuration that is used to create different configurations (used in for loops) is taken from this file. |
2 | 2 | --- |
3 | 3 |
|
| 4 | +# 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 surprises) |
| 9 | +# Each pattern represents different balance between validation depth, execution time and CI resource usage |
| 10 | + |
| 11 | +# TRIGGER PATTERNS------------------------------------------------------------------- |
| 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 | + |
| 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 | + |
| 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 |
| 30 | + |
| 31 | +# 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 |
| 34 | + |
| 35 | +# QUALITY CONSIDERATIONS--------------------------------------------------------------- |
| 36 | +# 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. |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | +#----------------------------------------------------------------------------------- |
| 41 | + |
4 | 42 | # Run all relevant tasks when a pull request targeting the develop or release branch is created or updated. |
5 | 43 | pull_request_trigger: |
6 | 44 | name: Pull Request Trigger (develop, develop-2.0.0, & release branches) |
|
0 commit comments