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

Email recipients should support use of build parameters

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None

    Description

      The recipients list for email notification should support parameter expansion.

      Attachments

        Issue Links

          is blocking

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-6503 Hudson email Notification takes a build parameter for recipients but replaces the parameter name with parameter value

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            mwebber Matthew Webber added a comment -

            This still fails for me, exactly as per my comment of 7/Jun/2010 - The failure is with Hudson 1.368 and email-ext 2.6.
            For a recipient list that contains a $ENVVAR, the substitution is not performed - I tried with both core email, and extended email plugin.

            mwebber Matthew Webber added a comment - This still fails for me, exactly as per my comment of 7/Jun/2010 - The failure is with Hudson 1.368 and email-ext 2.6. For a recipient list that contains a $ENVVAR, the substitution is not performed - I tried with both core email, and extended email plugin.
            mwebber Matthew Webber added a comment -

            I'm bumping the priority simply because of the various unsuccessful attempts to fix this. If someone has time to take a look at it, and test any fix, that would be great.

            mwebber Matthew Webber added a comment - I'm bumping the priority simply because of the various unsuccessful attempts to fix this. If someone has time to take a look at it, and test any fix, that would be great.
            mindless Alan Harder added a comment -

            Hm, looks like global env vars are part of build.getEnvironment() during the build steps but not there in the post-build steps. Digging further..

            mindless Alan Harder added a comment - Hm, looks like global env vars are part of build.getEnvironment() during the build steps but not there in the post-build steps. Digging further..
            mindless Alan Harder added a comment -

            yes, this is the way buildEnvironments is written.

            I'm reclosing this issue. Can you open a new improvement request asking for global environment variables to be made available to post-build actions? Thanks.

            mindless Alan Harder added a comment - yes, this is the way buildEnvironments is written. I'm reclosing this issue. Can you open a new improvement request asking for global environment variables to be made available to post-build actions? Thanks.
            mwebber Matthew Webber added a comment -

            A new improvement request has been opened (JENKINS-7075), as requested.

            mwebber Matthew Webber added a comment - A new improvement request has been opened ( JENKINS-7075 ), as requested.

            People

              mindless Alan Harder
              abayer Andrew Bayer
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: