[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable It's available now (2.27) 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I meant when the new version of email-ext with your fix for this other ticket https://issues.jenkins-ci.org/browse/JENKINS-16916 will be available to upgrade to? 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I haven't implemented anything in regards to this ticket, so I am not sure what version it will get into. 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Thanks for clarifying about PROPFILE. As I am no longer using PROPFILE, I'll hold off on raising a ticket with the token-macro plug-in for PROPFILE not evaluating a path that contain an environment variable. Yes you are right. I could probably do what I have described above in this ticket with a groovy template and have the groovy do the job of evaluating the environment variable. But at present I've only been using plain-text e-mails. Though I do like the suggestion of using a groovy template, and it would be a good workaround for this issue. Do you know when the next version of email-ext with your changes will be made available? 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl edited a comment on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Also, you would be able to do this with a groovy template much easier, especially in the next version where I make it easier to use content tokens in the groovy template. See https://issues.jenkins-ci.org/browse/JENKINS-16916 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Also, you would be able to do this with a groovy template much easier, especially in the next version where I make it easier to use content tokens in the groovy template. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl edited a comment on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Propfile is not from email-ext, its from token-macro. Which means you would need to have someone fix it for that plugin too. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Propfile is not from email-ext, its from 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] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable The PROPFILE token also does not evaluate an environment variable when specified as part of the "file" variable for that token. So if it gets fixed for the FILE token, it would also be useful to have in the PROPFILE token or any token that allows you to specify a file path (FILE and PROPFILE tokens are the two that come to mind). 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Agreed. Actually in my implementation, I need unique files to be written into the workspace as I want my job to support concurrent builds. So having "staticname.txt" isn't ideal as it could get overwritten if two jobs are running at the same time. That's why I wanted to use an environment variable to specify the path in the FILE token where each instance of the running job would define its own unique value for the path in an environment variable. I will use this workaround for now until a fix is in place. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I'll leave this open and see if its something that I can add. It becomes less of a priority with the workaround, but I can see where it would be useful. 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Success! Thanks for the workaround Alex! I will use it . Here's the build step that worked for me (I'm running on Linux with the default shell):
echo "\${FILE,path=\"$MY_FILE_PATH\"}" > staticname.txt
I still think it would be nice to have the FILE token evaluate the environment variable specified in its "path" itself as that would avoid the extra build step, but for now, this workaround does what I want it to do.
Thanks again for your quick response and help!
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable You may need more escaping for the ", play around with 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 -- 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
edited a comment on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Ah I see. When I escaped the first $ in the token, this is what gets displayed in the e-mail:
${FILE, path=custom_info.txt}
So even though MY_FILE_PATH is properly evaluated to be "custom_info.txt", it looks like the nested functionality isn't working for me because it isn't evaluating "${FILE, path=custom_info.txt}" to display the contents of custom_info.txt.
The contents of staticname.txt is also:
${FILE, path=custom_info.txt}
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Ah I see. When I escaped the first $ in the token token, this is what gets displayed in the e-mail:
${FILE, path=custom_info.txt}
So even though MY_FILE_PATH is properly evaluated to be "custom_info.txt", it looks like the nested functionality isn't working for me because it isn't evaluating "${FILE, path=custom_info.txt}" to display the contents of custom_info.txt.
The contents of staticname.txt is also:
${FILE, path=custom_info.txt}
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Depending on what OS you are running on, you may need to escape the writing of the token to the file. I don't what the token to be replaced, I just want you to write it out to the file when you know the path to the file you want included in the email. The idea is to write the content you want ${FILE, path="custom_info.txt"}, when custom_info.txt is in your MY_FILE_PATH variable. You would want to escape the first $ in the token while writing it out to the file.
Build step:
echo \${FILE, path="$MY_FILE_PATH"} > staticname.txt
Email content:
${FILE, path="staticname.txt"}
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
edited a comment on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Hi Alex. I tried Step 1) that you've listed above but I get a "bad substitution" shell error and the build is marked as failed as a result. I don't think I can use the FILE token outside of the editable e-mail notification, should I be able to? Here is my syntax:
echo ${FILE, path="$MY_FILE_PATH"} > staticname.txt
where "MY_FILE_PATH" is an environment variable that I've specified in a property file that I've defined as part of "Prepare an environment for the run".
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Hi Alex. I tried Step 1) that you've listed above but I get a "bad substitution" shell error and the build is marked as failed as a result. I don't think I can use the FILE token outside of the editable e-mail notification, should I be able to? Here is my syntax:
echo ${FILE,path="$MY_FILE_PATH"} > staticname.txt
where "MY_FILE_PATH" is an environment variable that I've specified in a property file that I've defined as part of "Prepare an environment for the run".
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
That's not what I was trying to recommend, let me try and rephrase.
1) Create a build step that creates a file in the workspace like this:
echo ${FILE, path="%PATH_TO_FILE%"} > staticname.txt
2) Use the following as the token in the email
${FILE, path="staticname.txt"}
The staticname.txt does not use a variable since you know the name of the file you are creating.
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Alex, thanks for the suggestion. I tried out the workaround and you are right that the FILE token allows for nested content. However, when the nested content is a FILE token that uses an environment variable in the "path", it does not evaluate the environment variable. So the same problem occurs. Nesting does not rectify the problem. I think the issue is inherent in the FILE token interpretation itself. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Kavita, I agree. I need to determine how best to do what you want. One workaround I might propose for now would be to generate a file with the ${FILE, path="real_path_here"} when you know the env variable works to specify the path to the file. Then use that generated file in the email template, the FILE token allows for nested content, so it should read the file, then replace the FILE token inside with the content you are looking for. Let me know if you need more information.
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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I think Valerie's issue was different from mine as the FILE token itself works fine for me. What does not work is the evaluation of an environment variable in the "path" for the FILE token. I am running email-ext - 2.24.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.
[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Valerie Wagner commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Restarting Jenkins seems to have done the trick! That and getting the right combination of spaces and double-quotes. thanks for all your help! 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable There is a test case in place for the build for this token, so I know the token itself works. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Yes, when you upgrade plugins, you need to restart Jenkins. 2.21 would definitely throw the exception for a file it couldn't find. 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-16716) FILE token does not evaluate a path that contains an environment variable
Valerie Wagner commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Yes, the file definitely exists. I'm using 2.21. Actually I thought I upgraded to 2.25 earlier today in an attempt to see if it would fix it, but perhaps I need to restart Jenkins to get that to take effect. I'll give it a try. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable That file exists relative to the workspace root? Also, what version of the plugin are you using? There was a version that threw an exception like you are seeing if the file didn't exist. I fixed that, but I don't remember what version it was. 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-16716) FILE token does not evaluate a path that contains an environment variable
Valerie Wagner
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
I don't want to hijack this issue if mine is different. But perhaps adding a space above will solve kavita's original problem. As far as I can tell, this is exactly what my syntax should be:
${FILE, path="sw/java/libs/testutils/build/testng-changes.html"}
I've triple checked that the path is right & the file exists. Incidentally, this now gives me an exception:
ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
at java.util.regex.Matcher.quoteReplacement(Matcher.java:655)
at hudson.plugins.emailext.plugins.ContentBuilder$Tokenizer.appendReplacement(ContentBuilder.java:211)
at hudson.plugins.emailext.plugins.ContentBuilder.replaceTokensWithContent(ContentBuilder.java:112)
at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:82)
at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:482)
at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:314)
at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259)
at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251)
at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
at hudson.model.Run.execute(Run.java:1601)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:236)
Perhaps I should open a separate issue?
Thanks for your help!
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Hmmm, I'll give it a shot locally. 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-16716) FILE token does not evaluate a path that contains an environment variable
Valerie Wagner commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable I've tried it with & without a space. And with relative paths. Neither works 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] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable It only works with workspace relative paths. Also, you need a space between the , and the path. 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-16716) FILE token does not evaluate a path that contains an environment variable
Valerie Wagner
commented on JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Does the $FILE token work at all? I'm trying to use it with literal paths and I get the same result as you once your environment variable has been substituted. Perhaps it's not the variable replacement that is broken but the file inclusion mechanism itself.
If I put in something like:
${FILE,path="custom_info.txt"}
That literal string appears in my email. I've tried all sorts of combinations of relative & absolute paths and I can't get any other result.
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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl assigned JENKINS-16716 to Alex Earl FILE token does not evaluate a path that contains an environment variable Change By: Alex Earl (08/Feb/13 8:37 PM) Assignee: Alex Earl 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-16716) FILE token does not evaluate a path that contains an environment variable
Kavita Tiwari
created JENKINS-16716
FILE token does not evaluate a path that contains an environment variable
Issue Type:
Improvement
Assignee:
Unassigned
Components:
email-ext
Created:
08/Feb/13 6:36 PM
Description:
When I try the following in the Default Content of the Editable E-mail Notification:
${FILE,path="$MY_FILE_PATH"}
The contents of the file specified by the path do not get displayed. I have MY_FILE_PATH defined as a property in a properties file that is injected into the environment in the "Prepare an environment for the run" option where the full path of the property file is specified.
The property file defines: MY_FILE_PATH=custom_info.txt
where "custom_info.txt" is a file in the workspace of the job that contains some text that I would like to display as part of the e-mail.
What is strange is that when I receive the e-mail, this appears:
${FILE,path="custom_info.txt"}
So the email-ext plugin evaluates the environment variable MY_FILE_PATH, but the FILE token does not evaluate it as a path.
The ability to have the FILE token evaluate a path that contains an environment variable would be useful for displaying different information depending on which file path is stored in the environment variable.
I am running Jenkins 1.480.2.
Due Date:
15/Feb/13 12:00 AM
Project:
Jenkins
Priority:
Minor
Reporter:
Kavita Tiwari
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.
