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.

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

chore(ci): notify via slack when a publishing workflow fails #525

Merged
merged 34 commits into from
Oct 23, 2024

Conversation

ArtieReus
Copy link
Collaborator

@ArtieReus ArtieReus commented Oct 16, 2024

Summary

To ensure we're notified of any publishing failures, integrate Slack into the workflows so that a notification is posted whenever the workflow fails. This is crucial because workflows that react to a push on the main branch run after the PR is merged. At that point, there is no active control by the developer, and if the developer isn't self-checking the action logs, any issues that arise could go unnoticed. With Slack notifications, we can proactively alert the team of any failures, ensuring that problems are addressed immediately.

Changes Made

  • create a reuse workflow for the slack notification
  • notify on failure when building supernova
  • notify on failure when building greenhouse
  • notify on success on npm release using the reuse workflow

Related Issues

Screenshots (if applicable)

Testing Instructions

  1. npm i
  2. npm run TASK

Checklist

  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have made corresponding changes to the documentation (if applicable).
  • My changes generate no new warnings or errors.

@ArtieReus ArtieReus requested a review from a team as a code owner October 16, 2024 14:23
Copy link

changeset-bot bot commented Oct 16, 2024

⚠️ No Changeset found

Latest commit: 1471e1b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ArtieReus ArtieReus self-assigned this Oct 16, 2024
@ArtieReus ArtieReus added infrastructure Infrastructure related issues, ci as well draft labels Oct 16, 2024
@ArtieReus ArtieReus marked this pull request as draft October 16, 2024 14:23
@ArtieReus
Copy link
Collaborator Author

fixes #409

@ArtieReus ArtieReus marked this pull request as ready for review October 17, 2024 08:53
@ArtieReus ArtieReus removed the draft label Oct 17, 2024
@ArtieReus
Copy link
Collaborator Author

fixes #409

hodanoori
hodanoori previously approved these changes Oct 22, 2024
Copy link
Contributor

@barsukov barsukov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets us fix errors and merge it

Copy link
Contributor

@barsukov barsukov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much better! thank you 💯

@andypf andypf merged commit 79d3c8c into main Oct 23, 2024
13 checks passed
@andypf andypf deleted the artie-shared-slack branch October 23, 2024 02:53
andypf added a commit that referenced this pull request Oct 23, 2024
* chore(ci): uses shared notification if workflow job fails

* chore(ci): adds pr for testing

* chore(ci): changes to fully qualified url

* chore(ci): makes use of the shared workflow correctly

* chore(ci): passes webhook as input

* chore(ci): reads webhook from input

* chore(ci): passes the webhook as secret

* chore(ci): adds mapping

* chore(ci): sets secrets not within with statement

* chore(ci): adds valid json

* chore(ci): formats the body

* chore(ci): formats the title

* chore(ci): removes double JUNO on title

* chore(ci): sets body rich per var

* chore(ci): sets inline envs

* chore(ci): sets playload in a new step

* chore(ci): corrects envs json syntax

* chore(ci): ensures the JSON output is compact and valid

* chore(ci): adds tests with rich body

* chore(ci): cleans up the call

* chore(ci): adds branch to the shared task

* chore(ci): removes test

* chore(ci): tests reuse action in release

* chore(ci): removes double quotes

* chore(ci): adds test

* chore(ci): adds test integration

* chore(ci): adds last test

* chore(ci): removes tests and setups release

* chore(ci): fixes copy paste errors

---------

Co-authored-by: Andreas Pfau <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Infrastructure related issues, ci as well
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants