New collection: hpe.ilo

[rajeevkallur]

Ansible Galaxy: https://galaxy.ansible.com/hpe/ilo
GitHub: https://github.com/HewlettPackard/ilo-ansible-collection
Issues Tracker: https://github.com/HewlettPackard/ilo-ansible-collection/issues
GitHub Handles: @rajeevkallur
Is the collection part of Automation Hub: Soon
We meet Collection Requirements: Yes

[Andersson007]

@rajeevkallur (sorry, deleted the first comment accidentally) hello, thanks for the inclusion request!
The collection will be reviewed as soon as there are volunteers in the community and steering committee.
The request will be published in Bullhorn every week (except the next one, will be on PTO).
Reviewing other's requests can speed up the process.
Thanks

[mariolenz]

@rajeevkallur I don't want to start an official review at the moment (no time!) but as far as I can see, you don't tag your releases and I don't see any CI Testing.

[Andersson007]

@rajeevkallur please go through https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst carefully.
after you fix stuff, you can check it yourself first using this review checklist. thanks

[rajeevkallur]

@mariolenz, Is CI Testing must?

[mariolenz]

@rajeevkallur At least for sanity tests I think it is.

Where's the problem? CI Testing says: You can copy the free-to-use GitHub action workflow file from the Collection Template repository to the .github/workflows directory in your collection to set up testing through GitHub actions. So it's really easy to implement.

Anyway, how do you make sure that changes to your collection are OK, or that your collection still works with a new ansible-core release without a CI?

Of course, you can run this daily (or at least once per week) manually, but since this would be a pain in the ass I suggest using some kind of CI pipeline. You don't even have to use GitHub Actions, but it would be great to have access to your pipeline so we see those tests are really running and, above all, succeeding.

[Andersson007]

i think reading Collection Requirements rather than just copy-pasting them to the description is all what we need here. There's a corresponding section. Thanks @mariolenz for the answer