May 03, 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.

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.

April 13, 2015

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!

April 04, 2015

AppVeyor 2.5.5

What’s new

  • #22 Unzip artifacts before uploading to Azure Storage deployment (documentation).
  • #204 Build worker reboot.
  • #207 New: API method to clear project build cache (documentation).
  • #208 Do not fail entire NuGet deployment if symbolsource.org is down.
  • #209 Fixed: GitHub Releases deployment provider fails on invalid auth_token.
  • #210 Add nuget delete command sample to account NuGet page.
  • #218 Delete and create scenario for Azure Cloud Service deployment provider - recreate Azure Cloud Service deployment instead of update. Could be enabled on UI or in appveyor.yml with recreate_deployment: true. Default is false - update mode.
  • #222 Added –non-interactive –trust-server-cert to svn checkout command.
  • #224 Alternative implementation of FTP provider (documentation).

Build worker updates

  • 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.
    • Node.js 0.10.38 x86 is default Node.js in PATH
  • Azure SDK 2.5.1
  • Microsoft Visual Studio Installer Projects extension installed (.vdproj support).
  • Bundler 1.9.2 is pre-installed to all Rubies.
  • Python 2.7.9 replaces Python 2.7.8 in C:\Python27 and C:\Python27-x64.
  • Python 3.4.3 replaces Python 3.4.1 in C:\Python34 and C:\Python34-x64.

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.

March 21, 2015

AppVeyor 2.5.4

What’s new

  • #175 Commit message indentation is not retained.
  • #177 Fixed: Slash is not supported in build version number.
  • #180 Trigger new builds on Visual Studio Online fast forward commits and tag pushes.
  • #181 Fixed: Install-product cmdlet is broken on new Node.js or io.js releases.

  • #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
  • #184 Agent environment settings are sortable now with drag and drop.
  • #187 Added “Tag name” (tag) setting to GitHub deployment provider for separate tag and release name templates.
  • #188 New NuGet deployment provider:
    • Does not rely on nuget.exe
    • Retries pushing package if 500 response status received
    • Does not fail if package already exists
  • #189 Increase file name column on Artifacts page of build results
  • #190 New environment variables to distinguish forced and repetitive builds:
    • APPVEYOR_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.
  • #191 Display build/job start and end times in popup hint over status message.
  • #192 Fixed: “Access is denied” when restoring build cache over read-only items.
  • #193 Azure build worker should use build cache from the same region.
  • #195 Deployment agent: Add skip_dirs, skip_files to “Windows Application” deployment.
  • #197 Fixed: Build cache update fails for dependencies with very long path.
  • #198 Build email notifications are off by default for newly added user/collaborator.
  • #203 Fixed: Web Deploy provider deploying from zip fails on very long paths

Build worker updates

  • 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.
    • Node.js 0.10.37 x86 is default Node.js in PATH
  • xUnit 2.0 runners updated to the latest 2.0.0 RTM.

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.

← Older
Newer →