Scripts wait longer for builds to ingest when --fail-if-not-fully-cacheable
is used
#791
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.
This change adds the
--availability-wait-timeout
option to the build scan summary tool invocation with a value of '60' when the--fail-if-not-fully-cacheable
option is used.This should increase the likelihood of experiment build scans being ingested in order to retrieve the required data from the Develocity API to determine cacheability.
The

availabilityWaitTimeoutSecs
query parameter is included on the Develocity API calls when the--fail-if-not-fully-cacheable
option is included in the script invocation.When the

--fail-if-not-fully-cacheable
option isn't included, noavailabilityWaitTimeoutSecs
parameter is included in the Develocity API call.Closes #505