Fix Azure Pipeline timeouts for build_ci and publish_tag jobs #886
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 Azure Pipeline
build_ciandpublish_tagjobs were failing due to 2-minute timeouts insufficient for their operations.Changes
timeoutInMinutesfrom 2 to 10 minutes in thebuild_cijobtimeoutInMinutesfrom 2 to 5 minutes in thepublish_tagjobThis allows adequate time for the complete CI workflow: package restore → build → NuGet pack → authentication → feed push in the
build_cijob, and for downloading artifacts and publishing to GitHub releases in thepublish_tagjob.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.