Temporarily move publishing to Helix build agents - #7404
Merged
Conversation
As seen in dotnet/core-eng#13098 and the linked IcM ticket, we seem to have moved from WIN- to fv- machines and started hitting memory issues.
|
Do we have the capacity for this? 😮 |
Member
Author
Pretty sure in terms of cores and agent capacity we do, other than if you mean monetarily where I have no clue. This is way more expensive than using hosted since it's moving around ADO artifacts. I am simply preparing the PR to have it ready if we want to; it might be something we do via a custom non-main branch like before when the problem was disk space not memory. |
|
Yep makes sense. Was mostly worried about cores and wait times. Maybe this is a good opportunity for another major overhaul for how we do the publishing. I'm sure @epananth would appreciate that. (not) |
epananth
approved these changes
May 19, 2021
1 task
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
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.
As seen in https://github.com/dotnet/core-eng/issues/13098 and the linked IcM ticket, we seem to have moved from WIN- to fv- machines and started hitting memory issues.
To double check: