April 12, 2016

NuGet 3.4.2-rc

With this update we deployed NuGet 3.4.2-rc command-line.

While version 3.4.2 fixes many bugs, adds some new features and, in general, looks good for production there are might be some issues (one, two).

To revert NuGet client back to version 3.3.0 add this to your appveyor.yml:

install:
  - ps: iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/install-nuget-3-3-0.ps1'))

What’s new

  • #744 Xamarin 4.0.3.214
  • #745 NuGet 3.4.2-rc command-line for Visual Studio 2015 image
  • #746 Fixed: Adding new private GitLab project fails while configuring Deploy Key

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

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

os: Previous Visual Studio 2015

April 11, 2016

What’s new

  • #719 Cygwin re-installed
  • #721 Visual Studio 2015 Update 2
  • #723 Build should not fail because of cache errors
  • #726 Node 0.12.11-13, 0.10.43-44, 4.4.2, 5.10.0, 5.10.1
  • #728 Git LFS 1.1.2
  • #731 Azure SDK 2.9
  • #734 Ruby 2.3.0
  • #738 Fixed: GitLab: only 20 repositories returned on new project page

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

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

os: Previous Visual Studio 2015

March 26, 2016

Breaking change - Node.js 4.4.1 (LTS) x86 is default Node.js installation

Starting from this update Node.js LTS x86 (currently 4.4.1) will be installed by default on build workers. Before this update there was Node.js 0.12.7 x86 installed by default.

If your project depends on Node.js 0.12.x you can add the following PS command to install section of appveyor.yml (or on UI if you don’t use YML):

install:
  - ps: Install-Product node 0.12

What’s new

  • #688 LLVM 3.8.0 (x64)
  • #690 “GitHub Pull Request” notification provider New!
  • #694 Node.js 4.x (x86) LTS installed by default New!
  • #695 Cygwin x64
  • #695 Cygwin re-installed
  • #697 Fixed: Cancelling rolling branch build cancels all PR builds targeting this branch
  • #698 Qt 5.6 New!
  • #699 NSIS 2.50
  • #701 Node 4.4.1, 5.9.0
  • #703 NUnit 3.2
  • #706 CMake 3.5
  • #707 Fixed: Automatic nuget packaging calls nuget pack for all projects within .nuspec directory
  • #708 Fixed: TFVC repositories are not shown if authorized user doesn’t have access to $/ root
  • #709 Fixed: Slack notification icon is distorted on Mac OS X client
  • #710 Qt Creator 3.6.1
  • #712 F# 2.0

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

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

os: Previous Visual Studio 2015

March 13, 2016

What’s new

  • #487 Show build status in favicon
  • #661 Chrome 49.0.2623.87
  • #662 FireFox 45.0
  • #663 Mono 4.2.2.30
  • #670 Golang 1.6
  • #671 Apache Cordova Update 7 for Visual Studio 2015
  • #673 Fixed: “UpdateVersionDetails” API method does not return descriptive error
  • #675 Fixed: LargeErrorMessage breaks AddTest build worker API
  • #676 Replace “Operating system” notation with “Build worker image”
  • #680 GitHub deployment provider: update release details if exists
  • #682 Trigger builds on pull request “reopened” action
  • #683 Golang 1.5.3 update
  • #684 Node.js 4.3.2, 4.4.0, 5.7.0, 5.7.1, 5.8.0
  • #685 Python Tools for Visual Studio 2015 (December 2015)
  • #687 Unlink profile button for GitHub, BitBucket and VSO

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

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

os: Previous Visual Studio 2013

March 08, 2016

Changing default build worker image to Visual Studio 2015

Visual Studio 2015 was released more than a year ago, time proven on AppVeyor OSS environment and Visual Studio 2015 Update 1 was even released already. More and more customers use Visual Studio 2015 for their new projects and migrating existing projects into it. We at AppVeyor also use Visual Studio 2015 and find it very stable and mature enough to be installed on default build worker image.

Right now default build worker image has only Visual Studio 2013 installed and you have to wait if your project targets Visual Studio 2015 (Visual Studio 2015 is selected in “Build worker image” field of project settings or “os: Visual Studio 2015” added to appveyor.yml).

We are going to change default image to “Visual Studio 2015” for all existing accounts on Friday, March 18th, 2016.

After this change customers having “Visual Studio 2013” in “Build worker image” field on Environment tab of project settings (or “os:” setting in appveyor.yml does not contain “Visual Studio 2015” value, or no “os:” setting at all) will see some queue time increase between 1-2 minutes. This time is required to re-create and re-boot build worker VM with non-default image.

You may need to do a few easy steps below to fix that.

What to do?

Update build worker image to “Visual Studio 2015”

On “Environment” tab of project settings select “Visual Studio 2015” in “Build worker image” dropdown or if you configure your project through appveyor.yml add the following line to the config:

image: Visual Studio 2015

Even if your project targets Visual Studio 2013 or earlier you should still do this step because default image has both Visual Studio 2013 and Visual Studio 2015 installed.

Update path to msbuild.exe

Visual Studio 2015 comes with .NET 4.6.1 and MSBuild 14.0 which are upgrades to .NET 4.0 and MSBuild 12.0 respectively.

If your build calls msbuild.exe without specifying its full path and strongly depends on MSBuild 12.0 you may need to adjust PATH environment variable as “Visual Studio 2015” image has MSBuild 14.0 in PATH.

To change MSBuild path to MSBuild 12.0 add the following line to “Install” section of your project configuration:

for “CMD” mode:

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

for “PS” mode:

$env:PATH="C:\Program Files (x86)\MSBuild\12.0\Bin;$env:PATH"

or add this command in install section of appveyor.yml:

install:
  - set PATH=C:\Program Files (x86)\MSBuild\12.0\Bin;%PATH%

Contact us

If you have any questions or concerns regarding this move please let us know by replying to this email or submitting a new issue on our forums.