Visual Studio 2015 image)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.
Paid customers have two ways to build/test with Visual Studio 2015:
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:
os: Visual Studio 2015
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.
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!
.sln file has # Visual Studio 14 header (not # Visual Studio 2013; otherwise AppVeyor will force MSBuild 12.0.Add MSBuild 14.0 to PATH with the following command:
set PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%
Xamarin platform has been installed to build workers in both Pro and OSS environments.
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 R2Previous UnstablePrevious Visual Studio 2014 CTP4Previous Visual Studio 2015 CTPPrevious Visual Studio 2015 CTP 6Previous Visual Studio 2015 PreviewPrevious MinGWYou 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.
AppVeyor 3.0.8
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).
https://Install-Product node '0.10' cmdlet to switch to the latest 0.10.x version.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 R2Previous UnstablePrevious Visual Studio 2014 CTP4Previous Visual Studio 2015 CTPPrevious Visual Studio 2015 CTP 6Previous Visual Studio 2015 PreviewPrevious MinGWYou 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.
AppVeyor 3.0.5
Install-Product node '' to switch to the latest 2.x io.js version.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 R2Previous UnstablePrevious Visual Studio 2014 CTP4Previous Visual Studio 2015 CTPPrevious Visual Studio 2015 CTP 6Previous Visual Studio 2015 PreviewPrevious MinGWYou 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.
AppVeyor 2.6.4
Windows Server 2012 R2) - see sections below for details:Install-Product node '' to switch to the latest 2.x io.js version.Install-Product node '0' to switch to the latest 0.12.x Node.js version.MinGW/MSYS 4.8.2 32-bit has been installed to Default Azure and Pro images (Windows Server 2012 R2).
The following packages were installed:
mingw-get
mingw-developer-toolkit
mingw32-base
mingw32-make
msys-base
gcc
g++
msys-rxvt
msys-unzip
msys-wget
msys-zip
C:\MinGWC:\MinGW\binC:\MinGW\msys\1.0Use C:\MinGW\bin\mingw-get install <package> to install additional packages.
Cygwin has been installed to Default Azure and Pro images (Windows Server 2012 R2).
Cygwin root folder: C:\cygwin
Installer downloaded from https://cygwin.com/setup-x86.exe and available as C:\cygwin\setup-x86.exe
Installed modules:
autoconf
automake
bison
gcc-core
gcc-g++
mingw-runtime
mingw-binutils
mingw-gcc-core
mingw-gcc-g++
mingw-pthreads
mingw-w32api
libtool
make
python
gettext-devel
gettext
intltool
libiconv
pkg-config
git
wget
curl
Installation command used:
C:\cygwin\setup-x86.exe -qnNdO -R C:/cygwin -s http://cygwin.mirror.constant.com -l C:/cygwin/var/cache/setup -P autoconf -P automake -P bison -P gcc-core -P gcc-g++ -P mingw-runtime -P mingw-binutils -P mingw-gcc-core -P mingw-gcc-g++ -P mingw-pthreads -P mingw-w32api -P libtool -P make -P python -P gettext-devel -P gettext -P intltool -P libiconv -P pkg-config -P git -P wget -P curl
Qt has been installed to Default Azure and Pro images (Windows Server 2012 R2).
Online installer: http://download.qt.io/official_releases/online_installers/
Qt root folder: C:\Qt
Installed components:
C:\Qt\5.4C:\Qt\5.4\mingw491_32C:\Qt\5.4\msvc2013_64_openglC:\Qt\5.4\msvc2013_openglC:\Qt\5.3C:\Qt\5.3\mingw482_32C:\Qt\5.3\msvc2013_64_openglC:\Qt\5.3\msvc2013_openglC:\Qt\Tools\mingw482_32C:\Qt\Tools\mingw491_32There 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 R2Previous UnstablePrevious Visual Studio 2014 CTP4Previous Visual Studio 2015 CTPPrevious Visual Studio 2015 CTP 6Previous Visual Studio 2015 PreviewPrevious MinGWYou 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.
AppVeyor 2.6.3
Visual Studio 2015 RC image.Install-Product node '' to switch to the latest 2.x io.js version.unstable image.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 R2Previous UnstablePrevious Visual Studio 2014 CTP4Previous Visual Studio 2015 CTPPrevious Visual Studio 2015 CTP 6Previous Visual Studio 2015 PreviewPrevious MinGWYou 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.