[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too. Something like this $VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too.
Something like this \$VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
${VARNAME}, $VARNAME and ${ENV, var="VARNAME"} works for me, too.
Something like this $VARNAME doesn´t work. It is the backslash(es) in front of the $. See comment by Alex Earl on 20/May/13 10:42 PM
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
When does the fix be available? I updated the token macro plugin to 1.7 and the email-ext-plugin to 2.30.2 but it still fails.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Ralf Rausch
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I think it is the same issue.
In the default content section of the editable email notification we defined this value: Server-Log-Files: \\${ENV, var="COMPUTERNAME"}\logs\${PROJECT_NAME}.
In the e-mail we get: Server-Log-Files: ${ENV, var="COMPUTERNAME"}\logs\${PROJECT_NAME} The ${ENV} and ${PROJECT_NAME} are not converted.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14482) com.cloudbees.plugins.flow.JobExecutionFailureException
Ralf Rausch created JENKINS-14482 com.cloudbees.plugins.flow.JobExecutionFailureException Issue Type: Bug Assignee: Nicolas De Loof Attachments: console-output.txt Components: build-flow Created: 18/Jul/12 12:15 PM Description: My Build-Flow "Test-Flow" looks like the following: build( "Test1" ) build( "Test2" ) If Job "Test1" ends with "Finished: UNSTABLE" the "Test-Flow" will break with the following error (see attachment) Environment: Jenkins ver. 1.474 Build Flow Plugin 0.4 Project: Jenkins Priority: Major Reporter: Ralf Rausch 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
