• Type: New Feature
• Resolution: Duplicate
• Priority: Major
• Component/s: email-ext-plugin
• Labels:

  None
• Environment:

  Linux

1. 

   email-ext-tokens.png

   35 kB

   2010-01-19 06:41

[JENKINS-5311] email-ext token listing all triggers of a build

asalicetti created issue - 2010-01-19 04:31

asalicetti made changes - 2010-01-19 04:31

Description

Original: It would be very useful to include the user who triggered the build into the subject or body of the email sent by email-ext. Unfortunately, such variable is not available. For the job who has not an upstream job and can only be started manually (by logged users) cuold be very useful. See also [Issue 4463|http://issues.jenkins-ci.org/browse/JENKINS-4463] (refused).

New: It would be very useful to include the user who triggered the build into the subject or body of the email sent by email-ext. Unfortunately, such variable is not available. For the job who has not an upstream job and can only be started manually (by logged users) could be very useful. See also [Issue 4463|http://issues.jenkins-ci.org/browse/JENKINS-4463] (refused).

mdonohue made changes - 2010-01-19 06:13

Description	Original: It would be very useful to include the user who triggered the build into the subject or body of the email sent by email-ext. Unfortunately, such variable is not available. For the job who has not an upstream job and can only be started manually (by logged users) could be very useful. See also [Issue 4463|http://issues.jenkins-ci.org/browse/JENKINS-4463] (refused).	New: It would be very useful to include what triggered the build into the subject or body of the email sent by email-ext. Unfortunately, such variable is not available. See also [Issue 4463|http://issues.jenkins-ci.org/browse/JENKINS-4463] (refused).
Summary	Original: Logged in user available as env variable	New: email-ext token listing all triggers of a build

Collapse comment: asalicetti added a comment - 2010-01-19 06:41

asalicetti added a comment - 2010-01-19 06:41

Available tokens

Expand comment: asalicetti added a comment - 2010-01-19 06:41

asalicetti added a comment - 2010-01-19 06:41 Available tokens

asalicetti made changes - 2010-01-19 06:41

Attachment

New: email-ext-tokens.png [ 19037 ]

Collapse comment: asalicetti added a comment - 2010-01-19 06:42

asalicetti added a comment - 2010-01-19 06:42

What do you mean with "email-ext token listing all triggers of a build"?
Which is the env variable that holds the logged in user?
I haven't found it...

However, here there are all the available tokens as declared by email-ext plugin:

Expand comment: asalicetti added a comment - 2010-01-19 06:42

asalicetti added a comment - 2010-01-19 06:42 What do you mean with "email-ext token listing all triggers of a build"? Which is the env variable that holds the logged in user? I haven't found it... However, here there are all the available tokens as declared by email-ext plugin:

Collapse comment: mdonohue added a comment - 2010-01-19 07:05

mdonohue added a comment - 2010-01-19 07:05

That's a summary of the issue which is still open - I generalized it to include all causes of a build, as that would provide a more uniform presentation of the data.

Expand comment: mdonohue added a comment - 2010-01-19 07:05

mdonohue added a comment - 2010-01-19 07:05 That's a summary of the issue which is still open - I generalized it to include all causes of a build, as that would provide a more uniform presentation of the data.

mdonohue made changes - 2010-01-20 05:19

Link

New: This issue duplicates JENKINS-3166 [ JENKINS-3166 ]

mdonohue made changes - 2010-01-20 05:19

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-25 23:59

Workflow

Original: JNJira [ 135400 ]

New: JNJira + In-Review [ 203460 ]