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

ci: deadmansnitch for code-cover-publish Github Action #137412

Merged

Conversation

golgeek
Copy link
Contributor

@golgeek golgeek commented Dec 13, 2024

Before the fix provided by #137298, this Github Action was silently failing.

This PR configures a call to DeadManSnitch service to report when the Github Action was last successful. The service is configured to alert CRL internal team when no ping was seen in the last 24h.

Epic: none
Release note: None

Before the fix provided by cockroachdb#137298, this Github Action was silently
failing.

This PR configures a call to DeadManSnitch service to report when the
Github Action was last successful. The service is configured to alert
CRL internal team when no ping was seen in the last 24h.

Epic: none
Release note: None

Signed-off-by: Ludovic Leroux <[email protected]>
@golgeek golgeek requested a review from a team as a code owner December 13, 2024 16:46
@cockroach-teamcity
Copy link
Member

This change is Reviewable


- name: 'Call DeadManSnitch'
run: |
curl -X GET 'https://nosnch.in/c2d75963ee' -d 'message=Code coverage uploaded to GCS'
Copy link
Contributor

Choose a reason for hiding this comment

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

No auth/API key is needed for this? Wondering if the url should be a secret in that case - although admittedly I haven't looked into how DeadManSnitch works.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No auth/API key needed.

About it being a secret, I kinda wondered the same thing, but we already have one publicly available in the repo, and the worst thing that can happen is that something reports the status in lieu of the action (granted that it defeats the purpose...).

Maybe @cockroach-dev-inf has an opinion?

Copy link
Collaborator

Choose a reason for hiding this comment

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

We don't typically have to keep these URL's secret -- the risk isn't huge.

If you want to make this one a secret, be my guest (although you've technically already "leaked" this one, so you should "rotate" it :) )

I'm not aware of any broad issue with third parties hitting these URL's and as mentioned the worst thing that can happen is we think the thing has reported a success when it hasn't.

@srosenberg srosenberg closed this Dec 13, 2024
@srosenberg srosenberg reopened this Dec 13, 2024
@golgeek
Copy link
Contributor Author

golgeek commented Dec 13, 2024

TFTR!

bors r=srosenberg,rickystewart,DarrylWong

@craig craig bot merged commit 8919614 into cockroachdb:master Dec 13, 2024
37 checks passed
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.

5 participants