Add sentry release for connectors

[tuliren]

Summary

• Create a Sentry release whenever a new connector version is published.
• In this way, we can track an exception back to the version and suspicious commit.
• Sentry doc
  • https://docs.sentry.io/product/releases/suspect-commits/
  • https://docs.sentry.io/product/cli/releases/
• Relate to [EPIC] Report failure stack traces via sentry #9104.

[tuliren]

/publish connector=connectors/source-e2e-test

🕑 connectors/source-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775135842

[tuliren]

/publish connector=connectors/source-e2e-test

🕑 connectors/source-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775172948

[tuliren]

/publish connector=connectors/source-e2e-test

🕑 connectors/source-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775261117

[tuliren]

/publish connector=connectors/source-e2e-test

🕑 connectors/source-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775294220

[tuliren]

/publish connector=connectors/source-e2e-test

🕑 connectors/source-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775325674

[tuliren]

/publish connector=connectors/destination-e2e-test

Error: Workflow does not have 'workflow_dispatch' trigger

[tuliren]

/publish connector=connectors/destination-e2e-test

🕑 connectors/destination-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775386448
✅ connectors/destination-e2e-test https://github.com/airbytehq/airbyte/actions/runs/1775386448

[tuliren]

/publish connector=connectors/destination-dev-null

🕑 connectors/destination-dev-null https://github.com/airbytehq/airbyte/actions/runs/1775421535
✅ connectors/destination-dev-null https://github.com/airbytehq/airbyte/actions/runs/1775421535

[edgao]

I'm not familiar with how sentry works, is this basically doing:

1. install/setup sentry tooling
2. create a release with name like source-whatever@1.2.3 and associate it with a range of git commits (?)
3. do the normal connector publish stuff
4. finish the sentry release

and (presumably) if any of the sentry steps fail, then the entire release fails? (which seems like a good thing, just want to confirm)

[tuliren]

create a release with name like source-whatever@1.2.3 and associate it with a range of git commits (?)

Yes. I have installed the Sentry integration for Github. So Sentry can automatically associate the new commits for a new release. One flaw in the current process is that we typically publish a connector in a PR, and do a squash merge. So some of the PR commits will be included in the release, which won't exist in the master branch after the PR is merged. However, I cannot think of a quick way to solve this problem.

if any of the sentry steps fail, then the entire release fails?

I think Sentry is flexible most of the time. As long as it is installed correctly, it won't fail if there is an issue.

does it make sense to commit this file to git? Then if e.g. sentry.io goes down, our ability to release isn't impacted

I'd prefer not to. If we commit it, it becomes an implicit dependency we need to maintain. Sentry is usually pretty robust. We will re-evaluate if there are frequent failures.