[don't review][ just testing] fix(telemetry): Defer CLI execution from configuration to execution phase#1187
Draft
runningcode wants to merge 1 commit into
Draft
Conversation
…hase (GRADLE-82) The telemetry ValueSources (SentryCliInfoValueSource and SentryCliVersionValueSource) were spawning sentry-cli processes during configuration phase. Gradle tracked these as configuration cache inputs and re-evaluated them on every build, causing ~38% overhead on large projects. Move CLI execution to the execution phase by: - Using heuristic values (URL-based SaaS detection, BuildConfig version) during configuration instead of calling sentry-cli - Deferring actual CLI calls to the first startTask() invocation via ProcessBuilder, where they enrich telemetry with org and version data - Removing the two ValueSource classes that caused the overhead Fixes GRADLE-82 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
runningcode
changed the title
Contributor
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
### Features
- Defer CLI execution from configuration to execution phase ([#1187](https://github.com/getsentry/sentry-android-gradle-plugin/pull/1187))If none of the above apply, you can opt out of this check by adding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SentryCliInfoValueSourceandSentryCliVersionValueSourcewhich spawnedsentry-cliprocesses during configuration phase, causing Gradle to track them as configuration cache inputs and re-evaluate them on every build (~38% overhead on large projects)BuildConfig.CliVersion) instead of calling sentry-clistartTask()invocation (execution phase) viaProcessBuilder, where the org and exact CLI version are used to enrich telemetry tagsFixes #1100
Fixes GRADLE-82
🤖 Generated with Claude Code