[
https://issues.apache.org/jira/browse/MESOS-4258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090360#comment-15090360
]
Shuai Lin commented on MESOS-4258:
----------------------------------
Besides the patch, this would also require a Jenkis admin to configure the
locations of the xml files, as described in the "Configuration" section of
[Jenkins xUnit Plugin
Page|https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin]. Here we have
three xml reports:
- 3rdparty/libprocess/3rdparty/report.xml
- 3rdparty/libprocess/report.xml
- src/report.xml
> Generate xml test reports in the jenkins build.
> -----------------------------------------------
>
> Key: MESOS-4258
> URL: https://issues.apache.org/jira/browse/MESOS-4258
> Project: Mesos
> Issue Type: Task
> Components: test
> Reporter: Benjamin Mahler
> Assignee: Shuai Lin
> Labels: newbie
>
> Google test has a flag for generating reports:
> {{--gtest_output=xml:report.xml}}
> Jenkins can display these reports via the xUnit plugin, which has support for
> google test xml: https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin
> This lets us quickly see which test failed, as well as the time that each
> test took to run.
> We should wire this up. One difficulty is that 'make distclean' complains
> because the .xml files are left over (we could update distclean to wipe any
> .xml files within the test locations):
> {noformat}
> ERROR: files left in build directory after distclean:
> ./3rdparty/libprocess/3rdparty/report.xml
> ./3rdparty/libprocess/report.xml
> ./src/report.xml
> make[1]: *** [distcleancheck] Error 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
