Configuration of release name and distribution

Problem Statement

Currently, the only way to override defaults for the plugin is via SENTRY_RELEASE and SENTRY_DIST environment variables. I believe, this is against the Gradle’s best practices for project configuration, and it creates pratical problems when app version and build number come from the app’s build.gradle file, as there is no clean way to override from within build.gradle the values which Sentry’s Gradle Plugin will get from System.getenv(...) call during configuration.

Solution Brainstorm

I suggest to add a way to provide custom release name and build number to the plugin via gradle properties. I am mostly noob in Gradle and Java, thus I’ll leave implementation details for more knowledgeble people 😃

[marandaneto]

Its already possible to do some sort of config with project.ext.sentryCli on Gradle, so this one can fit in there.

[birdofpreyru]

@marandaneto sure, though as the documentation page you pointed says:

Before disabling the automatic source maps upload, you can set the release and dist as environment variables, SENTRY_RELEASE and SENTRY_DIST respectively. The script that performs the automatic source maps upload will use those values instead the default ones, and they will match the given release and dist. This ensures that the given custom release and dist values are used.

To which I agree, as it is easier just to set these env vars, than to figure out how to correctly configure CLI for source maps upload. And, even if somebody is to upload them manually, the first step for android is to “remove the Gradle integration”, at which point one thinks “why it is not possible to just configure that integration the Gradle way to use desired values” 😉