Skip to content

ci: Comply with Ansible partner certification checking [citest_skip]#230

Merged
richm merged 1 commit intomainfrom
ci-ansible-lint-ansible-test-matrix
Apr 8, 2026
Merged

ci: Comply with Ansible partner certification checking [citest_skip]#230
richm merged 1 commit intomainfrom
ci-ansible-lint-ansible-test-matrix

Conversation

@richm
Copy link
Copy Markdown
Contributor

@richm richm commented Apr 8, 2026

https://github.com/ansible-collections/partner-certification-checker/blob/main/README.md

Unfortunately we cannot use the checkers provided by their team because they assume
the git repo is in collection format - you cannot convert to collection format first
then point the checkers at that collection. Instead, implement our own checkers that
do the same (and more) - check with multiple versions of ansible-lint and ansible-test
to ensure we cover:

  • all supported versions of EL
  • Automation Hub gating
  • the latest versions of Ansible, including the latest milestone version

This requires the latest version of tox-lsr

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Update CI workflows to align with Ansible partner certification checks by running linting and testing across multiple Ansible and Python versions via tox.

CI:

  • Run ansible-lint in CI against multiple ansible-lint/ansible-core/Python version combinations using a matrix strategy and tox instead of the ansible-lint GitHub Action.
  • Run ansible-test sanity checks in CI across a matrix of supported Ansible and Python versions via tox instead of the ansible-test GitHub Action.
  • Upgrade all GitHub workflows to use tox-lsr version 3.18.0.

https://github.com/ansible-collections/partner-certification-checker/blob/main/README.md

Unfortunately we cannot use the checkers provided by their team because they assume
the git repo is in collection format - you cannot convert to collection format first
then point the checkers at that collection.  Instead, implement our own checkers that
do the same (and more) - check with multiple versions of ansible-lint and ansible-test
to ensure we cover:

* all supported versions of EL
* Automation Hub gating
* the latest versions of Ansible, including the latest milestone version

This requires the latest version of tox-lsr

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
@richm richm self-assigned this Apr 8, 2026
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Apr 8, 2026

Reviewer's Guide

Updates CI workflows to align with Ansible partner certification requirements by running ansible-lint and ansible-test across specific Ansible/Python version matrices via tox-lsr 3.18.0, replacing direct GitHub Actions integrations and centralizing collection conversion and testing in tox.

Flow diagram for updated ansible_lint workflow with version matrix

flowchart TD
  A["Trigger ansible-lint workflow"] --> B{"Event allowed (no citest_skip)"}
  B -- No --> Z["Skip workflow"]
  B -- Yes --> C["Set up strategy matrix
  versions:
  1) ansible-lint 24.* / ansible-core 2.16.* / python 3.12
  2) ansible-lint 26.* / ansible-core 2.20.* / python 3.13"]

  C --> D["Update pip and git"]
  D --> E["Install tox and tox-lsr 3.18.0 via pip3"]
  E --> F["Set up Python using actions/setup-python
  python-version = matrix.versions.python"]
  F --> G["Run tox for collection and ansible-lint-collection
  with matrix-specific deps:
  LSR_ANSIBLE_LINT_DEP = ansible-lint==matrix.versions.ansible_lint
  LSR_ANSIBLE_LINT_ANSIBLE_DEP = ansible-core==matrix.versions.ansible"]
  G --> H["Tox env collection converts role to collection format"]
  H --> I["Tox env ansible-lint-collection runs ansible-lint against collection"]
  I --> J["Report job result for this matrix entry"]
  J --> K{"All matrix entries finished"}
  K -- No --> C
  K -- Yes --> L["Complete ansible-lint workflow"]
Loading

File-Level Changes

Change Details Files
Run ansible-lint via tox in a versioned matrix instead of the ansible-lint GitHub Action.
  • Added a strategy matrix over ansible-lint, ansible-core, and Python versions with fail-fast disabled for the ansible-lint workflow job.
  • Upgraded tox-lsr to version 3.18.0 in the ansible-lint workflow.
  • Introduced an actions/setup-python step using the matrix Python version.
  • Replaced the bespoke collection conversion plus ansible-lint GitHub Action invocation with a single tox command that converts to a collection and runs ansible-lint using matrix-driven ansible-lint and ansible-core constraints.
.github/workflows/ansible-lint.yml
Run ansible-test via tox with a matrix of Ansible and Python versions rather than the ansible-test GitHub Action.
  • Added a strategy matrix over ansible-test target versions (including stable streams and milestone) and matching Python versions with fail-fast disabled in the ansible-test workflow.
  • Upgraded tox-lsr to version 3.18.0 in the ansible-test workflow.
  • Introduced an actions/setup-python step using the matrix Python version.
  • Replaced separate collection conversion and ansible-test GitHub Action usage with a tox invocation that both converts to a collection and runs versioned ansible-test environments defined per matrix entry.
.github/workflows/ansible-test.yml
Standardize on tox-lsr 3.18.0 across CI workflows.
  • Bumped tox-lsr from 3.17.1 to 3.18.0 in the ansible-managed-var-comment workflow.
  • Bumped tox-lsr from 3.17.1 to 3.18.0 in the python-unit-test workflow, keeping existing tox/virtualenv handling.
  • Bumped tox-lsr from 3.17.1 to 3.18.0 in the qemu-kvm-integration-tests workflow.
.github/workflows/ansible-managed-var-comment.yml
.github/workflows/python-unit-test.yml
.github/workflows/qemu-kvm-integration-tests.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@richm richm merged commit f606c48 into main Apr 8, 2026
13 checks passed
@richm richm deleted the ci-ansible-lint-ansible-test-matrix branch April 8, 2026 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant