[JIRA] (JENKINS-16169) PROMOTED_* variables are not available when sending mail on a Promotion event
Slide-O-Mix resolved JENKINS-16169 as Incomplete PROMOTED_* variables are not available when sending mail on a Promotion event Change By: Slide-O-Mix (02/Jan/13 4:12 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16169) PROMOTED_* variables are not available when sending mail on a Promotion event
Slide-O-Mix commented on JENKINS-16169 PROMOTED_* variables are not available when sending mail on a Promotion event Did you try the ENV token? See the content token help when configuring the email-ext plugin for how to use it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16169) PROMOTED_* variables are not available when sending mail on a Promotion event
uri milman
created JENKINS-16169
PROMOTED_* variables are not available when sending mail on a Promotion event
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
19/Dec/12 1:35 PM
Description:
When using the Promoted Build plugin, some variables are exposed:
PROMOTED_NUMBER
PROMOTED_URL
PROMOTED_JOB_NAME
PROMOTED_ID
When sending mail while promoting, those vars do not exist, so one cannot refer to the original build which was promoted. Also, the ${Changes} token takes changes of the promoted build, which is empty, since the changes list itself is not copied to the promoted one.
use case: send an email of the build being promoted to QA, with its number, and a link to the changes-list, so it's possible to see the changes between 2 promoted builds.
Project:
Jenkins
Priority:
Major
Reporter:
uri milman
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
