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>
* Final update copyright headers to reference license files at the repo root
Signed-off-by: spham <spham@amazon.com>
* Fix copyright validator unit tests to support the stale O3DE header scenario
Signed-off-by: spham <spham@amazon.com>
* add repository to ci_build_metrics
* fixing build
* changing the job to pass the right parameters
* passing parameters that need to be expanded
* missed this, important
* fixing typo
* Update the minimum CMake version to 3.20
Sets the cmake_minimum_required calls to version 3.20 and updates the
README.md to point at the general CMake download page instead of a stale
link.
* Remove unnecessary cmake minimum version
It was using an old 3.0 version and can be removed.
* Additional updates to CMake 3.20, build scripts
Updates the version and remove logic to find a CMake in 3rdParty.
* Removing backup path to ninja path in the build_ninja_windows.cmd
The backup path for finding ninja was coming from the Perforce depot which isn't available for o3de builds.
* Removing reference to 3rdParty Android SDK 29 from the build and run unit test script
The Android SDK is not part of the new 3rdParty system and users are expected to install the Android SDK on their own in order to build the engine for Android.
* Update the get_python scripts and README
No longer try to append a CMake path to LY_3RDPARTY_PATH, but do still
support LY_CMAKE_PATH because there are still uses of it. Remove
mention of an LY_3RDPARTY_PATH-relative CMake path from the README.md.
* Removing LY_NINJA_PATH from the build_ninja_windows.cmd
Co-authored-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com>
* Fix quotes
* Revert "Fix quotes"
This reverts commit 29ace5ef2bf1c78991a8cfeb840bfb30c4ce5d8d.
* evaluating the parameters
* Revert "Revert "Fix quotes""
This reverts commit 4f7008e9ccbd5fdc0b33853a4fb1f50285233da9.
* just one eval
* double escaping
* another attempt to happiness
* changing NODE_NAME to LABEL_NAME since that one is more stable and doesnt have spaces
* SPEC-7135 Provide a method to re-trigger compiler detection for changes that require it
* removing check (is wrong and is not necessary)
* Invert existance check
* add empty lines at the end
* Clean is triggering on each build
* clearing if the variable is false
* test code to understand what is going on...
* yeap, looks good
* handling "false" in linux/mac
* fix for linux/mac
* Fixing typos
jonawals
Chris Galvan
AMZN-ScottR
Steve Pham
Gene Walters
scottr
Esteban Papp
jromnoa
mnaumov
jromnoa
Eric Phister