[ci] Use new 1ES Hosted win2019 Pool #6063
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
pjcollins
force-pushed
the
cloudtest-win-2019
branch
from
980eada to
5b99d3a
Compare
Context: https://www.1eswiki.com/wiki/1ES_hosted_AzureDevOps_Agents We've been tasked with migrating away from our scale set agent pools to a new 1ES service. There are a couple of benefits to using 1ES agent pools. We should now be able to use customizable versions of the [Microsoft-hosted agent images][0] which come preloaded with some of our dependencies. These images are also updated regularly which should hopefully reduce maintenance costs. Overall, the process for creating, updating, and rolling out image changes to our scale set agent pools should now be dramatically simplified over [the existing workflow][1]. Visual Studio update steps have been removed as these images should stay up to date with the latest stable VS, similar to the Microsoft-hosted images. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml [1]: https://github.com/xamarin/monodroid/wiki/Azure-Pipelines-and-DevOps#windows-scale-set-agent-pool-management
pjcollins
force-pushed
the
cloudtest-win-2019
branch
from
5b99d3a to
1d1ed30
Compare
jonathanpeppers
approved these changes
Jul 7, 2021
dellis1972
approved these changes
Jul 7, 2021
jonpryor
pushed a commit
to jonpryor/xamarin-android
that referenced
this pull request
Aug 25, 2021
Context: https://www.1eswiki.com/wiki/1ES_hosted_AzureDevOps_Agents We've been tasked with migrating away from our scale set agent pools to a new 1ES service. There are a couple of benefits to using 1ES agent pools: we should now be able to use customizable versions of the [Microsoft-hosted agent images][0] which come preloaded with some of our dependencies. These images are also updated regularly which should hopefully reduce maintenance costs. Overall, the process for creating, updating, and rolling out image changes to our scale set agent pools should now be dramatically simplified over [the existing workflow][1]. Visual Studio update steps have been removed as these images should stay up to date with the latest stable VS, similar to the Microsoft-hosted images. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml [1]: https://github.com/xamarin/monodroid/wiki/Azure-Pipelines-and-DevOps#windows-scale-set-agent-pool-management
jonpryor
pushed a commit
that referenced
this pull request
Aug 26, 2021
Context: https://www.1eswiki.com/wiki/1ES_hosted_AzureDevOps_Agents We've been tasked with migrating away from our scale set agent pools to a new 1ES service. There are a couple of benefits to using 1ES agent pools: we should now be able to use customizable versions of the [Microsoft-hosted agent images][0] which come preloaded with some of our dependencies. These images are also updated regularly which should hopefully reduce maintenance costs. Overall, the process for creating, updating, and rolling out image changes to our scale set agent pools should now be dramatically simplified over [the existing workflow][1]. Visual Studio update steps have been removed as these images should stay up to date with the latest stable VS, similar to the Microsoft-hosted images. [0]: https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml [1]: https://github.com/xamarin/monodroid/wiki/Azure-Pipelines-and-DevOps#windows-scale-set-agent-pool-management
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Context: https://www.1eswiki.com/wiki/1ES_hosted_AzureDevOps_Agents
We've been tasked with migrating away from our scale set agent pools to
a new 1ES service. There are a couple of benefits to using 1ES agent
pools. We should now be able to use customizable versions of the
Microsoft-hosted agent images which come preloaded with some of our
dependencies. These images are also updated regularly which should
hopefully reduce maintenance costs. Overall, the process for creating,
updating, and rolling out image changes to our scale set agent pools
should now be dramatically simplified over the existing workflow.
Visual Studio update steps have been removed as these images should stay
up to date with the latest stable VS, similar to the Microsoft-hosted
images.
The new Azure Resource for this pool can be found here.