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 result sinks for Telegram, Slack, Email #153
Comments
How do you feel about using YAML anchors/references? Like this:
I'd like to drop the ability to override notify provider params in the job def, in order to reduce complexity. |
I agree with it. It's clear. |
Actually, I'm thinking of merging #179 into this. We have a notion of "result sink", which is given the result of a run (success/failure), stdout, and stderr, and then does something with it. (At the same time, I'm thinking of just making the whole jobfile pure YAML.) See https://github.com/dshearer/jobber/wiki/1.4-Jobfile-Format |
Hi @dshearer, from this discussion, it's not really clear if this is only change of a configuration file, to allow multiple notifications providers or an actual implementation of those providers for defined types e.g. I'm thinking about replacing cron with jobber, but I'm not sure if I should spend time now on writing own notification program if it will be provided soon. Thanks! |
Yes, this ticket is for providing these implementations. I do plan to do this, but I don't know by when. |
I will write simple notifier, for now then. Thanks for the update. |
Plugins could be nice. Maybe reuse plugins from drone.io http://readme.drone.io/plugins/plugin-overview/ |
I feel bad about them. Unless you know what are YAML anchors, the format looks too cryptic. |
Make notification sender (jobbern) with some default providers (email, telegram, slack, webhook etc).
Configuration example:
The text was updated successfully, but these errors were encountered: