Just a thought, have you tried to set a publish directory as /htmlstuff/**? I 
think that means all subdirectories

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Schalk W. Cronjé
Sent: Thursday, October 10, 2013 9:39 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: HTML Report Publisher and FIle Hierarchies

That approach does not scale when the report contains 10k+ files.

I have subsequently discovered that I have generating incorrect relative links. 
It is only when the links point to directories that they still 404.


--
Schalk W. Cronjé
[Sent from mobile phone]



-------- Original message --------
From: Vivekanand S V <svvivekan...@gmail.com<mailto:svvivekan...@gmail.com>>
Date: 10/10/2013 14:29 (GMT+00:00)
To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>
Subject: Re: HTML Report Publisher and FIle Hierarchies

You should be able publish another html (By clicking the add button present 
below it) by giving the new directory in the 2nd one and giving file3.html as 
the file to archive. This is how I work with multiple HTML files.

On Thu, Oct 10, 2013 at 6:29 PM, Schalk Cronjé 
<ysb...@gmail.com<mailto:ysb...@gmail.com>> wrote:
Of late I have been doing custom HTML reports to be published in Jenkins. It 
seems that if files are in the same directories as the index page they can be 
referenced from Jenkins, but not if they are in a subdirectory.

To illustrate, if the following is the published index page then, file2 will be 
displayed, but file3.html with yield a 404 error.
<html><body>
  <a href='file2.html'>same_level</a>
  <a href='nested/file3.html'>in_subdir</a>
</body</html>

All of the files in the hierarchy will be archived,

Anyone know whether this is defined behaviour or a bug?
Tested on Jenkins 1.531 with HTML Publisher 1.2
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the Google 
Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/JPnL9KuQZiU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to