Migrate images-release pipeline to use 1es agents #5459
Conversation
|
Successful test pipeline run: https://msazure.visualstudio.com/One/_build/results?buildId=46476254&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3 |
| - Build-Image -equals true | ||
| - win-rs5 | ||
| - DotNetFramework | ||
| - ImageOverride -equals agent-aziotedge-winserver-2019dc-build |
There was a problem hiding this comment.
Please use Windows Enterprise LST instead of Windows Server.
agent-aziotedge-winserver-2019dc-build -> agent-aziotedge-win10-entn2019-build
There was a problem hiding this comment.
I tried that image initially but the build failed because it did not have Java installed on it. Here's the pipeline run from that attempt: https://msazure.visualstudio.com/One/_build/results?buildId=46366280&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=16be6190-c20b-50b6-8210-aa45e5159981
There was a problem hiding this comment.
Windows Server 2019 is locked to Windows 10.0.17763, just like Windows 10 LTS. agent-aziotedge-winserver-2019dc-build is the right image to use.
There was a problem hiding this comment.
Note we can migrate the MS-hosted agents over to 1ES-hosted as well, and it will give use better response times (we won't be competing with the rest of the org for position in the queue). But the priority right now is removing the maintenance burden of custom agents.
This only affects the Windows job because the Linux jobs use Microsoft hosted agents.