Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

Sentry Integration: Track staging commits

Đang mở
  • Có gì không ổn?
#1,241 0 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@vprashrex đang làm issue này rồi.

Từ ngày 10/10/2026.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

enhancement

Is your feature request related to a problem?
Staging deploys for every green main CI run do not correctly capture commit shas in Sentry releases. With multiple changes landing on staging, it is difficult to identify which merge introduced a staging issue.

Describe the solution you'd like
Implement the shared release-id code from the production issue:

  • Update docker-compose.staging.yml to pass RELEASE_TAG alongside GIT_SHA for backend services.
  • In deploy-staging.yml, set RELEASE_TAG=main and GIT_SHA=$DEPLOY_SHA in the docker compose build command.
  • Checkout the repo with fetch-depth: 0 after the SSM command succeeds.
  • Register the release and deploy using getsentry/action-release only if the SSM deploy is successful.
  • Reuse the SENTRY_AUTH_TOKEN secret and SENTRY_ORG variable; add SENTRY_STAGING_PROJECT as kaapi-staging.

Why is this enhancement needed?
This enhancement will ensure each staging deploy is associated with its specific commits, allowing quick identification of the source of staging issues before changes reach production.

Original issue

Describe the current behavior
Staging deploys on every green main CI run through .github/workflows/deploy-staging.yml (SSM → EC2 → docker compose -f docker-compose.staging.yml). The commit sha is already passed as the GIT_SHA build arg, but the Sentry release id ignores it, so every staging event in the kaapi-staging project reports the same release. Many changes land on staging between production releases, and there is no way to tell which merge introduced a staging issue.

Describe the enhancement you'd like
Depends on the shared release-id code from the production issue (kaapi-backend@<RELEASE_TAG or API_VERSION>+<git sha 12>).

  • docker-compose.staging.yml: pass RELEASE_TAG as a build arg next to GIT_SHA for every service that builds the backend image.
  • deploy-staging.yml:
    • set RELEASE_TAG=main alongside GIT_SHA=$DEPLOY_SHA in the docker compose build command
    • checkout the repo with fetch-depth: 0 in a step after the SSM command succeeds
    • register the release and deploy with getsentry/action-release (release: kaapi-backend@main+<DEPLOY_SHA 12>, environment: staging, set_commits: auto) only when the SSM deploy succeeded
  • GitHub setup: reuse the SENTRY_AUTH_TOKEN secret and SENTRY_ORG variable; add SENTRY_STAGING_PROJECT = kaapi-staging.

Why is this enhancement needed?
Each staging deploy becomes a Sentry release with its commits, so a new staging issue points at the merge that caused it before the change reaches production.

Additional context

  • Use DEPLOY_SHA (workflow_run.head_sha), not github.sha: this workflow is triggered by workflow_run, where github.sha is the default-branch head, not necessarily the deployed commit.
  • deploy-staging-ecs.yml (manual workflow_dispatch) is a second staging path; decide whether it stays and, if so, apply the same steps there.
  • Verify after the next main merge: Sentry → Releases in kaapi-staging shows kaapi-backend@main+<sha> under staging with commits attached.
Ngôn ngữ chính
Python
Star
18
Fork
11
Merge trung bình
3 ngày 11 giờ
Pull request đã merge (30 ngày)
8

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của ProjectTech4DevAI/kaapi-backend

Tất cả issue của ProjectTech4DevAI/kaapi-backend

Issue tương tự

Thêm issue về Python

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.