Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58935

For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols

      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.

          [JENKINS-58935] For pipeline context, devise a way to generalize the config options and notification steps for all IM protocols

          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?

          Christopher Orr added a comment - 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?

            Unassigned Unassigned
            jimklimov Jim Klimov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: