You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide/writing-tasks.md
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -175,6 +175,7 @@ build_and_test_task:
175
175
always:
176
176
junit_artifacts:
177
177
path: "**/test-results/**/*.xml"
178
+
format: junit
178
179
```
179
180
180
181
!!! tip "URL to the latest artifacts"
@@ -184,6 +185,20 @@ build_and_test_task:
184
185
```yaml
185
186
https://api.cirrus-ci.com/v1/artifact/github/<USER OR ORGANIZATION>/<REPOSITORY>/<TASK NAME>/<ARTIFACTS NAME>/<PATH>
186
187
```
188
+
189
+
### Artifact Format
190
+
191
+
Cirrus CI supports parsing artifacts in order to extract information that can be presented in the UI for better user experience.
192
+
Simply use `format` field of an artifact instruction to specify artifact's format:
193
+
194
+
```yaml
195
+
junit_artifacts:
196
+
path: "**/test-results/**/*.xml"
197
+
format: junit
198
+
```
199
+
200
+
Currently Cirrus CI can only parse JUnit XML artifacts but many tools use this format already. Please [let us know](https://github.com/cirruslabs/cirrus-ci-annotations/issues/new)
201
+
what kind of formats Cirrus CI should support next!
0 commit comments