[jbosstools-issues] [JBoss JIRA] (JBIDE-13155) Links to code coverage data file jacoco.exec are broken for some components
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Tue Nov 27 12:04:21 EST 2012
[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737440#comment-12737440 ]
Nick Boldt commented on JBIDE-13155:
------------------------------------
FWIW, the coverage report DOES work. I tweaked the "multicomponent" jobs to make them appear, but I guess I didn't verify the jacoco.exe file was appearing as well.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.component--javaee/lastSuccessfulBuild/artifact/sources/target/coverage-report/html/JaCoCo-Multi/index.html
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.component--javaee/lastSuccessfulBuild/artifact/sources/target/jacoco.exec (404'd)
Or maybe the job config changes I did got accidentally reverted.
Basically, the required change for multicomponent jobs is this, when archiving build artifacts:
{code}
-sources/target/jacoco.exec
+sources/*/target/jacoco.exec
{code}
Or, if applied to all (multi- or single) component jobs:
{code}
-sources/target/jacoco.exec
+sources/target/jacoco.exec,sources/*/target/jacoco.exec
{code}
> Links to code coverage data file jacoco.exec are broken for some components
> ---------------------------------------------------------------------------
>
> Key: JBIDE-13155
> URL: https://issues.jboss.org/browse/JBIDE-13155
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Vlado Pakan
> Assignee: Mickael Istria
>
> jacoco.exec files are not available for these modules on Jenkins jobs for JBT 4.0 stable branch: base, birt, central-maven-examples, javaee, server.
> Each job has a link to jacoco.exec file but while navigating to this link within jobs of modules listed above "HTTP Status 404 -" error web page is displayed.
--
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
More information about the jbosstools-issues
mailing list