sentry-ci-integration

Integrate Sentry with CI/CD pipelines.Use when setting up GitHub Actions, GitLab CI, or other CI systemswith Sentry releases and source maps.Trigger with phrases like "sentry github actions", "sentry CI","sentry pipeline", "automate sentry releases".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill automates the integration of Sentry with CI/CD pipelines such as GitHub Actions, GitLab CI, and CircleCI. It streamlines the error tracking workflow by managing release creation, uploading source maps for precise stack trace mapping, and associating commits with releases. By automating these DevOps tasks, it ensures that production errors are immediately actionable and linked to specific code changes, significantly reducing the Mean Time to Resolution (MTTR).

Use Cases

  • Automated Release Management: Automatically create, finalize, and track Sentry releases as part of your deployment pipeline to monitor version-specific stability.
  • Source Map Orchestration: Simplify the complex process of generating and uploading source maps to Sentry during the build phase to ensure readable stack traces in production.
  • Commit and Metadata Association: Link git history and commits to Sentry releases automatically, allowing teams to identify exactly which developer and code change introduced a regression.
  • Environment Deployment Tracking: Configure automated deployment notifications to Sentry to correlate performance changes and errors with specific environment deployments.
namesentry-ci-integration
description|
allowed-toolsRead, Write, Edit, Bash(gh:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Ci Integration

Prerequisites

  • Sentry CLI installed or available in CI
  • SENTRY_AUTH_TOKEN secret configured
  • SENTRY_ORG and SENTRY_PROJECT environment variables set
  • Source maps generated during build

Instructions

  1. Add SENTRY_AUTH_TOKEN secret to CI platform (GitHub, GitLab, CircleCI)
  2. Configure SENTRY_ORG and SENTRY_PROJECT environment variables
  3. Create workflow step to build application with SENTRY_RELEASE env
  4. Add step to create Sentry release using sentry-cli or action
  5. Upload source maps from build output directory
  6. Associate commits with release using set-commits --auto
  7. Finalize the release to mark it complete
  8. Add deploy notification step for environment tracking
  9. Configure checkout with fetch-depth: 0 for full git history
  10. Test workflow by pushing to trigger release creation

Output

  • Release created and finalized in Sentry
  • Source maps uploaded for stack trace mapping
  • Commits associated with release
  • Deploy notification sent to Sentry

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources