Skip to content

Fix health check #39

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

Merged
merged 3 commits into from
Sep 1, 2021
Merged

Fix health check #39

merged 3 commits into from
Sep 1, 2021

Conversation

pcothenet
Copy link
Contributor

@pcothenet pcothenet commented Sep 1, 2021

What

  • Make health check notify of errors as well
  • Notify only of errors
  • Limit to one node version for now (less noise)

Why

  • Get notified in case of errors

SDK Release Checklist

  • Have you added an integration test for the changes?
  • Have you built the package locally and made queries against it successfully?
  • Did you update the changelog?
  • Did you bump the package version?
  • For breaking changes, did you plan for the release of the new SDK versions and deploy the API to production?

@@ -33,6 +33,7 @@ jobs:
- name: Notify slack
uses: kpritam/slack-job-status-action@v1
with:
if: ${{ failure() }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@kleinjm I'm pretty sure that this will work fine with this and notify us of failure.

I would rather we trust the system and be notified only of failures in order to diminish noise.

Copy link
Contributor

Choose a reason for hiding this comment

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

absolutely. And FWIW, that artifact upload GH action uses failure() and works as expected (doesn't try to upload on success case) so this should work

@pcothenet pcothenet requested a review from kleinjm September 1, 2021 18:53
job-status: ${{ job.status }}
slack-bot-token: ${{ secrets.SLACK_BOT_TOKEN }}
channel: github-actions
Copy link
Contributor

Choose a reason for hiding this comment

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

are you going to delete this channel? I'm in favor of that

node: ['10', '12', '14']
node: ['12']
Copy link
Contributor

Choose a reason for hiding this comment

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

not sure you want to do this if we care to support all versions. You can set max-parallel: 1 to run these in series instead of parallel and then we'll only be alerted on the first node version test suite that fails. See https://github.com/patch-technology/patch-ruby/blob/4c8f0f5fd64a46f4e4815764be3ffb677be425db/.github/workflows/test.yml#L16

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good idea. I was concerned about getting four useless success notifications, but now that I've switched to failure only, this should work.

Copy link
Contributor

@kleinjm kleinjm left a comment

Choose a reason for hiding this comment

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

not blocking but I feel we should keep all node versions

@pcothenet pcothenet merged commit 1c668ac into main Sep 1, 2021
@pcothenet pcothenet deleted the pc/health branch September 1, 2021 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants