Problem Statement
Summary
Sentry cannot reliably apply repository CODEOWNERS to JVM stack frames when package/module paths do not correspond directly to repository paths. Provide a first-party way to map JVM frames to repository-owned files so Java, Kotlin, and Scala projects can use automatic issue ownership without maintaining custom CI scripts.
Problem
JVM stack frames identify classes through package and module paths, while CODEOWNERS rules target repository file paths. In monorepos, paths may also include module-specific prefixes such as service-a/src/main/java/, and multiple modules may contain identical package paths.
Without a reliable mapping, issues remain unowned or are assigned incorrectly. The current workaround—generating Sentry Ownership Rules from CODEOWNERS in customer CI—is unsupported, difficult to maintain, and hard to validate. Repeated misassignment also reduces trust in automatic ownership.
Requirements
Resolve supported JVM stack frames to the correct repository path when a unique mapping exists.
Apply existing CODEOWNERS semantics to that resolved path.
Support monorepos, including duplicate or ambiguous package paths.
Keep ownership current when CODEOWNERS, modules, or mappings change, without manual regeneration.
Surface unmatched and ambiguous in-app frames with an actionable reason.
Do not require customer-maintained translation scripts.
Solution Brainstorm
No response
Product Area
Issues
Problem Statement
Summary
Sentry cannot reliably apply repository CODEOWNERS to JVM stack frames when package/module paths do not correspond directly to repository paths. Provide a first-party way to map JVM frames to repository-owned files so Java, Kotlin, and Scala projects can use automatic issue ownership without maintaining custom CI scripts.
Problem
JVM stack frames identify classes through package and module paths, while CODEOWNERS rules target repository file paths. In monorepos, paths may also include module-specific prefixes such as service-a/src/main/java/, and multiple modules may contain identical package paths.
Without a reliable mapping, issues remain unowned or are assigned incorrectly. The current workaround—generating Sentry Ownership Rules from CODEOWNERS in customer CI—is unsupported, difficult to maintain, and hard to validate. Repeated misassignment also reduces trust in automatic ownership.
Requirements
Resolve supported JVM stack frames to the correct repository path when a unique mapping exists.
Apply existing CODEOWNERS semantics to that resolved path.
Support monorepos, including duplicate or ambiguous package paths.
Keep ownership current when CODEOWNERS, modules, or mappings change, without manual regeneration.
Surface unmatched and ambiguous in-app frames with an actionable reason.
Do not require customer-maintained translation scripts.
Solution Brainstorm
No response
Product Area
Issues