Automates artifact validation and commit-status gating to enforce crash-symbolication completeness.
The AI agent listens for GitHub push events, reads commit and repo details, and identifies the target Sentry release. It fetches the release’s uploaded artifacts and runs concrete validation: a .dSYM file for iOS or both proguard.txt and mapping.txt for Android. If artifacts are complete, the agent updates the GitHub commit status to success, allowing merges; if artifacts are missing, it does not update the status, effectively blocking merges.
Performs end-to-end artifact checks and updates PR status.
Listen for GitHub push events and extract commit SHA, repository, and branch.
Fetch the target Sentry release and its uploaded artifact files.
Validate that a .dSYM exists or that both proguard.txt and mapping.txt exist.
Determine success when artifacts are present and update status accordingly.
Skip updating status when artifacts are incomplete, blocking merges.
Maintain a traceable log of validation results and platform-specific rules.
Before: teams face manual artifact checks, flaky PR gates, and symbolication gaps. After: artifacts are automatically validated on every push, statuses reflect reality, and merges only proceed when symbolication is complete.
A simple 3-step flow that non-technical users can follow.
Listens for push events and extracts commit SHA, repository name, and branch metadata.
Retrieves the release for the given version and gathers uploaded artifact files.
Runs the artifact rules (dSYM or ProGuard+mapping) and updates GitHub status to success when valid; otherwise no status update.
A realistic scenario showing task, time, and outcome.
Scenario: A new GitHub push triggers the AI Agent, which fetches the Sentry release’s files. The Android release includes both proguard.txt and mapping.txt, so the agent marks the commit as success. The PR can be merged within minutes with a verified symbolication path.
Role-based reasons for using this AI agent.
Ensure crash symbolication artifacts exist before releasing.
Enforce gate at PR level with reliable artifact checks.
Automate artifact validation within CI/CD pipelines.
Integrate Sentry symbolication checks into workflow
Verify symbolication readiness across platforms.
Guarantee crash symbolication for iOS and Android releases.
Core tools the AI agent uses to run checks.
Reads push events and updates commit statuses to reflect artifact completeness.
Fetches releases and files and applies artifact validation rules.
Uploads artifacts to Sentry and provides version alignment for checks.
Stores validation results for audit and traceability.
Concrete scenarios where the AI agent adds value.
Common questions about the AI agent and how it works.
It automates the end-to-end validation of crash-symbolication artifacts and gates PRs based on artifact completeness. It listens to GitHub pushes, queries Sentry for releases, and decides whether to update the commit status. The goal is to ensure every release has the necessary artifacts before it can be merged.
The gate checks for a valid iOS dSYM file or, for Android, the presence of both proguard.txt and mapping.txt in the Sentry release. You can customize what qualifies as complete by editing the validation logic.
When artifacts are valid, the agent issues a commit-status update to GitHub with a success state and description. If artifacts are missing, no status update is sent, effectively blocking PR merges until assets arrive.
The workflow does not update the commit status, so the PR remains open and the merge gate remains in place. You get clear logs showing which artifacts are missing and why validation failed, enabling faster remediation.
Yes. The gate supports iOS and Android symbolication rules and can be extended to additional platforms by adding artifact checks. You can customize per-platform criteria to match project requirements.
You’ll need GitHub API access, a Sentry auth token with release access, and a build pipeline that uploads artifacts to Sentry. The agent uses these credentials to read push events, fetch releases, and update commit statuses.
Yes. You can modify the JS logic in the validation step to require extra artifacts or different naming conventions. This makes the gate adaptable to evolving symbolication pipelines.
Automates artifact validation and commit-status gating to enforce crash-symbolication completeness.
