mirror of https://github.com/zulip/zulip.git
hooks: Tell Sentry the explicit commit range.
This is necessary if one has different deployments (with different commit ranges) using the same projects. See https://docs.sentry.io/product/releases/associate-commits/#using-the-cli for the API of the `sentry-cli` tool.
This commit is contained in:
parent
7657cb4a0f
commit
edfc911649
|
@ -24,8 +24,9 @@ curl "https://sentry.io/api/0/organizations/$sentry_org/releases/" \
|
||||||
|
|
||||||
merge_base="${ZULIP_NEW_MERGE_BASE_COMMIT:-}"
|
merge_base="${ZULIP_NEW_MERGE_BASE_COMMIT:-}"
|
||||||
if [ -n "$merge_base" ]; then
|
if [ -n "$merge_base" ]; then
|
||||||
|
old_merge_base="$ZULIP_OLD_MERGE_BASE_COMMIT"
|
||||||
echo "sentry: Setting commit range based on merge-base to upstream of $merge_base"
|
echo "sentry: Setting commit range based on merge-base to upstream of $merge_base"
|
||||||
sentry-cli releases --org="$sentry_org" set-commits "$sentry_release" --commit="zulip/zulip@$merge_base"
|
sentry-cli releases --org="$sentry_org" set-commits "$sentry_release" --commit="zulip/zulip@$old_merge_base..$merge_base"
|
||||||
fi
|
fi
|
||||||
|
|
||||||
if [ -n "$sentry_frontend_project" ]; then
|
if [ -n "$sentry_frontend_project" ]; then
|
||||||
|
|
Loading…
Reference in New Issue