-
Notifications
You must be signed in to change notification settings - Fork 22
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
Failure Notification Example Via Slack #435
Conversation
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.
I think the process is broken (at least was, @eti-codefresh ?), the build won't run after a merge from a fork. Only from a branch.
So You may have to merge first from your fork to a branch on codefresh-io, then from that branch to main.
for the workflow picture, use a Codefresh screenshot instead of the ArgoWorkflow one
examples/failure-notification/versions/0.0.1/docs/failure-notification.md
Outdated
Show resolved
Hide resolved
examples/failure-notification/versions/0.0.1/docs/failure-notification.md
Outdated
Show resolved
Hide resolved
examples/failure-notification/versions/0.0.1/docs/failure-notification.md
Outdated
Show resolved
Hide resolved
examples/failure-notification/versions/0.0.1/docs/failure-notification.md
Outdated
Show resolved
Hide resolved
examples/failure-notification/versions/0.0.1/workflowTemplate.yaml
Outdated
Show resolved
Hide resolved
Maybe add at least 1 parameter for SLACK_HOOK_URL so it can be run as an example. |
@lrochette I have added the annotations, renamed the template, fixed the misspellings, added parameter, and retook a new screenshot. |
Closing PR as this is from fork. Reopening new PR from branch. |
This example is to show how to set up a failure notification for a workflow. This example sends a slack notification upon when the workflow exits with a failure.
@lrochette this is for Example: Notifications on Step/Pipeline Failure