bdae72ef6c
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)
18 lines
1 KiB
Bash
Executable file
18 lines
1 KiB
Bash
Executable file
#!/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 --stub --docker --color -v || ansible-test coverage xml --stub --venv --venv-system-site-packages --color -v
|