Feature release: Link back to source from GitHub, Bitbucket and GitLab

| 2 min. (349 words)

Raygun Crash Reporting gives you the deep diagnostic details you need in to fix an error quickly and efficiently. When an error is thrown by your application, the error details arrive in your dashboard under the ‘Summary’ tab where you can find the stacktrace details for a fast fix.

Having this information available is really important for efficient error management, however, some of our customers need better access to the stacktrace information for a faster fix. For example, you may find moving between your repository and your stacktrace information tedious and messy, especially when dealing with lots of files and having to copy and paste the path.

Raygun Crash Reporting has made this easier by creating a link back to source for GitHub, Bitbucket and GitLab to make error resolution easier and faster. An extra bonus is that if you also have deployment tracking set up in Raygun Crash Reporting these links back to the source will also point to the correct revision of the code in your hosting service.

Before we get started, it’s important to ensure that your Raygun Crash Reporting application is integrated with your web-based hosting service for source code. If not, here are the detailed instructions:

When you have integrated your source code service, you’ll be able to see the link back to source inside the Raygun Crash Reporting stacktrace information. Here’s where to find the link for GitHub, Bitbucket and GitLab:

Whether you use GitHub, Bitbucket or GitLab as your hosting service, getting the information you need for a fast fix is even easier. With GitHub, GitLab and Bitbucket links back to source, opening the frame information in separate browser tabs allows for faster movement between the high level overview and stacktrace information. No need to get lost when resolving errors – the source code is now integrated to your stacktraces.

Do you need help setting up link back to source? Get in touch with a friendly team member here. We’d be happy to help.