-
Notifications
You must be signed in to change notification settings - Fork 459
chore: Small yamato tweaks to try speed up our PR trigger runs #3711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop-2.0.0
Are you sure you want to change the base?
Changes from all commits
146e9cc
816fea9
469f7cc
790bc62
2aa215e
5a240a9
96c9611
59463bf
ecb9bce
46e042f
7dc9799
49b35d2
4731ff9
255a05c
14ee396
2390cbc
40c759d
7b2d2c8
37aff39
454cf58
c0ff854
acbebff
753aa65
56098df
6b06a12
8703ac6
fccced3
11aa246
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,15 +44,15 @@ | |
# 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. | ||
|
||
|
||
#----------------------------------------------------------------------------------- | ||
#----------------------------------------------------------------------------------- | ||
|
||
# After some experimenting with CI setups we discovered that even though sometimes we don't need CI to run (no reason to run package tests if only Documentation is changed) there are some checks that devs may not realize but changes in seemingly unrelated files will cause their failures | ||
# This trigger was created to ensure that ALL PRs run this minimal check even when we don't need to run full tests | ||
pr_minimal_required_checks: | ||
name: Minimal PR checks | ||
dependencies: | ||
- .yamato/package-pack.yml#package_pack_-_ngo_win | ||
- .yamato/project-standards.yml#standards_ubuntu_testproject_trunk | ||
- .yamato/package-pack.yml#package_pack_-_ngo_win | ||
triggers: | ||
expression: |- | ||
(pull_request.comment eq "ngo" OR | ||
|
@@ -72,6 +72,9 @@ pr_code_changes_checks: | |
name: Code changes PR checks | ||
# Run the following tests on a selection of different desktop platforms | ||
dependencies: | ||
# 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 | ||
- .yamato/vetting-test.yml#vetting_test | ||
|
||
# Run package EditMode and Playmode package tests on trunk and an older supported editor (6000.0) | ||
- .yamato/package-tests.yml#package_test_-_ngo_trunk_mac | ||
- .yamato/package-tests.yml#package_test_-_ngo_6000.0_win | ||
|
@@ -82,7 +85,7 @@ pr_code_changes_checks: | |
|
||
# 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 | ||
# Coverage on other standalone machines is present in Nightly job so it's enough to not run all of them for PRs | ||
- .yamato/desktop-standalone-tests.yml#desktop_standalone_test_testproject_win_il2cpp_6000.0 | ||
- .yamato/desktop-standalone-tests.yml#desktop_standalone_test_testproject_ubuntu_il2cpp_trunk | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any reason why to run this on trunk instead of the "minimal supported editor"? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It re-uses the same |
||
- .yamato/cmb-service-standalone-tests.yml#cmb_service_standalone_test_testproject_ubuntu_il2cpp_trunk | ||
triggers: | ||
expression: |- | ||
|
@@ -104,9 +107,9 @@ pr_code_changes_checks: | |
"**/*.md" | ||
] | ||
cancel_old_ci: true | ||
|
||
|
||
|
||
|
||
|
||
|
||
|
@@ -144,6 +147,9 @@ develop_nightly: | |
# Build player for webgl platform on trunk and 6000.0 editors | ||
- .yamato/_run-all.yml#run_all_webgl_builds_trunk | ||
- .yamato/_run-all.yml#run_all_webgl_builds_6000 | ||
# Run Runtime tests against cmb service on trunk and 6000.0 editors | ||
- .yamato/_run-all.yml#run_all_project_tests_cmb_service_trunk | ||
- .yamato/_run-all.yml#run_all_project_tests_cmb_service_6000 | ||
# Build player for webgl platform on trunk and 6000.0 editors | ||
- .yamato/project-updated-dependencies-test.yml#updated-dependencies_testproject_NGO_ubuntu_trunk | ||
- .yamato/project-updated-dependencies-test.yml#updated-dependencies_testproject_NGO_win_6000.0 | ||
|
@@ -177,5 +183,7 @@ develop_weekly_trunk: | |
- .yamato/_run-all.yml#run_all_project_tests_console_standalone | ||
# Build player for webgl platform on trunk | ||
- .yamato/_run-all.yml#run_all_webgl_builds | ||
# Run Runtime tests against CMB service | ||
- .yamato/_run-all.yml#run_all_project_tests_cmb_service | ||
# Run code coverage test | ||
- .yamato/code-coverage.yml#code_coverage_ubuntu_trunk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason why to remove it?
The configuration is a bit tricky in the flow but those jobs run before any other job gets executed so we take resources only if we don't have any basic mistakes. Vetting test will fail when for example something gets flagged with new API
Note that if this will pass and we declare it as dependency later (in the trigger) then Yamato will just reuse the result of this job so we are not wasting any resources/time here
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Vetting test was generally taking longer to run than the standards test (Standards check is normally 5m, Vetting test is normally 9m). So far, it's also been some thing that fails very rarely.
I also moved the vetting test to a smaller machine than before so it'll get distributed faster. That means the job was running a bit slower again. I was finding it a bit slow to be a quick initial check, and seeing as it shouldn't fail very often, I was thinking it made more sense to run not as a "quick" check.