Skip to content

Fix macOS home-brew PR slack notifications for new release #7102

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

Conversation

NlightNFotis
Copy link
Contributor

Currently, the slack notification action we use to notify
us in case jobs fail doesn't work on macOS and Windows (because
of a docker issue bootstrapping an Alpine linux environment on
top of those, see rtCamp/action-slack-notify#22).

This is allowing us to do that, by cloning the action source code
into our scripts/ folder, and then running it using a downloaded
golang toolchain - instead of needing to run the whole action on
top of docker.

  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@NlightNFotis NlightNFotis requested a review from a team as a code owner September 5, 2022 16:05
@NlightNFotis NlightNFotis self-assigned this Sep 5, 2022
@NlightNFotis NlightNFotis added the CI label Sep 5, 2022
@codecov
Copy link

codecov bot commented Sep 5, 2022

Codecov Report

Merging #7102 (c2f99d4) into develop (4067de6) will increase coverage by 0.00%.
The diff coverage is 95.12%.

@@           Coverage Diff            @@
##           develop    #7102   +/-   ##
========================================
  Coverage    77.87%   77.87%           
========================================
  Files         1576     1576           
  Lines       181568   181588   +20     
========================================
+ Hits        141394   141413   +19     
- Misses       40174    40175    +1     
Impacted Files Coverage Δ
...lvers/smt2_incremental/smt_response_validation.cpp 95.36% <94.11%> (-0.22%) ⬇️
...lvers/smt2_incremental/smt_response_validation.cpp 98.48% <100.00%> (+0.05%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

case "failure":
color = "danger"
default:
color = envOr(EnvSlackColor, "good")
Copy link
Contributor

Choose a reason for hiding this comment

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

Should the default really be "good"? Isn't this what we would see if we have some unexpected outcome (infrastructure unavailable?)... I would assume we'd like to see some warning or error, not that it worked.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll see if I can find one that's a neutral colour (say, yellow or grey)

Copy link
Contributor

Choose a reason for hiding this comment

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

Or failure. We should assume the "bad" path here, not the "good" path.

AuthorName: envOr(EnvGithubActor, ""),
AuthorLink: os.Getenv("GITHUB_SERVER_URL") + "/" + os.Getenv(EnvGithubActor),
AuthorIcon: os.Getenv("GITHUB_SERVER_URL") + "/" + os.Getenv(EnvGithubActor) + ".png?size=32",
Footer: envOr(EnvSlackFooter, "<https://github.com/rtCamp/github-actions-library|Powered By rtCamp's GitHub Actions Library>"),
Copy link
Contributor

@TGWDB TGWDB Sep 6, 2022

Choose a reason for hiding this comment

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

Can we do this without a footer? If not, can we make the footer empty? I don't see a benefit in advertising/adding footers here. (The messages are already quite spammy...)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, happy to leave this empty.

@NlightNFotis NlightNFotis merged commit b69a945 into diffblue:develop Sep 6, 2022
@NlightNFotis NlightNFotis deleted the fix_macos_slack_notifications branch September 6, 2022 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants