[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins

[dor...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dor Segal updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43038  
 
 
  Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins   
 

  
 
 
 
 

 
Change By: 
 Dor Segal  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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-15167) Parsing pom.xml failed due to '\t' character inside pom.xml

[dor...@gmail.com (JIRA)]

Dor B.D
 created  JENKINS-15167


Parsing pom.xml failed due to '\t' character inside pom.xml















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


maven



Created:


14/Sep/12 10:15 AM



Description:


Having '\t' escape code for tab inside pom.xml in case of maven project cause parsing error. As result, project can't be build, jenkins displays general parsing pom error. 

As solution i think: 
1. More details description for this error would have help me and others.
or 
2. Ignoring this kind of characters inside the pom while parsing it and allow to build + displaying a warning that this character found inside the pom and should be fixed.


	Note: Local build without jenkins, only maven, worked fine, which means, parsing error is in jenkins.






Due Date:


09/Sep/12 12:00 AM




Project:


Jenkins



Priority:


Minor



Reporter:


Dor B.D

























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