AppVeyor 2.6.0
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.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.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.
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!
AppVeyor 2.5.5
auth_token.appveyor.yml with recreate_deployment: true. Default is false - update mode.io.js 1.6.2, io.js 1.6.3 x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.Node.js 0.10.38, Node.js 0.12.2 x86 and x64 added. Use Install-Product node 0 cmdlet to switch runtime to the latest Node.js version or Install-Product node 0.10 to the latest 0.10.x build.PATH.vdproj support).C:\Python27 and C:\Python27-x64.C:\Python34 and C:\Python34-x64.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.5.4
#183 Slack incoming webhooks support. In appveyor.yml Slask notification provider could be configured to use incoming webhook:
- provider: Slack
incoming_webhook: http://incoming-webhook-url
# ...or as before using auth token
- provider: Slack
auth_token:
secure: kBl9BlxvRMr9liHmnBs14A==
channel: development
tag) setting to GitHub deployment provider for separate tag and release name templates.nuget.exeAPPVEYOR_FORCED_BUILD (True or undefined) - builds started by “New build” button or from the same API.APPVEYOR_RE_BUILD (True or undefined) - build started by “Re-build commit/PR” button of from the same API.skip_dirs, skip_files to “Windows Application” deployment.io.js 1.6.1 x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.Node.js 0.10.37 x86 and x64 added. Use Install-Product node 0 cmdlet to switch runtime to the latest Node.js version or Install-Product node 0.10 to the latest 0.10.x build.PATHThere 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.5.0
<something>.yml file for project configuration. Now you can specify your own name of .yml file on “General” tab of project settings - it will be used instead of appveyor.yml.#131 Added environment variable support in build.project setting, so you can setup solution or project name to build in environment variable, for example:
environment:
my_project: MyApp.sln
build:
project: $(my_project)
io.js 1.5.0, io.js 1.4.2 and io.js 1.4.3 both x86 and x64 added. Use Install-Product node 1 cmdlet to switch runtime to the latest io.js version.Ruby 2.0.0 updated to build p643.Ruby 2.2.1 installed:C:\Ruby22C:\Ruby22-x64Chocolatey 0.9.8.33Chrome 41.0.2272.87Chrome WebDriver updated to 2.14IE WebDriver updated to 2.45Erlang OTP runtime 17.4 x64 installed into C:\Program Files\erl6.3ERLANG_HOME set to C:\Program Files\erl6.3C:\Program Files\erl6.3\bin added to PATH2.3.24.3There 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.