You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
a3d14e217e
We currently cannot predict when a given snapshot will be taken. This is
problematic as test impact analysis assumes that the coverage data will
be updated after each run. As we have no control over when our coverage
data will persist we will instead always seed when the pipeline and
branch is one of the seeding pipelines, otherwise we will attempt to
read that seed data and perform test impact analysis (if no seed data is
present we will fall back to a regular, uninstrumented run of all test
targets).
This approach has the following implications:
1. PR builds will benefit from test impact analysis as the seed data is
(hopefully) available at the time the snapshot is created.
2. Builds for the aforementioned seeding branches and pipelines will not
benefit from test impact analysis and will incur the cost of seeding
regardless of whether or not that generated seed data ends up in the
snapshot.
Signed-off-by: John <jonawals@amazon.com>
|
5 years ago | |
|---|---|---|
| .. | ||
| asset_windows.cmd | 5 years ago | |
| build_asset_windows.cmd | 5 years ago | |
| build_config.json | 5 years ago | |
| build_installer_windows.cmd | 5 years ago | |
| build_ninja_windows.cmd | 5 years ago | |
| build_test_windows.cmd | 5 years ago | |
| build_windows.cmd | 5 years ago | |
| clean_windows.cmd | 5 years ago | |
| env_windows.cmd | 5 years ago | |
| installer_windows.cmd | 5 years ago | |
| package_build_config.json | 5 years ago | |
| pipeline.json | 5 years ago | |
| python_windows.cmd | 5 years ago | |
| test_windows.cmd | 5 years ago | |