forked from dotnet/performance
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[main] Update dependencies from dotnet/arcade (#2649)
* Update dependencies from https://github.com/dotnet/arcade build 20221011.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22511.1 * Update dependencies from https://github.com/dotnet/arcade build 20221012.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22512.1 * Update dependencies from https://github.com/dotnet/arcade build 20221013.2 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22513.2 * Update dependencies from https://github.com/dotnet/arcade build 20221020.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22520.1 * Update dependencies from https://github.com/dotnet/arcade build 20221024.5 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22524.5 * Update dependencies from https://github.com/dotnet/arcade build 20221028.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22528.1 * Update dependencies from https://github.com/dotnet/arcade build 20221102.1 Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk From Version 8.0.0-beta.22503.1 -> To Version 8.0.0-beta.22552.1 Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
- Loading branch information
1 parent
3733128
commit 64447d6
Showing
15 changed files
with
127 additions
and
103 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| # Select a pool provider based off branch name. Anything with branch name containing 'release' must go into an -Svc pool, | ||
| # otherwise it should go into the "normal" pools. This separates out the queueing and billing of released branches. | ||
|
|
||
| # Motivation: | ||
| # Once a given branch of a repository's output has been officially "shipped" once, it is then considered to be COGS | ||
| # (Cost of goods sold) and should be moved to a servicing pool provider. This allows both separation of queueing | ||
| # (allowing release builds and main PR builds to not intefere with each other) and billing (required for COGS. | ||
| # Additionally, the pool provider name itself may be subject to change when the .NET Core Engineering Services | ||
| # team needs to move resources around and create new and potentially differently-named pools. Using this template | ||
| # file from an Arcade-ified repo helps guard against both having to update one's release/* branches and renaming. | ||
|
|
||
| # How to use: | ||
| # This yaml assumes your shipped product branches use the naming convention "release/..." (which many do). | ||
| # If we find alternate naming conventions in broad usage it can be added to the condition below. | ||
| # | ||
| # First, import the template in an arcade-ified repo to pick up the variables, e.g.: | ||
| # | ||
| # variables: | ||
| # - template: eng/common/templates/variables/pool-providers.yml | ||
| # | ||
| # ... then anywhere specifying the pool provider use the runtime variables, | ||
| # $(DncEngInternalBuildPool) and $ (DncEngPublicBuildPool), e.g.: | ||
| # | ||
| # pool: | ||
| # name: $(DncEngInternalBuildPool) | ||
| # demands: ImageOverride -equals windows.vs2019.amd64 | ||
|
|
||
| variables: | ||
| # Coalesce the target and source branches so we know when a PR targets a release branch | ||
| # If these variables are somehow missing, fall back to main (tends to have more capacity) | ||
| - name: BranchNameForPoolSelection | ||
| value: ${{ coalesce(variables['System.PullRequest.TargetBranch'], variables['Build.SourceBranch'], 'refs/heads/main') }} | ||
|
|
||
| # Any new -Svc alternative pools should have variables added here to allow for splitting work | ||
|
|
||
| # Main branch pools | ||
| - ${{ if ne(contains(variables['BranchNameForPoolSelection'], 'release'), true) }}: | ||
| - name: DncEngPublicBuildPool | ||
| value: NetCore-Public | ||
| - name: DncEngInternalBuildPool | ||
| value: NetCore1ESPool-Internal | ||
|
|
||
| # Release branch pools | ||
| - ${{ if contains(variables['BranchNameForPoolSelection'], 'release') }}: | ||
| - name: DncEngPublicBuildPool | ||
| value: NetCore-Svc-Public | ||
| - name: DncEngInternalBuildPool | ||
| value: NetCore1ESPool-Svc-Internal |
Oops, something went wrong.