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:\Ruby22
C:\Ruby22-x64
Chocolatey 0.9.8.33
Chrome 41.0.2272.87
Chrome WebDriver
updated to 2.14
IE WebDriver
updated to 2.45
Erlang OTP runtime 17.4 x64
installed into C:\Program Files\erl6.3
ERLANG_HOME
set to C:\Program Files\erl6.3
C:\Program Files\erl6.3\bin
added to PATH
2.3.24.3
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.
AppVeyor 2.4.22
-IncludeReferencedProjects
option support during automatic packaging of NuGet artifacts. There is a new Include referenced projects
setting on Build tab of project settings and build.include_nuget_references: true|false
in appveyor.yml
deploy.ps1
is now run before service is started, so you have an ability to update its app.config
.service_username
and service_password
settings added to set custom user account to run service under.description
field of GitHub
deployment provider. You can use \n
symbol to separate lines in release description which will be replaced with real LF
symbol during deployment.io.js 1.3.0
and io.js 1.4.1
both x86 and x64 added. Use Install-Product node 1
cmdlet to switch runtime to the latest io.js version.Coverity Scan Build Tool 7.6.0 x64
was added to all workers in C:\Tools\Coverity
. C:\Tools\Coverity\bin
added to PATH
.2.0.0-rc3-build2880
C:\go
path.C:\go-x86
C:\go-x64
symbolic link to C:\go
GOROOT
variable to C:\go
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.
The new build worker image with Visual Studio 2015 CTP 6 + SDK was added.
Image name: Visual Studio 2015 CTP 6
. You can select this image in “OS” dropdown on Environment tab of project settings or set in appveyor.yml
os: Visual Studio 2015 CTP 6
AppVeyor 2.4.21
AppVeyor 2.4.20
APPVEYOR_ACCOUNT_NAME
environment variable to build and deployment contexts.Version
command to appveyor.exe
.deployment_label
settings to Azure Cloud Service deployment provider.Added an ability to use environment variables in build version specification, for example:
environment:
major_version: 1.0
version: $(major_version).{build}
2.0.0-rc2-build2857
C:\go
C:\go-x64
C:\go\bin
to PATH