Fake Build task

Creates a fake XAML-Team Build entry in the TFS database for Team Build (vNext) builds by using TFS API. Fake XAML-Team Build entries are making the new Team Build available for old XAML-build based tools which don't support the new build system. E.g.:MTM 2013, MTM 2012, Release Management Server (before TFS 2015.2) At the moment the FakeBuild task maps only a limited number of Build run fields/data between old and new build system.

Recommendation: Add this build task as the last build step of your build definition.

Requirements

• Visual Studio 2017,2015 or 2013 must be installed on build agent computer.

Configuration

• Add the expected drop location (needs to be a file share and therfore an UNC path)
• Build agent service needs "Edit build information" and "Edit build definition" permission on all XAML Team Builds

Changelog

• Changes since 5.1.66: Added VS 2017 support for TFS API, fixed escaping bug (e.g. whitespace in bug definition name) (thanks Michael Ruminer), improved logging messages, removed preview state
• Changes since 5.2.8 Added information about data protection
• Changes sind 6.0.8 Added support for adding prefix and suffix to Xaml build definition name, fixed links in manifest, added config section names (Common Settings and Advanced), reworked some Powershell functions (make them more stable)

Additional Links

• AIT-Homepage
• AIT TFS-Tools

Privacy information

This extension operates completely locally and does not process any personal data on external computers. For general information on data protection, please refer to our data protection declaration.