-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[CIAPP] Document support for logs in CI Visibility junit XML upload #13680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CIAPP] Document support for logs in CI Visibility junit XML upload #13680
Conversation
1796c2d
to
2762174
Compare
2762174
to
034719b
Compare
@@ -118,6 +116,11 @@ This is the full list of options available when using the `datadog-ci junit uplo | |||
**Example**: `team:backend`<br/> | |||
**Note**: Tags specified using `--tags` and with the `DD_TAGS` environment variable are merged. If the same key appears in both `--tags` and `DD_TAGS`, the value in the environment variable `DD_TAGS` takes precedence. | |||
|
|||
`--logs` **(beta)** | |||
: Enable forwarding content from the XML reports as [Logs][7]. The content inside `<system-out>`, `<system-err>`, `<failure>` will be loaded. Logs from elements inside a `<testcase>` are automatically connected to test.<br/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
: Enable forwarding content from the XML reports as [Logs][7]. The content inside `<system-out>`, `<system-err>`, `<failure>` will be loaded. Logs from elements inside a `<testcase>` are automatically connected to test.<br/> | |
: Enable forwarding content from the XML reports as [Logs][7]. The content inside `<system-out>`, `<system-err>`, `<failure>` will be sent to the Logs system. Logs from elements inside a `<testcase>` are automatically linked to the test.<br/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I used the word connected because of https://docs.datadoghq.com/tracing/connect_logs_and_traces/ but good suggestions for the others I'll make the changes
`--logs` **(beta)** | ||
: Enable forwarding content from the XML reports as [Logs][7]. The content inside `<system-out>`, `<system-err>`, `<failure>` is collected as logs. Logs from elements inside a `<testcase>` are automatically connected to the test.<br/> | ||
**Default**: `false`<br/> | ||
**Note**: Logs are billed separately from CI Visibility. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Fernando Mayo <fernando@datadog.com>
d29f2a1
to
5a6b463
Compare
When this is ready for merge, please remove the github label and ping us in the documentation channel in slack! :) Thanks! |
What does this PR do?
Document a new feature when uploading test report in XML to CI Visibility. A new CLI flag and environment variable enables this additional feature where the logs will be forwarded to the logs product and connected to the tests in CI Visibility.
This was added in DataDog/datadog-ci#510
Preview
https://docs-staging.datadoghq.com/adrian.lopezcalvo%2Fci-visibility-junitxml-logs-support
Reviewer checklist