Windows images update on May 30, 2015

AppVeyor 2.6.4

What’s new

  • #253 Fixed: Support hash-bang and other special symbols in build version and branch names.
  • #257 Visual Studio 2015 support in “MSBuild” scenario.
  • #260 Fixed: Cancel build link is shown to users without permissions.
  • #270 Fixed: Generic “Mercurial” provider ignores branch when taking last commit.

Build worker updates

  • WiX 3.9
  • Default Azure and Pro images (Windows Server 2012 R2) - see sections below for details:
  • io.js 2.0.2 and 2.1.0 added to all images. Use Install-Product node '' to switch to the latest 2.x io.js version.
  • Node.js 0.12.3 and 0.12.4 added to all images. Use Install-Product node '0' to switch to the latest 0.12.x Node.js version.

MinGW/MSYS

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
  • MinGW root directory: C:\MinGW
  • MinGW bin directory: C:\MinGW\bin
  • MSYS root directory: C:\MinGW\msys\1.0

Use C:\MinGW\bin\mingw-get install <package> to install additional packages.

Cygwin

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

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:

  • Qt 5.4: C:\Qt\5.4
    • MinGW 4.9.1 (32 bit) OpenGL: C:\Qt\5.4\mingw491_32
    • msvc2013 32-bit OpenGL: C:\Qt\5.4\msvc2013_64_opengl
    • msvc2013 64-bit OpenGL: C:\Qt\5.4\msvc2013_opengl
  • Qt 5.3: C:\Qt\5.3
    • MinGW 4.8.2 (32 bit): C:\Qt\5.3\mingw482_32
    • msvc2013 32-bit OpenGL: C:\Qt\5.3\msvc2013_64_opengl
    • msvc2013 64-bit OpenGL: C:\Qt\5.3\msvc2013_opengl
  • Tools
    • MinGW 4.8.2: C:\Qt\Tools\mingw482_32
    • MinGW 4.9.1: C:\Qt\Tools\mingw491_32

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.

Windows images update on May 12, 2015

AppVeyor 2.6.3

What’s new

  • #263 Fixed: Assembly patching is not picking up a new build version set by Update-AppveyorBuild.
  • #266 Fixed: Display friendly message on artifact upload error.

Build worker updates

  • Azure SDK 2.6 installed to Visual Studio 2015 RC image.
  • AWS CLI 1.7.25 installed to all build worker images.
  • AWS SDK updated to 3.7.606.0 on all images.
  • io.js 2.0.0 and 2.0.1 added to all images. Use Install-Product node '' to switch to the latest 2.x io.js version.
  • Windows Management Framework 5.0 Preview April 2015 installed to unstable image.

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.

Windows images update on May 3, 2015

AppVeyor 2.6.1

What’s new

  • #251 NuGet library updated to version 2.8.5 to allow uploading NuGet packages with DNX dependencies.

Build worker updates

  • NuGet 2.8.5 installed (with support of DNX dependencies)
  • Ruby installations updated:
    • 2.0.0-p645 x86 (C:\Ruby200) with RubyGems 2.0.15
    • 2.0.0-p645 x64 (C:\Ruby200-x64) with RubyGems 2.0.15
    • 2.1.6 x86 (C:\Ruby21) with RubyGems 2.2.3
    • 2.1.6 x64 (C:\Ruby21-x64) with RubyGems 2.2.3
    • 2.2.2 x86 (C:\Ruby22) with RubyGems 2.4.6
    • 2.2.2 x64 (C:\Ruby22-x64) with RubyGems 2.4.6
    • Bundler 1.9.5 is installed for all Ruby versions
  • Azure SDK 2.6

Visual Studio 2015 RC

There is a new Visual Studio 2015 RC build worker image available with Visual Studio Community 2015 RC and Visual Studio 2015 SDK RC.

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

os: Visual Studio 2015 RC

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.

Windows images update on April 25, 2015

AppVeyor 2.6.0

What’s new

  • #26 Allow renaming of NuGet feeds.
  • #130 Deployment agent: Improved reliability of SignalR connection with “heartbeat” loop.
  • #229 Fixed: auth_token must be always defined in appveyor.yml to make Slack notifications work.
  • #230 Fixed: Long build message does not wrap.
  • #234 Fixed: Commit message text is not escaped.
  • #235 Files content type in Azure Blob Deployment.
  • #242 Artifact path with trailing slash in the end is not package as zip.
  • #243 Custom port for SFTP.
  • #245 Deployment agent: Allow changing app pool for web applications (vdirs).

Build worker updates

  • io.js 1.6.4, io.js 1.7.1 and io.js 1.8.1 both x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.
  • Microsoft Visual C++ Compiler for Python 2.7 installed to all build worker images.
  • pip is installed to all Python versions. To use pip add set PATH=C:\<python-dir>\scripts;%PATH% to your build script.
  • virtualenv package installed to all Python versions.

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.

Pro environment upgrade and data center migration

Pro environment build servers have been upgraded with faster hardware. Build workers are featuring the latest Xeon 2690 v3 (Haswell) processors and have 2,500 MB of RAM.

Also, to fix connectivity issues with GitHub build servers were moved to a San-Jose SoftLayer data center.

If you even configured firewall to allow deployments from build workers please update its settings with new build worker IPs:

169.54.128.0/27
169.54.128.128/27

Enjoy!

← Older
Newer →