Azure Cloud Service (extended support) deployment provider

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.
  • There are no “Staging” and “Production” deployments slots anymore - multiple cloud services must be deployed instead.
  • Deployment storage for cloud service packages (.cspkg) could be both “classic” and “general purpose” - migrate to ARM-based “general purpose” at any time after migration.
  • RDP is configured in deployment provider settings. RDP configuration in .csdef and .cscfg is ignored and can be safely deleted.
  • WAD diagnostics is configured in deployment provider settings. WAD configuration in .cscfg is ignored and can be safely deleted. “Diagnostics config” in provider settings is <PublicConfig> node of diagnostics.wadcfgx of cloud service project.
  • SSL certificate is stored in Azure Key Vault.

Let us know if you have any questions.

Thanks, AppVeyor Team

Visual Studio 2019 images update on June 18, 2024

What’s new

  • Chocolatey 2.3.0
  • Cmake 3.29.3
  • Qt 6.7.1
  • 7-zip 24.05
  • PostgreSQL 13.16, 14.12, 15.7, 16.3
  • Powershell 7.4.2
  • Python 3.12.3, 3.11.9
  • Ruby 3.0.7, 3.1.5, 3.2.4, 3.3.1
  • nuget 6.10.0
  • git 2.45.2
  • git-lfs 3.5.1
  • OpenSSL 3.3.1, 3.2.2 3.0.14
  • Node 18.20.3, 20.13.1, 21.7.3, 22.2.0
  • Boost 1.85.0
  • Maven 3.9.6
  • Mercurial 6.6.3
  • LLVM 18.1.6
  • Doxygen 1.11.0
  • MySQL 8.0.37
  • Flutter 3.22.0
  • yarn 1.22.19
  • Google chrome 125.0.6422.76
  • Edge browser 125.0.2535.51
  • Firefox 126.0
  • Chrome webdriver 125.0.6422.76
  • Edge webdriver 125.0.2535.51

Previous worker images

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 2019

You 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:

  • .Net 5
  • Boost 1.78
  • Go 1.13, 1.14, 1.15
  • Python 3.7

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.

Visual Studio 2022 images update on June 13, 2024

What’s new

  • Chocolatey 2.3.0
  • Cmake 3.29.3
  • Qt 6.7.1
  • PostgreSQL 13.16, 14.12, 15.7, 16.3
  • Powershell 7.4.2
  • Ruby 3.0.7, 3.1.5, 3.2.4, 3.3.1
  • Python 3.12.3, 3.11.9
  • dotnet SDK 6.0.422
  • nuget 6.10.0
  • 7zip 24.05
  • git 2.45.2
  • git-lfs 3.5.1
  • OpenSSL 3.3.1, 3.2.2 3.0.14
  • Node 18.20.3, 20.13.1, 21.7.3, 22.2.0
  • Boost 1.85.0
  • Maven 3.9.6
  • Mercurial 6.6.3
  • LLVM 18.1.6
  • Doxygen 1.11.0
  • MySQL 8.0.37
  • Flutter 3.22.0
  • yarn 1.22.19
  • Google chrome 125.0.6422.76
  • Edge browser 125.0.2535.51
  • Firefox 126.0
  • Chrome webdriver 125.0.6422.76
  • Edge webdriver 125.0.2535.51

Previous worker images

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 2022

You 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

This release also comes with an end date of AppVeyor’s support for the following software on these images:

  • .Net 5
  • Boost 1.78
  • Go 1.13, 1.14, 1.15
  • Python 3.7

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.

Visual Studio images update on April 4, 2024

What’s new

  • Qt 6.7.0
  • Cmake 3.29.1
  • NUnit 3.17.0
  • Go 1.22.1, 1.21.8, 1.20.14
  • dotnet SDK 8.0.202
  • OpenSSL 3.2.1, 3.1.5
  • Python 3.11.8, 3.12.2
  • Nuget CLI 6.9.1
  • Powershell 7.4.1
  • Doxygen 1.10.0
  • LLVM 18.1.1
  • Flutter 3.19.3
  • Ruby 3.3.0-1, 3.2.3-1, Ruby 3.2 default in path
  • Boost 1.84.0
  • Edge 123.0.2420.53
  • Firefox 124.0
  • Chrome 123.0.6312.86
  • Firefox driver 0.34.0
  • Edge driver 123.0.2420.53
  • Chrome driver 64-bit 123.0.6312.58

Previous worker images

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 2019
  • Previous Visual Studio 2022

You 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

Ubuntu images update on March 8, 2024

What’s new

  • Python 3.9.18, 3.10.13, 3.11.8, 3.12.2
  • Go 1.19.13, 1.20.14, 1.21.7, 1.22.0
  • Flutter 3.19.2
  • Powershell 7.4.1
  • RabbitMQ 3.13.0-1
  • MySQL 5.7.42 (bionic), 8.0.36 (focal and jammy)
  • Firefox 123.0
  • Chrome 122.0.6261.94-1
  • Qt 6.6.2
  • Git 2.43.2
  • Ruby 2.6.10, 2.7.8, 3.0.6, 3.2.3
  • Node 18.19.1, 19.9.0, 20.11.1, 21.6.2
  • MongoDB 6.0.14
  • JDK 21.0.2
  • LLVM (clang) 15, 16, 17
  • dotnet SDK 8.0.200-1 (focal and jammy)

What’s old

This release also comes with an end date of AppVeyor’s support for the following software on these images:

  • Ubuntu 16.04 (xenial) OS image
  • Python 3.4, 3.5
  • Ruby 2.1, 2.2, 2.3
  • .NET sdks 1.1, 2.1, 2.2
  • OpenJDK 1.7

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.

Previous worker images

There are build worker images available from previous deployment. You can use them in case of any issues with the current images:

  • Previous Ubuntu1804
  • Previous Ubuntu2004
  • Previous Ubuntu2204

You 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
← Older