Increase the CI build timeout while downloading the archive JAR, as n… #475
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…o cache is available and the download takes longer than expected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…o cache is available and the download takes longer than expected.
What changes were proposed in this pull request?
This PR increases the CI workflow timeout for the Docker-based Atlas build.
During the download-archives.sh step, the required archive JARs are downloaded when no GitHub Actions cache is available.
In such cases, the download duration is significantly longer than expected, causing the CI job to exceed the previous timeout limit.
The workflow timeout was increased from 3 hours (180 minutes) to 10 hours (600 minutes).
How was this patch tested?
Through CI build