Update pipeline timeouts #735
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
dotnet-buildtools-prereqs-docker-allpipeline is failing due to a timeout in an Ubuntu job. The timeout for the job is 210 minutes which differs from the timeout set in thedotnet-buildtools-prereqs-ubuntupipeline, which is set to 360. Since thedotnet-buildtools-prereqs-docker-allpipeline is intended to handle all OS types, it should have the default set to the highest value amongst all of those OS types which, in this case, is the Ubuntu one. So I've updated the timeout to be 360 for all relevant pipelines that build the entire suite of Dockerfiles.