November 18, 2017

Breaking changes

  • Qt 5.9.1 (C:\Qt\5.9.1) has been replaced with Qt 5.9.2 (C:\Qt\5.9.2).
  • Miniconda3 3.16.0 (Python 3.4.3) is now installed into C:\Miniconda34 directory (x64 to C:\Miniconda34-x64 respectively), and C:\Miniconda3 is now mapped to the latest Miniconda3 4.3.27 (Python 3.6.2).

What’s new

  • #1554 WDK for Windows 10, version 1709 on Visual Studio 2017 image
  • #1778 LLVM 5.0
  • #1841 SQL Server 2017 Developer edition
  • #1847 Boost 1.65.1
  • #1868 .NET 4.7.1 support
  • #1872 Java 8 Update 152
  • #1875 Fixed: Git clone over HTTPS times out
  • #1880 Node.js 4.8.5, 4.8.6, 6.11.5, 6.12.0, 8.8.0, 8.8.1, 8.9.0, 8.9.1, 9.0.0, 9.1.0, 9.2.0
  • #1881 Fixed: .sh extension is not properly mapped on VS 2017 image
  • #1883 Qt 5.9.2
  • #1892 Re-install all Ruby versions to avoid duplicate gems
  • #1897 Miniconda3 default installation is ancient, updating not always possible
  • #1901 Yarn 1.3.2
  • #1902 SSDT 15.4.0 preview for Visual Studio 2017 Preview (Visual Studio 2017 Preview image)
  • #1909 TypeScript 2.6 for Visual Studio 2015/2017
  • #1912 Cygwin/GDB x64 crash on execute.
  • #1914 PostgreSQL 10.1
  • #1921 NUnit 3.8.1 and NUnit Console 3.7
  • #1925 The built-in vcpkg needs to be updated.
  • #1926 Bundler 1.16.0
  • #1927 Go 1.8.5, 1.9.2
  • #1928 CMake 3.9.6
  • #1933 Visual Studio 2017 15.4.4
  • #1934 Visual Studio 2017 15.5.0 Preview 4.0 (Visual Studio 2017 Preview image)
  • #1935 .NET Core SDK 2.0.3 on Visual Studio 2015/2017 images

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

October 22, 2017

What’s new

  • #1496 Fixed: Do not parse .vdproj as XML
  • #1737 Bundler v1.15.4
  • #1746 Fixed: Unable to load multiple test assemblies with the same name from different folders
  • #1750 [Feature request] Patching support for .props files
  • #1753 Fixed: Forward slash in ‘clone_folder’ breaks artifacts packaging
  • #1758 Fixed: Backward slashes do not work in custom YAML path
  • #1759 Fixed: Exclude .NET Core test projects from automatic nuget packaging
  • #1764 Avoid NuGet packaging duplication if ‘GeneratePackageOnBuild’ is set
  • #1766 Expose a retry for Azure WebJobs deployment
  • #1770 Python 3.6.3
  • #1772 AssemblyVersion, FileVersion, InformationalVersion to .csproj patching
  • #1773 VDPROJ support on Visual Studio 2017
  • #1780 Miniconda2 4.3.27, Miniconda3 4.3.27
  • #1781 Add app_offline support to Deployment Agents
  • #1782 Fixed: Built-in Bash support is broken
  • #1783 Qt Installer Framework 3.0.1
  • #1785 TypeScript 2.5.2 for Visual Studio 2015/2017
  • #1786 Fixed: VSTS - Commit Number URL is Incorrect on Build Page
  • #1789 Fixed: Clone tag if specified in webhook ref field
  • #1790 RubyInstaller-2.4.2-2 available
  • #1793 Java 8 Update 144
  • #1794 Python 2.7.14
  • #1799 Update MSYS64
  • #1802 CMake 3.9.4
  • #1803 Unable to add AppVeyor to Github organization
  • #1806 NuGet feed API key reset in UI
  • #1809 “Bleeding” environment variables of different artifact type
  • #1811 .NET Core .csproj files patching on .fsproj (F# Project)
  • #1818 NuGet 4.3
  • #1822 Fixed: wget doesnt work in MSYS2 anymore
  • #1825 Fixed: Error 400 returned by nuget publishing for some customers
  • #1826 Fixed: docker-compose.exe is missing from Visual Studio 2017 image
  • #1829 Node.js 6.11.3, 8.5.0, 8.6.0
  • #1830 docker-compose 1.16.1
  • #1832 Qt 5.9.1 msvc2015 32-bit on Visual Studio 2017 image
  • #1833 Azure Service Fabric SDK 2.8
  • #1835 Chrome 61
  • #1836 Firefox 56
  • #1837 ChromeDriver 2.32
  • #1838 IE Driver 3.6.0
  • #1840 Docker images update to 10.0.14393.1715 and .1770
  • #1844 Go 1.8.4 and Go 1.9.1
  • #1851 Visual Studio 2017 15.4
  • #1852 Yarn 1.2.1
  • #1860 Node.js 6.11.4, 8.7.0
  • #1866 Windows SDK 10.0.16299.0 (Fall Creator’s Update SDK)
  • #1867 .NET Core SDK 2.0.2 on Visual Studio 2017 image
  • #1869 Fixed: Default NuGet feed list has old protocol endpoint on VS 2017 image
  • #1870 Fixed: The current py.exe on AppVeyor is inherently broken

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

