[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
resolved JENKINS-18014 as Fixed
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
This will be fixed in the token macro plugin in 1.8
Change By:
Alex Earl
(30/Jun/13 1:57 AM)
Status:
Reopened
Resolved
Resolution:
Fixed
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.
Alex Earl
updated JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Change By:
Alex Earl
(30/Jun/13 1:57 AM)
Component/s:
token-macro
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.
SCM/JIRA link daemon
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Code changed in jenkins
User: Alex Earl
Path:
src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java
src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java
src/test/java/org/jenkinsci/plugins/tokenmacro/TokenMacroTest.java
http://jenkins-ci.org/commit/token-macro-plugin/8c10736b54aac32f1590720fa2f843febaf31b32
Log:
Merge pull request #12 from slide/master
Fix JENKINS-18014
Compare: https://github.com/jenkinsci/token-macro-plugin/compare/766cdb04c67a...8c10736b54aa
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.
SCM/JIRA link daemon
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Code changed in jenkins
User: Alex Earl
Path:
src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java
src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java
src/test/java/org/jenkinsci/plugins/tokenmacro/TokenMacroTest.java
http://jenkins-ci.org/commit/token-macro-plugin/e1523eca5fb78fad1112193829ee4782620d9ce5
Log:
Fix JENKINS-18014
Changed the way that macros are escaped to using something similar to Groovy with two $'s. This required actually looking for the items that matched with two $'s and then handling that case special.
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.
Daniel Beck
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I understand that. To clarify:
\${ENV, var="VARNAME"} does not work for me (prints '\${ENV, var="VARNAME"}'), but \$VARNAME does work for me (prints '\value').
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I have a pull request in for the Token Macro plugin that would change the way escapes for tokens work. This should allow using \${ENV...}
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.
${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.
Daniel Beck
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I understand that. To clarify:
\${ENV, var="VARNAME"} does not work for me (prints '\${ENV, var="VARNAME"}'), but \$VARNAME does work for me (prints 'value').
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
The reason for that is the environment variables are actually replaced differently (through a mechanism in the Jenkins core, which doesn't support escaping). This replacement of environment variables is done before token macro does it's replacement.
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.
Nicolas De Loof
reopened JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Change By:
Nicolas De Loof
(11/Jun/13 9:01 AM)
Resolution:
Fixed
Status:
Resolved
Reopened
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.
Nicolas De Loof
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I can't find any way to get the negative lookbehind (?! to also consider an odd number of \.
I've tried (?!){0,1}) - as Java don't allow infinite lookbehinds - but then ${FOO} match.
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.
Nicolas De Loof
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I can't find any way to get the negative lookbehind
(?!\)
to also consider an odd number of \.
I've tried
(?!\(\\){0,1})
- as Java don't allow infinite lookbehinds - but then ${FOO} match.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I've been trying to play with this as well, I haven't come up with a good solution yet. I am wondering if a "real" parser might be necessary, but I don't want to go down that route if possible.
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.
Daniel Beck
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
What works for me is ${VARNAME}/$VARNAME instead of ${ENV, var="VARNAME"}.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
That will only work for environment variables
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.
Daniel Beck
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
True, but it's worth mentioning, since the comment by Ralf Rausch on 05/Jun/13 12:22 PM indicates it doesn't.
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.
Daniel Beck
edited a comment on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
What works for me is ${VARNAME} or $VARNAME instead of ${ENV, var="VARNAME"}.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
The issue that Eric was running into is that his ${ENV} token was preceeded by a \. The token itself works just fine. Please provide more information on your failure.
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] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Strange, I'll take a look. I tested with the new token-macro and it passed this type of case.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Hmmm, looks like the escaping fix didn't make it into Token Macro. I may need to do the fix differently anyhow.
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.
Alex Earl
resolved JENKINS-18014 as Fixed
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Changed token macro escape to use $$ instead of \$
Change By:
Alex Earl
(24/May/13 3:49 AM)
Status:
Open
Resolved
Resolution:
Fixed
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.
Eric Freeman
created JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
20/May/13 3:14 PM
Description:
After upgrading Email-ext plugin to 2.29 from 2.27.1 using the ${ENV, var="FOO"} format no longer works. $FOO does however. Once I reverted back to 2.27.1 it started working again.
Environment:
Jenkins 1.514
Project:
Jenkins
Priority:
Major
Reporter:
Eric Freeman
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Do you have the token-macro plugin installed?
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.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I do have the token-macro plugin installed. Is this a conflict causing an issue for me?
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I just tried with 2.29 and I was able to use both formats. ${ENV, var="USERNAME"} and $USERNAME both worked and produced the correct output. You need to verify that token-macro is installed and enabled.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
No, the email-ext plugin relies on the token-macro plugin. Please make sure token-macro is updated to 1.6
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.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I have that plugin installed and is version 1.6. I updated to 2.9 again and still see the same issue. Now I can't downgrade to 2.27.1 and I'm broken again unless I update all these variables.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Is there anything in the jenkins log? I can't reproduce this with the 1.508.1 LTS (which is what email-ext is based on for core dependency) + email-ext 2.29 and token-macro 1.6
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.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I have moved my Jenkins server back to 1.509.1...latest LTS. Same issue still exists.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Can you attach your job's config.xml (after stripping username/passwords/etc).
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.
Eric Freeman
updated JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Attached.
Change By:
Eric Freeman
(20/May/13 10:17 PM)
Attachment:
MyJobXML.xml
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
It's the \ in front of the $ I think. Token macro uses that as an escape character and the ENV token is now provided by the Token macro plugin.
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.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
So now we have to go change this in all of our jobs that use this? If I disable the token macro, will it work as is again? Why can't you leave existing functionality as is?
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
No, token macro is required for email-ext.
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.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I've been trying to figure out a way around this, as I know its frustrating, but because of the way that the tokens are implemented now (all tokens use the token macro plugin now), there really is no way around the way that Token Macro uses the escape. What issue did you have downgrading to 2.27.1?
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.
