Update the hatch env selection to act as the tox one #13644
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Modify the way we select environments when we are using hatch to mirror what we were doing with tox.
Motivation
latest
weekly pipeline is all red since we migrated to hatch https://dev.azure.com/datadoghq/integrations-core/_build/results?buildId=123628&view=logs&j=762a2123-1c7c-5bf0-0e62-04885c3ecd74&t=e42a329a-2791-53f4-67fc-ce0c85b45aedselect_hatch_envs
also returns non-existing envs, which was not the case with the tox version:integrations-core/datadog_checks_dev/datadog_checks/dev/tooling/testing.py
Lines 194 to 237 in 24983f2
Additional Notes
ddev -v env test --base --new-env --junit --ddtrace datadog_checks_base:latest
, it should generate a warn and not an errorReview checklist (to be filled by reviewers)
changelog/
andintegration/
labels attachedqa/skip-qa
label.