search

sarahsporck / Migration-Test-Repository

This repository is used to test the ticket migration from jira to github
0 stars 1 forks source link

IGAPP-515: Disable Sentry Sourcemap releases for webnext #513

Closed jira-to-github-migrator-test[bot] closed 1 year ago

jira-to-github-migrator-test[bot] commented 1 year ago

Max Ammann - 10.3.2021, 14:09:45

Currently we upload sourcemap releases for every release to webnext. The version code of webnext is not a real one. Therefore this needs to be disabled

Try to use a different version name for webnext releases. Like 2020.3.1-webnext

https://sentry.tuerantuer.org/settings/digitalfabrik/projects/integreat-app/source-maps/web-aschaffenburg%402021.3.3/

Environment: - Linked issues:

jira-to-github-migrator-test[bot] commented 1 year ago

Max Ammann - 30.3.2021, 12:15:51

The original issue is because we are not bumping versions when we are doing development releases to webnext. That means we are uploading different sourcemaps to the same release in sentry. This is not really a big issue as sentry will figure out on which sourcemap the issue happened and use the correct one.

I think we should close the issue and NOT merge this. In fact this is only an issue for aschaffenburg and malte as we do not have different build configs for releases to webnext.malte.app and webnext.aschaffenburg.app.

The proper fix to this issue is probably to include the deployment information for web in the build config. That way we would have different build configs for integreat, malte and aschaffenburg for webnext. Like malte-test-cms and aschaffenburg-test-cms. What do you think about this proper fix?