This PR brings support of so-called build ID, which will allow us to precisely match stacktrace sent to Datadog with a mapping file.
This is achieved by generating build ID with each build, so that it can be added to the mapping file upload metadata and also stored as a file in the assets folder of the application which is going to be built, so that it can be later read by the SDK in runtime and added to the RUM/Logs errors.
Review checklist (to be filled by reviewers)
[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
What does this PR do?
This PR brings support of so-called build ID, which will allow us to precisely match stacktrace sent to Datadog with a mapping file.
This is achieved by generating build ID with each build, so that it can be added to the mapping file upload metadata and also stored as a file in the
assets
folder of the application which is going to be built, so that it can be later read by the SDK in runtime and added to the RUM/Logs errors.Review checklist (to be filled by reviewers)