-
Notifications
You must be signed in to change notification settings - Fork 256
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
🌱 Add Slack notification for image build workflow failure #1687
🌱 Add Slack notification for image build workflow failure #1687
Conversation
6973db3
to
c8c1718
Compare
c8c1718
to
1aeac8f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just a nit/sugggestion
Edit: The suggestion is not needed, the action in use already handled
Adds Slack notification for EST internal teams slack channel for jobs that run on push. So a wider audience can more quickly detect failures. Signed-off-by: NymanRobin <[email protected]>
1aeac8f
to
c3645a3
Compare
/retitle 🌱 Add Slack notification for build images workflow failure |
Is there any way to test it before merging? |
Testing it is quite hard @tuminoid What I have done is that I have ran it locally with https://github.com/nektos/act the result of these runs can be seen in the channel. To run test we would have to force failure in the pipeline and since this is push trigger we it would be on a merged change which is not ideal. We could of course change trigger to run pull-request but then again github won't allow usage of secrets in github action workflows triggered from forks. So maybe forcing a failure, in the pipeline with changed trigger in a branch created by an admin would be the test that I can think of. But honestly I do not see how that is so much different to running it locally |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/override metal3-bmo-e2e-test-pull metal3-centos-e2e-integration-test-main |
@tuminoid: Overrode contexts on behalf of tuminoid: metal3-bmo-e2e-test-pull, metal3-centos-e2e-integration-test-main In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @kashifest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
/retitle 🌱 Add Slack notification for image build workflow failure |
/cherry-pick release-0.6 |
/cherry-pick release-0.5 |
@NymanRobin: new pull request created: #1741 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@NymanRobin: new pull request created: #1742 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Adds Slack notification for EST internal teams slack channel for jobs that run on merge.
This is so a wider audience can more quickly detect failures.
Sadly, this is currently only EST internal hopefully if this works out well we can find a solution were all interested can partake