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

Allow use of environment variable for e-mail address

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • mail-watcher-plugin
    • None

      Instead of setting the same e-mail address for each node, it would be ideal to allow expansion of a environment variable defined in the global properties.

      Currently, if I use a variable such as $NOTIFICATION_ADDRESS an e-mail is sent literally to '$NOTIFICATION_ADDRESS' instead of expanding it to the expected value.

          [JENKINS-20536] Allow use of environment variable for e-mail address

          Henrik Skupin added a comment -

          Is there any chance this can be implemented? It's a hassle to have to change so many configuration files if the email changes. Thanks.

          Henrik Skupin added a comment - Is there any chance this can be implemented? It's a hassle to have to change so many configuration files if the email changes. Thanks.

          Oliver Gondža added a comment -

          Token macro expansion would definitely be valuable addition. Also, I can not think of possible problems for implementing it, though I did not have enough time for now. Pull request welcomed.

          Oliver Gondža added a comment - Token macro expansion would definitely be valuable addition. Also, I can not think of possible problems for implementing it, though I did not have enough time for now. Pull request welcomed.

          Geoffroy Jabouley added a comment -

          Hi
          seeing recent updates on this plugin, could this ticket get some attention and possible implementation discussed?
          Token macro expansion is probably the best solution.
          I'm not really fluent with Java, i added such support in the past for other plugins but it was for much simpler use cases.
          Tried on this one few years ago, but was not able to understand how to do that...

          Geoffroy Jabouley added a comment - Hi seeing recent updates on this plugin, could this ticket get some attention and possible implementation discussed? Token macro expansion is probably the best solution. I'm not really fluent with Java, i added such support in the past for other plugins but it was for much simpler use cases. Tried on this one few years ago, but was not able to understand how to do that...

            Unassigned Unassigned
            davehunt Dave Hunt
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: