[JIRA] [email-ext] (JENKINS-17675) Allow the Pre-send script to be a file or call a scriptler script
Kavita Tiwari commented on JENKINS-17675 Allow the Pre-send script to be a file or call a scriptler script Great! Thanks Alex! 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-17675) Allow the Pre-send script to be a file or call a scriptler script
Kavita Tiwari commented on JENKINS-17675 Allow the Pre-send script to be a file or call a scriptler script Hi Alex, can you elaborate a bit on how content tokens can be used in the pre-send script? I can't find any groovy code examples of how to achieve this. E.g. for the FILE content token? 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
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
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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin Upgraded email-ext to 2.25 and it works! Thanks very much Alex! This issue can be closed. 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
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
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
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
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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari commented on JENKINS-16779 PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin No worries. I'm using token-macro - 1.5.1. Looking at the release notes for the token-macro plugin, it "Added macro for retrieving properties from property files in the build workspace." in Version 1.3. 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-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari
commented on JENKINS-16779
PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
When I look at the "Content Token Reference" help for the email-ext plugin this appears:
Token Macro Plugin Tokens
${BUILD_NUMBER}
Expands to the current build number, a sequential auto-incrementing unique number that identifies the build, such as "125"
${ENV,var="VARIABLENAME"}
Expands to an environment variable (specified here as VARIABLENAME) from the build environment. Note that this does not include any variables set by the build scripts themselves, only those set by Jenkins and other plugins.
${PROPFILE,file="FILENAME",property="PROPERTYNAME"}
Expands to the value of a property in a property file. The filename is relative to the build workspace root.
It shows PROPFILE as a token-macro plugin token that can be used by the email-ext plugin. The other tokens listed above work (BUILD_NUMBER and ENV). As such, I figured that it could be used by the email-ext 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] (JENKINS-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Kavita Tiwari
created JENKINS-16779
PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext, token-macro
Created:
12/Feb/13 4:55 PM
Description:
The PROPFILE token is not evaluating in the Editable E-mail Notification for the e-mail-ext plugin.
For example, when I put this in the Default Content of the e-mail:
${PROPFILE,file="props.cfg",property="TESTING_VAR"}
The value of "TESTING_VAR" is not displayed in the e-mail. Instead, this is displayed:
${PROPFILE,file="props.cfg",property="TESTING_VAR"}
This PROPFILE token works when I put it in the "Set Build Name" field for the build-name-setter plugin.
So the build-name-setter plugin is able to consume the PROPFILE token, but the e-mail-ext plugin does not seem to be consuming it properly.
I am running Jenkins 1.480.2 with email-ext - 2.24.1.
Due Date:
19/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.
[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
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.
