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

Use build parameter/variable for IM notification recipient

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We can not use build parameter or variable(example in a maven2 job) in the
      recipient list of hudson jabber plugin.
      I would like to use parameter that specify the notifiedd user.
      I would even prefer to notify connected user (the user who starts the build).

        Attachments

          Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-18947 Unable to use environment variables within the list of notification targets in the jabber plugin

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-34903 IRC plugin: custom post-build message

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            kutzi kutzi added a comment -

            changed issue type and summary

            Show
            kutzi kutzi added a comment - changed issue type and summary
            Hide
            Permalink
            kutzi kutzi added a comment -

            Feel free to submit a patch for this. Otherwise this won't be implemented any time soon.

            Show
            kutzi kutzi added a comment - Feel free to submit a patch for this. Otherwise this won't be implemented any time soon.
            Hide
            Permalink
            jimklimov Jim Klimov added a comment - - edited

            Partially duplicated by JENKINS-18947 (in the part that both issues ask to notify the user who started a build).

            With a look at this from 2019, note also that recently there were Jenkins core changes to promote running jobs as different Jenkins accounts, not just as "System". In relation to this story, make sure to NOT notify jobs started automatically, perhaps whether as System or not (the BuildCause's should probably allow to differentiate that), probably including non-human re-runs of such, although should probably it should notify a person who started a parent job that triggered this one with IM notifications enabled.

            Show
            jimklimov Jim Klimov added a comment - - edited Partially duplicated by JENKINS-18947 (in the part that both issues ask to notify the user who started a build). With a look at this from 2019, note also that recently there were Jenkins core changes to promote running jobs as different Jenkins accounts, not just as "System". In relation to this story, make sure to NOT notify jobs started automatically, perhaps whether as System or not (the BuildCause's should probably allow to differentiate that), probably including non-human re-runs of such, although should probably it should notify a person who started a parent job that triggered this one with IM notifications enabled.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              fhugot fhugot
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated: