[
https://issues.jboss.org/browse/JBIDE-12742?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12742:
----------------------------------------
Not sure that anyone would use coverage reports from a branch: coverage is a subtle
quality metrics (as opposed to acceptance quality metrics - such as test results), a
branch is generally not the place to work on such stuff.
make code coverage reports easier to find & aggregate them into a
simpler all-in-one view?
------------------------------------------------------------------------------------------
Key: JBIDE-12742
URL:
https://issues.jboss.org/browse/JBIDE-12742
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, testing
Affects Versions: 4.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.0.0.Alpha2
Attachments: 12742-cleaned-up-UI.png, 12742-cleaned-up-UI_individual_build.png
Could we...
* archive artifacts in the jobs, eg., to make it easier to find this page [1] ?
* ensure the coverage report stuff is published to
download.jboss.org, eg., in here [2]
?
* collect all the coverage reports from the various jobs [2] into a single place [3] ?
[1]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
[2]
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk....
[3]
http://download.jboss.org/jbosstools/builds/staging/_coverage-reports_/
--
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