Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.
What does this PR do?
Adds support for configuring Test Visibility in pipeline scripts using datadog step.
A new testVisibility property is added to the step, allowing to use automatic Test Visibility configuration in pipelines that do not support UI config (e.g. multi-branch pipelines found inside organization folders).
Description of the Change
If datadog step is present in the pipeline definition and testVisibility block is configured, DatadogTracerJobProperty property is registered in the job.
Existing code that handles the property does the rest.
Alternate Designs
Possible Drawbacks
Verification Process
Verified manually using a local Jenkins instance.
Integration test added.
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.
Requirements for Contributing to this repository
What does this PR do?
Adds support for configuring Test Visibility in pipeline scripts using
datadogstep. A newtestVisibilityproperty is added to the step, allowing to use automatic Test Visibility configuration in pipelines that do not support UI config (e.g. multi-branch pipelines found inside organization folders).Description of the Change
If
datadogstep is present in the pipeline definition andtestVisibilityblock is configured,DatadogTracerJobPropertyproperty is registered in the job. Existing code that handles the property does the rest.Alternate Designs
Possible Drawbacks
Verification Process
Verified manually using a local Jenkins instance. Integration test added.
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
changelog/label attached. If applicable it should have thebackward-incompatiblelabel attached.do-not-merge/label attached.kind/andseverity/labels attached at least.