summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNate Liu <liunate@gmail.com>2019-03-15 09:02:28 +0000
committernateYourNanny <nateliu@tw.ibm.com>2019-03-15 17:35:58 +0800
commiteef3cc4201058a4f195300ba0df9797550cc4068 (patch)
tree817bc8ac4f98a0440856057edfaf37e53752322b
parent09669e2c3c60e7fbb0369d50ec30cd4490ce4846 (diff)
downloadgitlab-ce-eef3cc4201058a4f195300ba0df9797550cc4068.tar.gz
Correct Gradle files pattern matching description and example
`junit` files pattern matching should be globbing instead of regex.
-rw-r--r--doc/ci/junit_test_reports.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/junit_test_reports.md b/doc/ci/junit_test_reports.md
index cf18c6d9660..d03c0b68daf 100644
--- a/doc/ci/junit_test_reports.md
+++ b/doc/ci/junit_test_reports.md
@@ -113,8 +113,8 @@ There are a few tools that can produce JUnit reports in Java.
In the following example, `gradle` is used to generate the test reports.
If there are multiple test tasks defined, `gradle` will generate multiple
-directories under `build/test-results/`. In that case, you can leverage regex
-matching by defining the following path: `build/test-results/test/TEST-*.xml`:
+directories under `build/test-results/`. In that case, you can leverage glob
+matching by defining the following path: `build/test-results/test/**/TEST-*.xml`:
```yaml
java:
@@ -123,7 +123,7 @@ java:
- gradle test
artifacts:
reports:
- junit: build/test-results/test/TEST-*.xml
+ junit: build/test-results/test/**/TEST-*.xml
```
#### Maven