We’ve introduced new external IPs in AppVeyor build environment - please update your firewalls (if set) as these IPs will start appearing over this week.

IP addresses assigned to build VMs in Google data center (us-central1 region):

104.197.110.30
104.197.145.181

IP addresses assigned to build VMs in LiquidWeb data center (Lansing, MI):

67.225.138.82
67.225.139.18
67.225.139.144
67.225.139.196
67.225.139.220
67.225.139.254
67.227.235.192
67.227.235.194
67.225.251.77
67.225.251.78
67.225.251.79
67.225.251.92
67.225.251.95
67.225.251.96
67.225.251.97
67.225.251.98
72.52.250.157
72.52.251.119

IP address of AppVeyor Cloud in Azure data center (West US region) - when deploying with “Environments”:

138.91.141.243

As always, the most recent and complete list of AppVeyor IP addresses can be found here.

What’s new

• Update version of Ruby 2.2.10
• Update version of Ruby 2.3.7
• Update version of Ruby 2.4.4
• Update version of awscli 1.15.53
• Update version of azure-cli 2.0.41

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 Ubuntu

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

What’s new

• #2508 .NET Core 2.1.2
• #2509 PostgreSQL 9.6.9 and 10.4
• #2510 Fixed: Python 3.7 is missing virtualenv
• #2511 Fixed: Qt latest doesn’t point to 5.11.1
• #2512 Visual Studio 2017 version 15.7.5
• #2513 pwsh.exe should load AppVeyor module on start
• #2515 Visual Studio 2017 version 15.8 Preview 4

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 2015
• Previous Visual Studio 2017

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 2017

What’s new

• #1509 Fixed: Build cache save failure should not affect build status
• #2183 Fixed: Push-AppveyorArtifact doesn’t work with PowerShell Core
• #2263 Fixed: Add-AppveyorTest does not work in PowerShell Core
• #2440 .NET Core 2.1.1
• #2451 Build Agent update
• #2455 Update Qt to use 5.11.1
• #2458 WDK for Windows 10, version 1803 (10.0.17134.1)
• #2470 Ruby 2.5.1-2
• #2471 Ruby 2.4.4-2
• #2475 Python 3.7.0
• #2477 Fixed: The build worker PowerShell module is not loaded by default in PowerShell Core
• #2479 Java 7 SE u80
• #2489 Node.js 6.14.3, 8.11.3, 9.11.2, 10.4.0, 10.4.1, 10.5.0, 10.6.0
• #2491 Python 3.6.6
• #2496 .NET Framework 4.6.2 on Visual Studio 2013 image
• #2502 Qt 5.7 VS 2015 32-bit
• #2503 Visual Studio 2017 version 15.8 Preview 3
• #2494 Fixed: Project name with spaces breaks Octopus deployment

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 2015
• Previous Visual Studio 2017

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 2017

What’s new

• #2469 Fixed: exit 0 causes build to hang in install or build_script
• #2473 Fixed: Linux build agent is not aware of AWS Elastic Beanstalk artifact type
• Update version of NodeJS 6.14.3
• Update version of NodeJS 8.11.3
• Update version of NodeJS 9.11.2
• Update version of pip 10.0.1
• Update version of SQL Server 2017 14.0.3029.16-2
• Update version of awscli 1.15.49
• Update version of localstack 0.8.7
• Update version of azure-cli 2.0.38

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 Ubuntu

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