|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14210) EMAIL-EXT - FILE tok... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)
- [JIRA] (JENKINS-14210) EMAIL-EXT - FIL... [email protected] (JIRA)

I agree.
But, In my case, the file sits at the workspace (file system location) and Jenkins is working fine except for the fact that it's not expanding ${JELLY_SCRIPT...} further. I'm planning to version this file (giga.txt) as well therefore, if we get this nested thing done, then, we'll server / meet all the guidelines and our requirement will meet as well.