ansible/.azure-pipelines/scripts/report-coverage.sh

#!/usr/bin/env bash
# Generate code coverage reports for uploading to Azure Pipelines and codecov.io.

set -o pipefail -eu

PATH="${PWD}/bin:${PATH}"

if ! ansible-test --help >/dev/null 2>&1; then
    # Install the devel version of ansible-test for generating code coverage reports.
    # This is only used by Ansible Collections, which are typically tested against multiple Ansible versions (in separate jobs).
    # Since a version of ansible-test is required that can work the output from multiple older releases, the devel version is used.
    pip install https://github.com/ansible/ansible/archive/devel.tar.gz --disable-pip-version-check
fi

# Generate stubs using docker (if supported) otherwise fall back to using a virtual environment instead.
# The use of docker is required when Powershell code is present, but Ansible 2.12 was the first version to support --docker with coverage.
ansible-test coverage xml --group-by command --stub --docker --color -v || ansible-test coverage xml --group-by command --stub --venv --color -v
[devel] Azure Pipelines configuration. 4 years ago			`#!/usr/bin/env bash`
			`# Generate code coverage reports for uploading to Azure Pipelines and codecov.io.`

			`set -o pipefail -eu`

			`PATH="${PWD}/bin:${PATH}"`

Update Azure Pipelines scripts and config. (#72986) * Increase fetch depth to reduce the frequency of full test runs for out-of-date PRs. * Update scripts to match those which will be used in collections. 4 years ago			`if ! ansible-test --help >/dev/null 2>&1; then`
			`# Install the devel version of ansible-test for generating code coverage reports.`
			`# This is only used by Ansible Collections, which are typically tested against multiple Ansible versions (in separate jobs).`
			`# Since a version of ansible-test is required that can work the output from multiple older releases, the devel version is used.`
			`pip install https://github.com/ansible/ansible/archive/devel.tar.gz --disable-pip-version-check`
			`fi`

Add fallback for coverage report generation. This should allow the same script to be used for two different scenarios: - ansible-core across multiple versions (not all of which support `--docker` for coverage reports) - collections (which should always use the `devel` branch for coverage reports) 4 years ago			`# Generate stubs using docker (if supported) otherwise fall back to using a virtual environment instead.`
			`# The use of docker is required when Powershell code is present, but Ansible 2.12 was the first version to support --docker with coverage.`
Avoid system-site-packages in AZP coverage venvs. The use of `--venv-system-site-packages` was an optimization to use the `coverage` package pre-installed in the AZP test container. However, now that the venv is bootstrapped by ansible-test that optimization no longer makes sense, since other downloads are already taking place. ci_coverage ci_complete 3 years ago			`ansible-test coverage xml --group-by command --stub --docker --color -v \|\| ansible-test coverage xml --group-by command --stub --venv --color -v`