[jbosstools-issues] [JBoss JIRA] (JBIDE-19058) refactor output.html and product.html into report_detailed.html and report_summary.html

Nick Boldt (JIRA) issues at jboss.org
Mon Jan 26 20:53:49 EST 2015


     [ https://issues.jboss.org/browse/JBIDE-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt reassigned JBIDE-19058:
----------------------------------

    Assignee: Nick Boldt


> refactor output.html and product.html into report_detailed.html and report_summary.html
> ---------------------------------------------------------------------------------------
>
>                 Key: JBIDE-19058
>                 URL: https://issues.jboss.org/browse/JBIDE-19058
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, qa
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> Today, vwatch produces two files:
> * a detailed, tabular report called "output.hml"
> * a summary report called "product.html"
> In Jenkins, I then rename these to results*.html and report*.html, which is a bit confusing because the files are not listed next to each other in the http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatch_master/ folder.
> So, I propose we generate the files with these names:
> * report_detailed.html
> * report_summary.html
> Then in Jenkins we can simply rename them to include a timestamp/buildID prefix, and continue to differentiate the "all" report from the org.jboss-only "filtered" report:
> * 2015-01-07_17-28-06_B1766_report_detailed_all.html
> * 2015-01-07_17-28-06_B1766_report_detailed_filtered.html
> * 2015-01-07_17-28-06_B1766_report_summary_all.html
> * 2015-01-07_17-28-06_B1766_report_summary_filtered.html



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jbosstools-issues mailing list