-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting maxClients for parallelism in yaml #7481
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I don't think we should be moving to hosted machines to run publishing until the changes are already merged due to the nature of dependency flow automation
- Need to at least start with lower numbers if we want to switch to hosted machines
@@ -196,6 +196,10 @@ public string BuildQuality | |||
/// </summary> | |||
public bool UseStreamingPublishing { get; set; } = false; | |||
|
|||
public int StreamingPublishingMaxClients {get; set;} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perhaps a short comment describing why these values are settable is in order.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added a comment with the streaming and non streaming values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comments should be /// < Summary > style and go here
(argh github formatting)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure will update it
eng/publishing/v3/publish-assets.yml
Outdated
@@ -29,8 +29,7 @@ jobs: | |||
# See https://github.com/dotnet/core-eng/issues/13098 for context | |||
${{ if eq(variables['System.TeamFoundationCollectionUri'], 'https://dev.azure.com/dnceng/') }}: | |||
pool: | |||
name: NetCoreInternal-Pool | |||
queue: BuildPool.Server.Amd64.VS2019 | |||
vmImage: 'windows-2019' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I'm mistaken (please correct me if so), these values as set below won't do anything until:
- This change goes in to main
- The Arcade build containing these changes is promoted to use
- An Arcade -> Arcade dependency flow occurs and updates https://github.com/dotnet/arcade/blob/main/eng/Versions.props#L68 to the version of Tasks.Feed containing this change
As such, I think we should hold off using hosted machines until we can actually lower the numbers from default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I changed it back to NetCoreInternal-Pool and kept the numbers as 16 and 12 for now. I am good with changing the numbers after we hit any error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems OK as-is, I'd suggest making the comments look a little different but NBD.
Hello @epananth! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
To double check:
Issue -> https://github.com/dotnet/core-eng/issues/13098
Test -> https://dev.azure.com/dnceng/internal/_build/results?buildId=1175942&view=results