Use latest OPS build tool #1334
Merged
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
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.
Title
Use latest build tool to build content after perf issue fix.
Summary
Yesterday, OPS build has a perf issue which results in build failure. We've fixed it today and revert the workaround to make dotnet/docs use latest build version.
Related LSI 829961: [LSI] [OPS]: OPS builds keep failing for dotnet/docs]
Details
The perf issue has been resolved. Currently all the PRs should pass now. If other users want to validate the PR again, please close and reopen the PR.
Suggested Reviewers
@mairaw