* Revert to regular run when invalid commits used.
* Cirrect s3 logging of last commit hash storage
* Add s3 top level url and build number script params.
* Use existing REPOSITORY_NAME env var.
Signed-off-by: John <jonawals@amazon.com>
* Define a new Jenkins job to deploy AWS resources
Signed-off-by: junbo <junbo@amazon.com>
* Address PR comments
Signed-off-by: junbo <junbo@amazon.com>
* Add error checking for all the calls
Signed-off-by: junbo <junbo@amazon.com>
* Remove the weekly-build-metrics tag
Signed-off-by: junbo <junbo@amazon.com>
* Parameterize ARN/Region and move it to a Jenkins envvar.
Signed-off-by: junbo <junbo@amazon.com>
* Revert the changes for build_config.json
Signed-off-by: junbo <junbo@amazon.com>
* Fix for PathLib unlink wrong version parameter.
* Fix dst target for TIAF.
* Remove TIAF historic data arhciving on s3 buckets
* Change permissions for TIAF bucket upload
Signed-off-by: John <jonawals@amazon.com>
* Some var cleanup so it shows better-organized in cmake-gui. Some vars were also not following the namign convention we are using
Removed some unnecessary messaging
Fixed a TIF bug where it would report the wrong test in a message, fixed a message that was being triggered
Changed TIF to be enabled just by the binary so running the ci_build scripts locally doesnt trigger TIF messaging
Removed `LY_ENABLE_MULTIPLAYER_COMPRESSION`, it was not being used
Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com>
* handling case where a parameter can be empty
Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com>
* needs to be var name, not contents
Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com>
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
* Add parameters to specify custom native build path and enable unity build in Android gradle builds
* Enable unity build for gradle to shorten the path to the generated object files which fixes build failures on Jenkins due to paths exceeding limit. This also speeds up builds.
jonawals
Junbo Liang
Esteban Papp
Chris Burel
Steve Pham
Chris Galvan
AMZN-ScottR
Gene Walters
scottr
SJ
mbalfour
amzn-hdoke
jromnoa
mnaumov