How to use HockeyApp with Visual Studio Team Services (VSTS) or Team Foundation Server (TFS)

You can integrate HockeyApp directly in Visual Studio Team Services (VSTS) and in Team Foundation Server (TFS) to upload your Android, iOS, and Mac OS X builds as well as Windows Phone apps. Support file types are .ipa, .apk, .app.zip, .appx, .appxbundle, .zip (if it contains an .appx or .appxbundle), .dSYM.zip, and mapping.txt for Android symbols. If you need support for Windows builds that are packaged as a .zip file, please check out this 3rd-party task.

Installation for VSTS

Use the HockeyApp extension for Visual Studio Team Services to configure secure integration enabling continuous deployment, work item management, and dashboard integration with Visual Studio Team Services. To install the extension, follow these steps:

Installation for TFS

Prerequisites

In order to deploy the HockeyApp extension in your TFS instance, you need to update to TFS 2015 Update 2 or newer.

Deployment

Download the HockeyApp extension from the VS Marketplace. Make sure to use the Download button, not the Install button.

Navigate to the Team Foundation Server Extensions page on your server, for example http://someserver:8080/tfs/_gallery/manage.

Click Upload new extension and select the file you have just downloaded.

After the extension has successfully uploaded, click Install and select the Team Project Collection to install into.

Upload Builds (VSTS and TFS)

Once the HockeyApp extension or build is deployed, you should see a new build step named "HockeyApp" under the Deploy group inside Build Steps. After you add it, configure it with these required parameters:

HockeyApp Connection: Choose the service endpoint you created earlier.

App ID: This identifier is available in the HockeyApp web portal after you create the app. Find more details on creating a new app here.

Binary File Path: The app package to be uploaded. If you are building the app in a preceding build step, ensure you enter a relative path to the app package; for example, $(Agent.ReleaseDirectory).

Optional parameters:

Symbols File Path: The symbol package to be uploaded. If you are building the app in a preceding build step, ensure you enter a relative path to the dSYM file for iOS & Mac apps, to the mapping.txt or symbols.zip for Android, or to the folder with all .pdb files for a UWP app.

Native Library File Path: This optional parameter can be set to a .zip file with all unstripped .so files on Android. HockeyApp will then dump the symbols from those .so files.