Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
cc34f740
Commit
cc34f740
authored
Aug 28, 2018
by
Leo
Committed by
Achilleas Pipinellis
Sep 03, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add Java Maven example to junit_test_reports.md
parent
5fb044b0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
3 deletions
+19
-3
doc/ci/junit_test_reports.md
doc/ci/junit_test_reports.md
+19
-3
No files found.
doc/ci/junit_test_reports.md
View file @
cc34f740
...
...
@@ -116,7 +116,23 @@ java:
junit
:
build/test-results/test/TEST-*.xml
```
If you define multiple tasks of kind test, it will generate multiple directories
under
`build/test-results/`
directory.
To address all subdirectory at once, you can leverage regex matching by defining following
If you define multiple tasks of kind test, it will generate multiple directories
under
`build/test-results/`
directory.
To address all subdirectory at once, you can leverage regex matching by defining following
path:
`build/test-results/test/TEST-*.xml`
### Java example with Maven
For parsing Surefire and Failsafe test resports use the following job in
`.gitlab-ci.yml`
:
```
yaml
java
:
stage
:
test
script
:
-
mvn verify
artifacts
:
reports
:
junit
:
-
target/surefire-reports/TEST-*.xml
-
target/failsafe-reports/TEST-*.xml
```
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment