[JIRA] (JENKINS-37594) email-ext plugin can't recognize content file in workspace

2016-09-23 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37594  
 
 
  email-ext plugin can't recognize content file in workspace
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-37594) email-ext plugin can't recognize content file in workspace

2016-09-16 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-37594  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: email-ext plugin can't recognize content file in workspace
 

  
 
 
 
 

 
 Works for me on osx. see screen shots  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-37594) email-ext plugin can't recognize content file in workspace

2016-09-16 Thread da...@vanlaatum.id.au (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37594  
 
 
  email-ext plugin can't recognize content file in workspace
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Attachment: 
 Screen Shot 2016-09-17 at 12.04.21 PM.png  
 
 
Attachment: 
 Screen Shot 2016-09-17 at 12.04.57 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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/d/optout.


[JIRA] (JENKINS-37594) email-ext plugin can't recognize content file in workspace

2016-08-22 Thread gordon.mad...@biotronik.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gordon Madden created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37594  
 
 
  email-ext plugin can't recognize content file in workspace
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2016/Aug/22 5:36 PM  
 
 
Environment: 
 email-ext plugin, Jenkins 1.651.3, Windows 7  
 
 
Labels: 
 plugin jenkins  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Gordon Madden  
 

  
 
 
 
 

 
 Set up email notification for any failed test. Created an html file and placed in root of workspace. Specified $ {FILE, path="all_failed.html"}  in the content block for the notification. Email is sent upon a failure, but the file pointed to by the content block cannot be found. Get the email message as: ERROR: File 'any_failure.html' does not exist Tried it with variations of spaces, quotes, and different types of files. Checked the syntax against the Content Token Reference (help question mark link) in the project configuration. Cannot get the content from the file.  Tried moving the file and setting the path to the full path (referenced from "C:\") and also using the relative path to the workspace. Has anyone gotten this feature to work?