July 22, 2017

What’s new

  • #1657 Fixed: PowerShell performance regression
  • #1665 Fixed: * Missing C libraries: eay32, ssl32
  • #1666 Fixed: Start-BitsTransfer is not working
  • #1669 Fixed: Firewall regression for Rust builds
  • #1670 Fixed: Firewall rules regression for connecting SMB shares
  • #1671 Make OpenSSL 1.0.x branch the default option
  • #1672 Removed workaround for api.nuget.org
  • #1673 Centralized mechanism for delivering hotfixes to all build workers
  • #1676 Fixed: CLR Types Error when publishing DACPAC with msdeploy
  • #1677 Fixed: IE Selenium driver error on Visual Studio 2017 image
  • #1678 Visual Studio 2017 version 15.2 (26430.16)

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

July 19, 2017

What’s new

  • #1609 Full installation of OpenSsl on VS 2017 image
  • #1615 Fixed VS2017 regression: “Debugging tools for Windows” (part of Windows SDK) missing
  • #1617 Fixed: Multiple builds for single commit (GitLab)
  • #1619 OpenSSL 1.1.0f
  • #1625 Node.js 4.8.4, 6.11.1, 7.10.1, 8.1.4
  • #1627 Data-Tier Application Framework (17.1 DacFx) on Visual Studio 2017 image
  • #1629 Update VS 2017 Preview image to 15.3 Preview 3
  • #1635 Qt 5.9.1
  • #1639 .NET Framework 4.7 Developer Pack on Visual Studio 2015 image
  • #1641 Visual Studio 2017 version 15.2 (26430.15)
  • #1644 Fixed: NormalizedVersion is not supported in OData requests to NuGet feeds
  • #1648 Coverity Scan 2017.07
  • #1652 TypeScript 2.4.1 for Visual Studio 2015
  • #1660 Modify hosts file before install scripts

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

June 12, 2017

What’s new

  • #648 “Do not sync ACLs” setting for Web Deploy provider
  • #1350 Ruby 2.4.1-1
  • #1435 APPVEYOR_PULL_REQUEST_REPO_NAME and APPVEYOR_PULL_REQUEST_REPO_BRANCH variables
  • #1507 Artifacts: set content-disposition to instruct the browser about the filename
  • #1557 Chocolatey 0.10.7
  • #1576 Yarn 0.24.6
  • #1579 Fixed: UNC paths support regression
  • #1582 Fixed: PsExec regression
  • #1583 Node.js 6.11.0, 8.1.0
  • #1584 Fixed: Ping regression
  • #1585 Bundler v1.15.1
  • #1588 Qt 5.9
  • #1589 Azure PowerShell 4.1.0
  • #1590 Nuget 4.1.0
  • #1591 Azure Service Fabric SDK 2.6
  • #1593 Visual Studio 2017 version 15.2 (26430.13)
  • #1594 Fixed: AppVeyor Build Worker API PowerShell module is not in PSModulePath
  • #1596 CMake 3.8.2
  • #1597 Chrome 59.0.3071.86
  • #1598 Firefox 53.0.3
  • #1599 Chrome Driver 2.30
  • #1602 Fixed: clone_depth not working (on GitLab)
  • #1603 Gecko Driver 0.17.0
  • #1604 Cygwin on Visual Studio 2017 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 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

May 18, 2017

What’s new

  • #1435 APPVEYOR_PULL_REQUEST_REPO_NAME and APPVEYOR_PULL_REQUEST_REPO_BRANCH variables
  • #1479 Fixed: Xamarin regression in Visual Studio 2017
  • #1488 .NET Framework 4.7 support
  • #1490 Fixed: Sporadic “Command exited with code -1” on some Visual Studio 2017 builds
  • #1504 DocumentDB Emulator 1.13.58.2
  • #1507 Artifacts: set content-disposition to instruct the browser about the filename
  • #1517 Fixed: “Privilege not held” error with PowerShell “stop-computer” command on Visual Studio 2017 image
  • #1520 Boost 1.64
  • #1524 SSDT 17.0 (14.0.61704.140) for Visual Studio 2015
  • #1532 WiX Toolset 3.11.0.1701
  • #1533 Git LFS 2.1.0
  • #1535 Fixed: YAML validator doesn’t finish if the configuration is a sequence and contains syntax errors
  • #1537 Node.js 4.8.3, 6.10.3, 7.10.0
  • #1542 Git 2.13
  • #1543 Curl 7.54.0
  • #1544 CMake 3.8.1
  • #1545 Disabled all unnecessary scheduled tasks
  • #1546 Docker base images update (May 2017)
  • #1547 Visual Studio 2017 version 15.2 (26430.06)
  • #1548 .NET Core SDK 1.0.4
  • #1550 Artifact name with spaces
  • #1551 Path to sqlpackage.exe updated on Visual Studio 2015 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 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

April 24, 2017

What’s new

  • #1373 Allow skipping build via Build Worker API
  • #1423 Custom waiting timeout for Agent Deployment environment
  • #1465 Fixed: Trailing slash in cache entry breaks caching
  • #1466 Retry while checking GitHub PR
  • #1469 Documentation on APPVEYOR_BUILD_WORKER_IMAGE
  • #1476 Python 3.6.1
  • #1477 InnoSetup 5.5.9
  • #1482 Git 2.12.2(2)
  • #1487 Azure Web Job deployment with “App Service Environment” option
  • #1498 CMake 3.8
  • #1499 Node.js 4.8.2, 6.10.2, 7.9.0
  • #1500 Fixed: Assembla SVN repository with caret (^) in URL cannot be cloned
  • #1508 .NET Core SDK 1.0.1 and 1.0.3 on Visual Studio 2017 image should be pre-cached
  • #1509 Fixed: Build cache save failure should not affect build status
  • #1515 Fixed: Wrong version of AWSSDK.Core used when called from PS script
  • #1516 Docker images update (April)

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