September 13, 2015

AppVeyor 3.1.9

What’s new

  • #352 MSYS 2
  • #364 WDK 10 on Visual Studio 2015 build workers
  • #365 Replace node.exe with node.cmd in io.js packages
  • #366 Boost 1.59.0
  • #370 Fixed: BOM is removed by AssemblyInfo patching
  • #371 io.js 3.1.0, 3.2.0, 3.3.0
  • #372 Fixed: AssemblyInfo Patcher ignores AssemblyVersionAttribute
  • #387 Chrome 45.0.2454.85
  • #390 Java 1.8 x64 is in PATH
  • #395 Increase download timeout for VSO repositories
  • #397 ASP.NET and Web Tools 2015 (Beta7) for Visual Studio 2015
  • #398 Fixed: Missing “auth_token” in Slack notification settings causes build to fail silently
  • #400 Fixed: GitHub provider fails without “description” setting specified
  • #402 Node.js 4.0.0
  • #404 NuGet 3.2 RC command line client to Visual Studio 2015 build workers
  • #407 Chrome Driver 2.19 for Selenium testing
  • #408 IE Driver Server 2.47 for Selenium testing
  • #409 FireFox 40.0.3
  • #411 Fixed: Error uploading GitHub release asset
  • #413 Qt Creator updated to v3.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

August 12, 2015

AppVeyor 3.1.0

What’s new

  • SQL Database deployment provider: added support for Azure SQL V12.
  • WebDeploy deployment provider: added support for ASP.NET 5 applications.
  • WebDeploy deployment provider: Pre- and post-sync commands.
  • #355 Coverity Scan 7.7.0
  • #356 JRuby 9.0.0.0 with Bundler 1.10.6
  • #357 NuGet 3.1 (Visual Studio 2015 image only)
  • #358 Boost 1.58.0
  • #359 Miniconda 3.10.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

August 09, 2015

AppVeyor 3.0.12

What’s new

  • #292 Support ASP.NET 5 apps in Web Deploy provider
  • #335 Environment update (VS 2015 only): Windows 10 SDK
  • #339 Fixed: Web Deploy provider throws unfriendly error if more than one artifact found
  • #343 Environment update: GitVersion 3.0.2
  • #344 Added pre- and post-sync commands to Web Deploy provider
  • #346 Environment update: Code Contracts 1.9.10714.2 for Visual Studio 2015 and 2013
  • #347 Environment update (VS 2015 only): MSBuild 14.0 in PATH on Visual Studio 2015 image
  • #348 Environment update (VS 2015 only): Universal Windows App Dev Tools for Visual Studio 2015
  • #349 Environment update (VS 2015 only): WiX 3.10
  • #350 Environment update: io.js 2.4.0, 2.5.0, 3.0.0
  • #354 Environment update: SSDT update for Visual Studio 2013 and 2015 to support Azure V12

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

July 21, 2015

Build environment update summary

  • Visual Studio Community 2015 RTM (“new” OSS environment and new Visual Studio 2015 image)
  • Visual Studio 2015 SDK
  • Xamarin tools
  • Azure SDK 2.7
  • TypeScript 1.5

Visual Studio 2015 RTM

Visual Studio Community 2015 RTM is installed on build workers of new “OSS” environment.

There is also new Visual Studio 2015 image available to all accounts.

Basic, Pro and Premium plans

Paid customers have two ways to build/test with Visual Studio 2015:

  1. Use Visual Studio 2015 image. You can select the image in “OS” dropdown on Environment tab of project settings or set it in appveyor.yml:

    yaml os: Visual Studio 2015

  2. All builds with custom images run on Azure where VMs are slower than those on “Pro” environment. You can send us a request to move your account to new “OSS” environment with fast VMs and Visual Studio 2015 installed.

Free plan

If you see Free (VS 2015) on your plan page then your free account has already been moved to a new faster environment with Visual Studio 2015. If your plan is just Free drop us a line and we’ll move your account over to a new environment!

How to build with MSBuild 14.0

  1. If your project build step is set to “MSBuild” make sure .sln file has # Visual Studio 14 header (not # Visual Studio 2013; otherwise AppVeyor will force MSBuild 12.0.
  2. Add MSBuild 14.0 to PATH with the following command:

    set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%

Xamarin

Xamarin platform has been installed to build workers in both Pro and OSS environments.

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 Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

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

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.

July 13, 2015

AppVeyor 3.0.8

Important update

Warning: The default Node.js version has been changed to 0.12.7 x86 and going forward 0.12.x builds will be default ones.

Use Install-Product node '0.10' cmdlet to switch to the latest 0.10.x version (0.10.40 currently).

Use Install-Product node '0.10.38' cmdlet to switch to the specific (0.10.38 in this example) Node.js version.

Use Install-Product node '' cmdlet to switch to the latest io.js version (2.3.4 currently).

What’s new

  • #217 Environment update: Java 7 Update 79 and Java 8 Update 45 - both JDK and JRE
  • #279 Environment update: Updated pip in all Python installations
  • #288 Deploy specific Azure Cloud Service role
  • #289 Make APPVEYOR_REPO_COMMIT_TIMESTAMP content unambiguous
  • #290 Environment update: Added Qt Installer Framework 2.0.1
  • #296 Environment update: PostgreSQL 9.4
  • #297 Add a “From Name” to the HipChat Integration
  • #309 Environment update: Added node.js 0.10.39, 0.10.40, 0.12.5, 0.12.6, 0.12.7
  • #314 Fixed: Typo “Cannot download GitHub repoitory contents”
  • #318 Environment update: Chocolatey 9.9.8
  • #319 Fixed: Build agent fails to update event log on multiple artifact uploads
  • #320 Fixed: Unable to re-authorize GitHub if revoked on GitHub side
  • #321 Fixed: Patching assembly version doesn’t work if there’s spaces around version parameter
  • #322 Environment update: Qt 5.5
  • #324 Allow 0 for next build number
  • #326 Clone public GitHub repositories with https://
  • #328 Environment update: MongoDB
  • #329 Environment update: Updated Mono 4.0.2 SR2
  • #331 Environment update: Added io.js 2.3.1, 2.3.2, 2.3.3, 2.3.4
  • #332 Environment update: Default Node.js version changed to 0.12.7
    • Use Install-Product node '0.10' cmdlet to switch to the latest 0.10.x version.
  • #333 Deployment Agent - ‘application_path’ setting for virtual directory root

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 Unstable
  • Previous Visual Studio 2014 CTP4
  • Previous Visual Studio 2015 CTP
  • Previous Visual Studio 2015 CTP 6
  • Previous Visual Studio 2015 Preview
  • Previous MinGW

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

Note to “Pro” customers: Whenever custom build worker image is chosen the build will run on Azure, so there is about 3-4 minutes delay before build starts to provision build worker virtual machine.