Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Sentry release tracking for production (git sha + deploy markers)

Offen
  • Stimmt etwas nicht?
#1,240 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@vprashrex arbeitet bereits daran.

Seit 10.10.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

enhancement

Describe the current behavior
Every event in the kaapi-production Sentry project reports release 0.5.0. The release id comes from the hand-maintained API_VERSION setting, so it has not changed since April 2026. The release has no commits and no deploys attached, which means:

  • "Regressed in release" and "Resolved in next release" do not work.
  • Suspect commits are never shown on an issue.
  • There is no way to tell from Sentry which production deploy introduced a problem.

Describe the enhancement you'd like

  • Code (shared with staging): build the release id from Docker build args as kaapi-backend@<RELEASE_TAG or API_VERSION>+<git sha 12>. SENTRY_RELEASE stays as an override. GIT_SHA already exists in settings; add RELEASE_TAG.
  • backend/Dockerfile: accept a RELEASE_TAG build arg.
  • .github/workflows/create-release.yml (tag push → ECS production):
    • checkout with fetch-depth: 0
    • resolve the same release id (kaapi-backend@${GITHUB_REF_NAME}+${GITHUB_SHA::12})
    • pass --build-arg RELEASE_TAG=${{ github.ref_name }}
    • after both ECS rollouts succeed, register the release and deploy with getsentry/action-release (environment: production, set_commits: auto)
  • GitHub setup: Sentry organization token (project:releases, org:read) as the SENTRY_AUTH_TOKEN secret, plus SENTRY_ORG and SENTRY_PROJECT (kaapi-production) variables. Without them the new step fails the deploy job.

Draft implementation and runbook: #1234 (docs/runbooks/sentry-release-tracking.md).

Why is this enhancement needed?
Faster triage after a production deploy: issues link to the commit and deploy that introduced them, and regressions are flagged automatically.

Additional context

  • Staging is tracked separately; it deploys through a different workflow.
  • Verify after the first tag deploy: Sentry → Releases shows the new id under production with a non-zero commit count, and API and Celery report the same release.
Vorherrschende Sprache
Python
Sterne
18
Forks
11
Ø Merge
4 T. 16 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ProjectTech4DevAI/kaapi-backend

Alle Issues in ProjectTech4DevAI/kaapi-backend

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.