-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
The instant-messaging-plugin since release 1.37 provides the shareable core functionality for pipeline integration, used by step implementations in ircbot-plugin (since 2.31) and jabber-plugin (merge and release pending). Hopefully over time other protocol plugins would catch up.
It sounds reasonable to implement a generic notification step (and `options{}` support eventually) that would send messages with a single command in the pipeline script without worries about which IM protocols are set up in a particular build farm, making the codebase and recipes for it more portable.
- is related to
-
JENKINS-36826 Support Jenkins Pipeline for Jabber notifications
-
- Resolved
-
-
JENKINS-58933 For pipeline context, add an "options{...}" preset for ircNotify (or generalize for imNotify?)
-
- Open
-
-
JENKINS-58934 For pipeline context, add an "options{...}" or similar clause trigger for IM notifications without an explicit step
-
- Open
-
-
JENKINS-33922 Pipeline support for IRC Notifier
-
- Resolved
-
I'm going to remove myself as assignee, as gcm-notification-plugin no longer exists.
I don't know whether you intend to work on this or not, but either way I think it would be useful to have some examples of what you think the syntax should look like.
e.g. How would it deal with custom targets or options per Pipeline, or there being multiple "IM providers" configured on a given Jenkins instance?