Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Send connector specific publish failures to a dedicated channel #42522

Closed
alafanechere opened this issue Jul 25, 2024 · 0 comments · Fixed by #42849
Closed

Send connector specific publish failures to a dedicated channel #42522

alafanechere opened this issue Jul 25, 2024 · 0 comments · Fixed by #42849
Assignees
@alafanechere
Labels
team/tooling team/triage

Comments

@alafanechere
Copy link
Contributor

Connector specific publish failure are sent in the same channel as the successful one.
It makes it hard to spot which connector has to be re-published as we have a lot of successful runs.

Let's change airbyte-ci logic where it sends slack messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alafanechere alafanechere

Labels
team/tooling team/triage
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

airbyte-ci: send publish failures to a dedicated slack channel airbytehq/airbyte
2 participants
@alafanechere @octavia-squidington-iii