There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Visual Studio 2022You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:
image: Previous Visual Studio 2022
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Visual Studio 2019You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:
image: Previous Visual Studio 2019
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Ubuntu1804Previous Ubuntu2004Previous Ubuntu2204You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:
image: Previous Ubuntu
Azure Cloud Service (extended support) deployment provider has been released to production.
Just a reminder, Azure Cloud Service (classic) deployments must be migrated to Azure Cloud Service (extended support) before August 31, 2024.
Azure Cloud Service (extended support) provider documentation
Some notable differences of “extended support” provider from “classic”:
.cscfg file: <NetworkConfiguration> section must be added..csdef file: Small, Medium, Large, etc. machine sizes must be changed to Standard_* sizes from “Standard” tier..cspkg) could be both “classic” and “general purpose” - migrate to ARM-based “general purpose” at any time after migration..csdef and .cscfg is ignored and can be safely deleted..cscfg is ignored and can be safely deleted. “Diagnostics config” in provider settings is <PublicConfig> node of diagnostics.wadcfgx of cloud service project.Let us know if you have any questions.
Thanks, AppVeyor Team
There are build worker images available from previous deployment. You can use them in case of any issues with the current images:
Previous Visual Studio 2019You can select build worker image in “Build worker image” dropdown on Environment tab of project settings or if you use appveyor.yml:
image: Previous Visual Studio 2019
This release also comes with an end date of AppVeyor’s support for the following software on these images:
As of the next image update the above libraries will no longer be available. Please update your build configurations accordingly, bearing in mind that you can switch your configuration to use previous image to extend the use of the removed software if need be.