Skip to content

Conversation

@mujacica
Copy link
Contributor

This commit adds backend support for Perforce version control integration:

  • New Perforce integration with P4 client support
  • Repository and code mapping functionality
  • Stacktrace linking for Perforce depot paths
  • Tests for integration, code mapping, and stacktrace linking
  • Updated dependencies in pyproject.toml

The integration supports:

  • Authentication via P4PORT, P4USER, P4PASSWD, P4TICKET
  • Code mapping between depot paths and project structure
  • Source URL generation for stacktrace frames
  • Integration with Sentry's repository and code mapping systems

This commit adds backend support for Perforce version control integration:

- New Perforce integration with P4 client support
- Repository and code mapping functionality
- Stacktrace linking for Perforce depot paths
- Tests for integration, code mapping, and stacktrace linking
- Updated dependencies in pyproject.toml

The integration supports:
- Authentication via P4PORT, P4USER, P4PASSWD
- Code mapping between depot paths and project structure
- Source URL generation for stacktrace frames
- Integration with Sentry's repository and code mapping systems
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 11, 2025
@cathteng
Copy link
Member

This PR is 2500 lines -- would it possible to split it up for review? There are aspects that should be reviewed by different teams like dependencies, specific features, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants