Do not rebuild Stack AMI when not needed #1681
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We do rebuild Stack AMI for Elastic CI Stack every single time, even when nothing in the AMI changes (e.g. agent version, related config, anything).
If we update README, CloudFormation template or anything outside of AMI, we should use AMI from the latest release instead. This should significantly reduce pipeline execution time – while Linux AMI builds in around 4-5 minutes, Windows takes about 20 minutes.
Description
Checklist
Release Notes