ansible-lint2junit

Converts ansible-lint output into JUnit XML, so lint findings show up as test results in CI — in particular in GitLab's test report UI.

This is a fork of wasilak/ansible-lint-junit (MIT licensed), renamed and modernised for GitLab (Python 3.9+):

• Testcases carry a stable identity (classname = ansible-lint rule ID, name = file:line message), so GitLab can track newly-failed/resolved findings between pipeline runs.
• Testcases carry a file attribute, so GitLab links each finding to the source file.
• Suite tests/failures counts reflect the actual findings (summary lines and blanks are ignored).
• No longer depends on ansible-lint itself — only its text output — so it installs cleanly alongside any ansible-lint version (the only dependency is defusedxml).
• ANSI colour codes are stripped from the input, so forgetting --nocolor doesn't silently produce an empty report.
• --fail-on-findings lets one CI step both publish the report and fail the job.

Installation

From PyPI:

pip install ansible-lint2junit

or from this project's GitLab package registry:

pip install ansible-lint2junit --index-url https://gitlab.surrey.ac.uk/api/v4/projects/sm0049%2Fansible-lint2junit/packages/pypi/simple

Usage

Pipe ansible-lint -p output in:

ansible-lint playbook.yml -p --nocolor | ansible-lint2junit -o ansible-lint.xml

or go via a file (multiple input files are concatenated):

ansible-lint -p --nocolor playbook.yml > ansible-lint.txt
ansible-lint2junit ansible-lint.txt -o ansible-lint.xml

Options:

If the input is non-empty but no line matches the file:line: message format, a warning is printed to stderr — usually a sign the input wasn't produced with -p.

GitLab CI example

ansible-lint:
  image: python:3.13
  script:
    - pip install ansible-lint
    - pip install ansible-lint2junit --index-url https://gitlab.surrey.ac.uk/api/v4/projects/sm0049%2Fansible-lint2junit/packages/pypi/simple
    - ansible-lint -p --nocolor . > ansible-lint.txt || true
    - ansible-lint2junit ansible-lint.txt -o ansible-lint.xml --fail-on-findings
  artifacts:
    when: always
    reports:
      junit: ansible-lint.xml

The || true keeps the job running so the report is always generated; --fail-on-findings then fails the job when there are findings, after the report exists. Drop it if lint findings should not fail the pipeline.

Output

• Findings become JUnit <failure> testcases, grouped by ansible-lint rule.
• Clean input still produces a valid (empty) JUnit XML file, so JUnit parsers that fail on a missing report (e.g. Bamboo) keep working. Use -d for parsers that also reject suites with zero tests.
• Both modern ansible-lint (rule-id[subrule] message) and legacy ([E301] message) output formats are recognised; unrecognised lines that still look like file:line: message are kept with a generic ansible-lint classname.

Development

pip install -e '.[test]'
pytest                  # tests (with coverage in CI)
ruff check . && ruff format --check .   # lint/format (pip install ruff)
mypy                    # type check (pip install mypy)

License

Distributed under the MIT license, as is the original project by Piotr Boruc.