November 06, 2015

Important updates

A single continuous-integration/appveyor GitHub commit status was replaces with two separate statuses: continuous-integration/appveyor/branch and continuous-integration/appveyor/pr for regular “push” and PR builds respectively.

If you have protected GitHub branches checking AppVeyor status please update them now to use new continuous-integration/appveyor/pr status.

What’s new

  • #286 Visual Studio 2012 Update 5
  • #384 Separate GitHub commit statuses for branch and PR builds
  • #456 Go 1.5.1
  • #460 ASP.NET 5 Beta 8
  • #463 Python 2.6
  • #465 Java 8 update 66
  • #468 Git Large File Storage
  • #472 Node.js 4.2.0, 4.2.1, 4.2.2, 5.0.0
  • #474 Allow overriding settings in Environment deployment provider
  • #476 Add SqlPackage.exe to PATH
  • #480 Overwrite assets in GitHub deployment provider
  • #481 Visual Studio 2015 Installer Projects
  • #483 F# 4.0 RTM for Visual Studio 2015
  • #488 Node.js tools for Visual Studio 2013 and 2015
  • #489 Python tools for Visual Studio 2013

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 Windows Server 2012 R2
  • Previous Visual Studio 2015

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

October 10, 2015

AppVeyor 3.3.0

What’s new

  • #92 JUnit test results support
  • #440 Visual Studio 2008 strong name
  • #443 Xamarin license activation/deactivating for PR builds
  • #444 CMake 3.3.2
  • #446 ODBC drivers for PostgreSQL, MySQL
  • #447 Fixed: Wrong encoding of spaces in GitHub commit status build URL
  • #450 Node.js 4.1.2
  • #451 WiX 3.10
  • #452 Skip non-tag builds
  • #453 Azure SDK 2.7.1

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 Windows Server 2012 R2
  • Previous Visual Studio 2015

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

September 28, 2015

AppVeyor 3.2.0

What’s new

  • #368 Ruby 2.2.3, 2.1.7, and 2.0.0-p647 + Bundler 1.10.6
  • #433 Fixed: Original encoding (BOM) is not preserved in assembly patcher
  • #434 Node.js 4.1.1
  • #435 Fixed: Build URL is not encoded on GitHub pull request details

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 Windows Server 2012 R2
  • Previous Visual Studio 2015

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2

September 27, 2015

On September 30, 2015 7:00-13:00 UTC networking engineers in AppVeyor data center will be performing router firmware upgrade. During this maintenance window they do expect a disruption to AppVeyor build servers network connectivity of a few minutes as the new firmware is being applied.

If you have any problems with your builds after that time please let us know.

We appreciate your patience during this work.

Best regards,
AppVeyor team

September 20, 2015

AppVeyor 3.1.10

What’s new

  • #414 WDK 10 “include” directory renamed on Visual Studio 2015 images
  • #420 Windows 10 Apps Tools version 1.1
  • #421 TypeScript 1.6.3
  • #422 Node.js 4.1.0
  • #423 Fixed: Deployment conditions fail on the empty string
  • #424 NuGet 3.2 on Visual Studio 2015 images
  • #425 Qt 5.4.2
  • #428 Python 3.5

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 Windows Server 2012 R2
  • Previous Visual Studio 2015

You can select build worker image in OS dropdown on Environment tab of project settings or if you use appveyor.yml:

os: Previous Windows Server 2012 R2