[JIRA] (JENKINS-53379) Source code not shown when using folders plugin

2019-03-18 Thread pst...@googlemail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil Taylor commented on  JENKINS-53379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Source code not shown when using folders plugin   
 

  
 
 
 
 

 
 Following a change in our build process, we are now seeing the source.  The change has been that the paths do not include going up a directory ( i.e. ../ ). The versions of plugins have not changed    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-53379) Source code not shown when using folders plugin

2018-09-01 Thread pst...@googlemail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil Taylor created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53379  
 
 
  Source code not shown when using folders plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Devin Nusbaum  
 
 
Components: 
 cloudbees-folder-plugin, cobertura-plugin  
 
 
Created: 
 2018-09-01 20:58  
 
 
Environment: 
 Ubuntu 18.04  Folder plugin 6.4  Cobertura plugin 1.12.1  
 
 
Labels: 
 cobertura folders  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Phil Taylor  
 

  
 
 
 
 

 
 When viewing coverage as a top level project, it is possible to view the source code highlighted with coverage. If a folder is used (or multiple levels of folder), then the plugin reports not being able find the source code to display.    We have used the same project just moved to a folder and then the source is not visible.   The source can be viewed locally, but then the project have to be cloned and built locally.   With the folder plugin, there are multiple /job/ entries (one per folder) which could be confusing the resolving of the link in CoverageResult.java