Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Molecule 6 #1303

Merged
merged 17 commits into from
Jun 30, 2024
Merged

Molecule 6 #1303

merged 17 commits into from
Jun 30, 2024

Conversation

eb4x
Copy link
Collaborator

@eb4x eb4x commented Jun 22, 2024

SUMMARY

Upgrading the molecule testing to version 6.

Future molecule wants to eliminate the various drivers, and just have ansible (delegated driver) set up the infrastructure. This PR does that. Creates all networks/containers in create.yml and destroys them in destroy.yml.

ISSUE TYPE
  • Feature Pull Request
COMPONENT NAME

molecule, ci

ADDITIONAL INFORMATION

A small smattering of other improvements, and just removing stuff that does not need to be there.

eb4x added 16 commits June 21, 2024 19:13
We want all the logs and help we can get during testing/CI.
Molecule automagically sets these.
Use loop unless we need additional complexity
cgroupns
introduced in community.docker 3.0.0
Also, there is no scenario in our CI where we do not want logs.
this does nothing
It's a dependency within our collection and gets installed with it.
The database type is irrelevant.
We can reuse the create/destroy for all roles, as we always need
a OS container, and the database container is only needed/created
when the test-instance is in a known database group.
It's the same for all roles, it reflects our dependency on
community.docker during provisioning.
@eb4x
Copy link
Collaborator Author

eb4x commented Jun 22, 2024

I think the failing tests are flukes, maybe just re-run the failed ones to verify.

@pyrodie18
Copy link
Collaborator

I think the failing tests are flukes, maybe just re-run the failed ones to verify.

Ya pretty sure they are....rerunning now

@pyrodie18
Copy link
Collaborator

Is there a reason not to just move straight to the current version of 24.6.0? ansible/molecule#4136

@eb4x
Copy link
Collaborator Author

eb4x commented Jun 22, 2024

Is there a reason not to just move straight to the current version of 24.6.0? ansible/molecule#4136

Not really sure, I wasn't aware of the newer releases. It has Python 3.10 as minimum requirement, but I see we bumped testing to 3.11. I'll add a commit to bump to the latest.

Let's try even newer versions of molecule.
@eb4x
Copy link
Collaborator Author

eb4x commented Jun 25, 2024

Maybe just re-run the failed tests again.

@pyrodie18 pyrodie18 merged commit 28c4921 into ansible-collections:main Jun 30, 2024
341 of 342 checks passed
emrocha pushed a commit to emrocha/community.zabbix that referenced this pull request Jul 1, 2024
@pyrodie18 pyrodie18 mentioned this pull request Jul 6, 2024
eb4x added a commit to eb4x/community.zabbix that referenced this pull request Jul 7, 2024
eb4x added a commit to eb4x/community.zabbix that referenced this pull request Jul 7, 2024
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.

2 participants