Bugsnag Auto Version
An Azure DevOps build task for updating your current Bugsnag AppVersion and notifying bugsnag of your release.
Configure your settings file (appsettings.json)
Your Bugsnag section should look something like this
Set your Version Mask in BAV
For example, if you wanted to automate the patch value. Your mask would look like this: 0.0.$
BAV will start to automatically increment the masked version number on each build.
Increase your AppVersion minor value
BAV will detect the minor version has increased, and reset the patch value back to 0.
Increase your AppVersion major value
BAV will detect the major version has increased, and reset the patch value back to 0.
BAV writes the new version number directly back into your json file, ready for release. The new version is also saved to a variable, which you specify in your build definition's variables tab.
Notify Bugsnag of your release
Once the new version number has been generated and saved, you can choose to notify Bugsnag of your release. This feature makes use of Bugsnag's build api.
Notify Bugsnag of your release further up-stream
If you decide that notifying Bugsnag of your release is a little premature at the build stage, you can opt to use an additional extension, Bugsnag Notify which performs the same notification task, either later in your build, or even from a completely separate release pipeline.
Looking for help getting setup.
Check out the wiki on getting started.
Version Number Madness
Check out the following scenario:
If you find yourself in this scenario, click here to find out how my Azure DevOps extensions can be made to work together to automate this entire process.
Want to notify Bugsnag during release instead of build?
Why not check out my other extensions:
On Visual Studio Marketplace