-
Notifications
You must be signed in to change notification settings - Fork 79
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
Enable email notification to external address #310
Comments
Could you use a notify script to do this?
… On Sep 6, 2020, at 11:52 AM, Christian Kotte ***@***.***> wrote:
Could you implement email notification to external addresses?
Probably a copy of system-email plus at least one parameters like recipient.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Is there a message passed to the program as a parameter? |
Wouldn't is be possible to just duplicate |
Yeah. When I get around to it ;)
In the meantime, would this work: https://dshearer.github.io/jobber/doc/v1.4/#notifications
… On Sep 7, 2020, at 3:46 AM, Christian Kotte ***@***.***> wrote:
Wouldn't is be possible to just duplicate result_sink_system_email.go and change execResult, err := common.ExecAndWait([]string{"sendmail", rec.Job.User}, msgBytes) and replace rec.Job.User with the recipient parameter?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#310 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRCWRGCK2LZJ3YSI43NMETSES2WZANCNFSM4Q4YQRHQ>.
|
I created a job where the command errors every time. However, the job doesn't never fails. It should eventually fail if I configured it to run every minute, but the schedule changes after two failures:
When will it fail and will the JSON be different? I can differentiate between success and error via "succeeded", but how can I get the failure state?
Edit: Ok. I got it. I should use
|
Could you implement email notification to external addresses?
Probably a copy of system-email plus at least one parameters like recipient.
The text was updated successfully, but these errors were encountered: