Try our new extension: Raygun and Visual Studio Team Services

Nick HarleyiOS, Product Updates, Provider Updates1 Comment

Raygun and visual studio team services: how to get setup

We’re always excited when customers get in touch to share their community projects, pull requests on our open source providers, or even just to tell us how they are using Raygun in their own applications. Here, we are pleased to announce a new extension for Raygun and Visual Studio Team Services, straight off the back of the work done by Ivan Lazarov.

Thanks to Ivan we have now made this extension available to be used right away in the Visual Studio Team Services marketplace.

This extension contains a build task which allows for uploading of dSYM files for iOS applications to Raygun from your CI environment. dSYM files are used to symbolicate crash reports, which would otherwise only show memory addresses of objects and methods.

Raygun and Visual Studio Team Services – how to set it up

You’ll need an existing Crash Reporting application already set up in Raygun.

Once you have created a Raygun iOS application for crash reporting, add the Upload Symbols to Raygun task to automate the uploading of dSYM files from a VSTS build definition.

The task for setting up Raygun and Visual Studio Team Services needs to be configured as follows:

  1. Authentication Method (Pick list, Required) – Choose how you would like to authenticate to Raygun. The following methods are supported:
    • Service Endpoint – Use a shared service that has already been set up or can be set up from this screen. The advantage of using a service is that there are no credentials to configure for a particular build – the credential are pre-configured at the service level and can be reused in multiple build definitions.
    • External Access Token – Obtain an External Access Token. You can create this token within your user settings in Raygun, just navigate to https://app.raygun.io/user and check the External Access Token section. Generate a new token if one does not already exist. Remember to use a secret variable for the token if going this route.
    • Username and Password – Use your Raygun username and password as is. Remeber to use a secret variable for password and/or username if going this route.
  2. App ID (String, Required) – To get this ID, either browse to Application settings > dSYM center and copy the last part of the URL path just before /symbols or just browse anywhere within Raygun and check the URL, your App ID will be in there, for example, https://app.raygun.com/settings/xxxxxx/symbols. The xxxxxx is your App ID.
  3. Symbols File Path (String, Required) – Enter a relative path to the dSYM file for iOS.

Configuring Your Raygun credentials

Instead of configuring an External Access Token or Username and Password on every build task, you can configure your credentials globally and refer to them within each build definition as needed. To do this, perform the following steps:

  1. Go into your Visual Studio Team Services or TFS project and click on the gear icon in the upper right corner
  2. Click on the Services tab
  3. Click on New Service Endpoint and select Raygun
  4. Give the new endpoint a name and enter either an External Access Token or the Username and Password for the account which can be reused.
  5. Select this endpoint via the name you chose in #4 whenever you add the Upload Symbols to Raygun task to a build definition

That’s it! You can try out the Raygun and Visual Studio Team Services extension for yourself on Visual Studio’s marketplace here.

Do you have a Raygun community project? We’d like to hear from you – let us know all about it by getting in touch. 

Next level software intelligence across your entire stack.

One Comment on “Try our new extension: Raygun and Visual Studio Team Services”

  1. Pingback: 11 Visual Studio features to turbocharge your coding

Leave a Reply

Your email address will not be published. Required fields are marked *