September 07, 2017

What’s new

  • #1076 vcpkg (Microsoft VC++ Packaging Tool)
  • #1083 Customize commit status context on project level
  • #1655 Git LFS 2.2.1
  • #1656 Docker: multi-stage builds
  • #1683 Visual Studio 2017 15.3.3
  • #1685 Go 1.7.6, 1.8.3
  • #1748 Go 1.9
  • #1695 CMake 3.9.1
  • #1702 Azure Storage Emulator 5.2
  • #1710 Fixed: .csproj patching mistakenly skips files with TargetFrameworks tag
  • #1713 Git for Windows 2.14.1
  • #1714 Node.js 6.11.2, 8.4.0
  • #1715 Disable new network location wizard
  • #1716 Configurable repository in GitHub Releases deployment
  • #1718 NSIS 3.02.1
  • #1721 DirectX SDK on Visual Studio 2017 image
  • #1722 curl 7.55.1
  • #1723 Chrome 60.x
  • #1724 Chrome driver 2.31
  • #1725 Gecko driver 0.18.0
  • #1726 Firefox 55.0.2 (32-bit)
  • #1727 Selenium IE driver 3.5.0
  • #1729 .NET Core SDK 2.0
  • #1730 Add an option to enable saving cache in pull request builds
  • #1742 .NET Core SDK 2.0.0 runtime x86 into Visual Studio 2017 image
  • #1747 InnoSetup 5.5.9 on Visual Studio 2017 Image
  • #1762 Docker 17.06.1-ee-2
  • #1763 Docker images update (August 2017)
  • #1775 Azure Service Fabric SDK 2.7

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 Visual Studio 2013
  • Previous Visual Studio 2015
  • Previous Visual Studio 2017

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

os: Previous Visual Studio 2015

September 04, 2017

What’s new (Visual Studio 2017 image only)

The following changes were applied to Visual Studio 2017 image only:

  • #1762 Docker 17.06.1-ee-2
  • #1763 Docker images update (August 2017)
  • #1656 Docker: multi-stage builds
  • #1683 Visual Studio 2017 15.3.3
  • #1714 Node.js 8.4.0
  • #1742 .NET Core SDK 2.0.0 runtime x86 into Visual Studio 2017 image
  • #1747 InnoSetup 5.5.9 on Visual Studio 2017 Image
  • #1748 Go 1.9

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 Visual Studio 2017

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

image: Previous Visual Studio 2017

August 17, 2017

What’s new (Visual Studio 2017 image only)

The following changes were applied to Visual Studio 2017 image only:

  • #1683 Visual Studio 2017 15.3.0
  • #1729 .NET Core SDK 2.0
  • #1076 vcpkg (Microsoft VC++ Packaging Tool)
  • #1655 Git LFS 2.2.1
  • #1685 Go 1.7.6, 1.8.3
  • #1695 CMake 3.9.1
  • #1702 Azure Storage Emulator 5.2
  • #1710 Fixed: .csproj patching mistakenly skips files with TargetFrameworks tag
  • #1713 Git for Windows 2.14.1
  • #1714 Node.js 6.11.2, 8.3.0
  • #1718 NSIS 3.02.1
  • #1721 DirectX SDK on Visual Studio 2017 image
  • #1722 curl 7.55.1
  • #1723 Chrome 60.x
  • #1724 Chrome driver 2.31
  • #1725 Gecko driver 0.18.0
  • #1726 Firefox 55.0.2 (32-bit)
  • #1727 Selenium IE driver 3.5.0

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 Visual Studio 2017

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

image: Previous Visual Studio 2017