community.rabbitmq
community.rabbitmq copied to clipboard
ansible-collections
Volunteer help wanted
Unfortunately I'm not able to commit as much time as I'd like to the maintenance and continuous improvement of this repository. I would appreciate it if some others could step up to take on any or all of these roles:
- Development of improvements - looking at the code base and improving its readability, maintainability and testability.
- Development of bug fixes - fixing reported bugs and implementing tests to ensure they do not happen with any future changes.
- Triaging of bug reports - validating the bug and providing a test playbook to reproduce it.
Please feel free to reply to this issue to volunteer.
Hey! I can help a bit, but I'm unfamiliar with Ansible's testing framework and code policies, so I may need a bit of help to get started. I managed to run ansible-test for unit tests, but the integration tests don't pass at the moment, do they? Or is it my local setup?
I think we're among interested parties to help out. Will try to help out with 2 point in the upcoming week or 2.
Hey @abompard - there aren't really any special policies, only those outlined in https://github.com/ansible-collections/community.rabbitmq#contributing-to-this-collection
Integration tests were passing the last time I checked, but it has been a while. The instructions are in the README.
@noonedeadpunk That would be great, thank you.
Hey @odyssey4me ! I couldn't run the integration tests, some repos have disappeared apparently. I've opened #75 to try to get them working again but I'm stuck with systemctl failing in the ubuntu container that ansible-test creates. Could you try running the integration tests on your side, maybe it's something wrong with my setup. Thanks!
I just tried to setup azure pipelines in my fork to see about helping with getting the test setup fixed... I gave up - the pipeline is using a private pool and I had to go ask for a grant to run stuff in parallel even though it said parallel runs were included in the free plan. Ugh. Never mind. The tests in this repo are not really fork-able.
@abompard I'd like to try helping diagnose things, which I guess has to be done through PRs. The azure pipeline logs have all expired in #75, so I can't look through to see what's broken. Could you push another commit or somehow retrigger the azure pipeline?
I just tried to setup azure pipelines in my fork to see about helping with getting the test setup fixed... I gave up - the pipeline is using a private pool and I had to go ask for a grant to run stuff in parallel even though it said parallel runs were included in the free plan. Ugh. Never mind. The tests in this repo are not really fork-able.
@cognifloyd The tests will run in AZP when you create a PR against this repo. No need to worry about them running in your fork. If you have any issues please shout out.
