[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-13155: -------------------------------- Description: 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13155: ---------------------------------------- Actually this happens to all "2 deep" builds because of relative path to jacoco.exec has changed. I'd be tempted to have a single jacoco.exec for the whole build, so it would require to override the jacoco.report.path on pom.xml of "big" components. WDYT? -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] 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... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... (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} -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13155: ---------------------------------------- [~nickboldt]: I think the "sources/target/jacoco.exec,sources/*/target/jacoco.exec" would work perfectly. [~vpakan]: Then we now go for 1 job = N jacoco.exec. I'm wondering what would be a good way to expose those different jacoco.exec in Jenkins to encourage developers to use it. -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13155: --------------------------------------- -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13155 at 11/27/12 10:39 PM: --------------------------------------------------------------- Fixed in 4 x 2 jobs (stable_branch and trunk) for javaee, server, central-maven-examples and base. Here's an example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... Denis, Vlado, Mickael: if happy with this solution, please close this jira. was (Author: nickboldt): Fixed in 4 x 2 jobs (stable_branch and trunk) for javaee, server, central-maven-examples and base. Here's an example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13155: ---------------------------------------- Ok, you can already do this. {code} $ mvn verify -f tests/my.magic.test/pom.xml {code} and then enjoy your target/jacoco.exec in EclEmma Coverage is here to spot which pieces of code are not covered and should have more testing love. Having a component-wide grain of analysis allows to find out where to put efforts on the whole component. Although I don't use them extensively, I feel these reports are (or will be) useful. The jacoco.exec are not archived, so we only keep the jacoco.exec of the latest build. I tend to think that as long as we don't have complaints, it's not bad. -- 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

[ https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-13155: ------------------------------------- New Jira for wrong report data JBIDE-13166 -- 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