<< Back to previous view |
![]() |
[QB-1916] Publishing artifacts which are also referred by HTML pages are duplicate on storage
|
|
Status: | Reopened |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | 5.1.7 |
Fix Version/s: | None |
Type: | Improvement | Priority: | Major |
Reporter: | Maikel vd Hurk | Assigned To: | Robin Shen |
Resolution: | Unresolved | Votes: | 1 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown |
Description |
Publishing artifacts which are also referred by HTML pages are duplicate on storage. In case you have following steps in configuration:
Publish artifacts => a.log,b.log,c.log Publish HTML report => index.html (referring to a.log,b.log,c.log) This will create: builds/artifacts/a.log builds/artifacts/b.log builds/artifacts/c.log builds/html/index.html builds/html/a.log builds/html/b.log builds/html/c.log |
Comments |
Comment by Robin Shen [ 21/Jan/14 12:05 AM ] |
QB does not publish files under builds/html directly, also it does not publish files referred from index.html automatically unless they are contained in the directory you specified when you define the html publish step. Can you please show me how your artifact and html publishing steps are defined? And what contents is inside the original directory being published? |
Comment by Maikel vd Hurk [ 21/Jan/14 02:22 AM ] |
Root folder containing logs and html: test-results/
Artifact step: -directory: test-results -files to publish: *.log -destination: test-results Html step: -directory: test-results -files to publish: *.log and *.html (to avoid broken links) -start page: index.html I know you could remove in html step the log files to publish, resulting in broken links. We want to be able to access them in both html and artifacts way. |
Comment by Robin Shen [ 22/Jan/14 12:58 AM ] |
This can be done by modifying html links in your index.html to point to various log in this way:
../../artifacts/a.log ../../artifacts/b.log Then you only need to publish log files in artifact publishing step. |
Comment by Maikel vd Hurk [ 22/Jan/14 09:14 AM ] |
I don't agree with modifying the HTML report, because if a developer would run locally then he will not have the separation between artifacts and html directory and both files will live next to each other. What is added value on QB side to make separation of directories? |
Comment by Robin Shen [ 22/Jan/14 09:30 AM ] |
We separate html reports from artifacts as it is often desirable to have different reports for a build, which can not suited well directly in artifacts window. |
Comment by Maikel vd Hurk [ 22/Jan/14 09:36 AM ] |
Oke make sense, but in my view creating a tailored HTML report only for QuickBuild need is also not desirable. You would like to have transparency between report generated on local development machine and CI report generated. |
Comment by Robin Shen [ 22/Jan/14 09:58 AM ] |
Reopen this issue.
QB should be able to be enhanced to define html reports to show files in artifacts directory directly, in addition to the ability to publish a separate html report directory. |