|
1 | | -{% metadata_file .yamato/project.metafile %} # All configuration that is used to create different configurations (used in for loops) is taken from this file. |
| 1 | +{% metadata_file .yamato/project.metafile %} |
2 | 2 | --- |
3 | 3 |
|
4 | 4 | # DESCRIPTION-------------------------------------------------------------------------- |
|
10 | 10 | # -accept-apiupdate and asserts that every 2.x type reference was rewritten and none survived. |
11 | 11 | # See apiupdaterproject/README.md. |
12 | 12 |
|
13 | | -# WHY THIS JOB IS MANUAL ONLY----------------------------------------------------------- |
14 | | - # It is deliberately not wired into pr_minimal_required_checks or pr_code_changes_checks. The thing |
15 | | - # it protects only changes when a public editor type is added, moved or removed, so paying a full |
16 | | - # editor import on every PR is not worth it. Kick it off with "/ci apiupdater" in a PR comment |
17 | | - # (see api_updater_pr_checks in _triggers.yml), or from the Yamato UI. |
18 | | - # If it should also run on a schedule, add .yamato/_run-all.yml#run_all_api_updater_tests to |
19 | | - # develop_nightly or develop_weekly_trunk in _triggers.yml. |
20 | | - |
21 | | -# CONFIGURATION STRUCTURE-------------------------------------------------------------- |
22 | | - # Runs on the default platform (Ubuntu) like every other basic job. run_upgrade_test.py is Python, so |
23 | | - # there is no platform constraint - the earlier PowerShell version forced a Windows agent because it |
24 | | - # needed robocopy to purge Library past MAX_PATH. |
25 | | - # A single editor is enough - the job is asserting on the editor's API updater, not on NGO |
26 | | - # behaviour across editor versions. Widen to validation_editors.all if that stops being true. |
27 | 13 |
|
28 | 14 | # TECHNICAL CONSIDERATIONS--------------------------------------------------------------- |
29 | 15 | # apiupdaterproject/Packages/manifest.json references the package by relative path |
|
34 | 20 | # --clean purges Library first: the assertion is meaningless against a warm Library that already |
35 | 21 | # holds rewritten sources from a previous run. |
36 | 22 |
|
37 | | -# QUALITY CONSIDERATIONS-------------------------------------------------------------------- |
38 | | - # The expected type list in run_upgrade_test.py is inline and hand-written. That is fine because |
39 | | - # its input is frozen: it enumerates the 2.x public editor API, and develop-2.0.0 is released. |
40 | | - # TODO: the list does not extend itself. A later relocation within 3.x, or a back port into 2.x, |
41 | | - # has to be added by hand or this job silently stops covering it. Deriving the list from the |
42 | | - # [MovedFrom] attributes in the package source would close that. |
43 | | - |
44 | | -#------------------------------------------------------------------------------------ |
45 | | - |
46 | 23 | {% for platform in test_platforms.default -%} |
47 | 24 | {% for editor in validation_editors.default -%} |
48 | 25 | api_updater_test_{{ platform.name }}_{{ editor }}: |
|
0 commit comments