chore: reduce active polling in code build workflows #13780
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.
Description of changes
This PR removes active polling that was in place to mitigate CodeBuild graph evaluation inefficiencies. Please see #13121 for details about inefficiencies.
These inefficiencies has been adressed and this PR removes most of active polling. The only place with active polling that remains is the job that runs after all e2e tests and needs to await on all job ids. Producing
depends-on
statement for that job must remain in place for now due to us hitting YML file size limits.Issue #, if available
Description of how you validated changes
Kicked off PR and E2E workflows.
Observed that jobs are awaiting on only required ones from previous level of nesting.
See
Checklist
yarn test
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.