Rollback setup-dotnet action #940
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
|
Contributor
Author
|
Opened this Issue for the folks that own this action to hopefully figure out what's going on: actions/setup-dotnet#410 |
ArinGhazarian
approved these changes
Apr 4, 2023
This was referenced Jun 26, 2023
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.
ThirdPartyNotices.txt(if applicable)When we upgraded the setup-dotnet action from v1 to v3 yesterday it caused our builds to get significantly longer (3.5min -> 8.5 min for one job).
I narrowed it down to something specifically in v3.0.0 of that action. I will open an issue for the team that owns that action to hopefully help us shed some more light on what's going on, in the meantime this PR rolls us back to v2.