-
Notifications
You must be signed in to change notification settings - Fork 144
HP-UX community pinboard #429
Comments
If you want to actively lead or are interested to be part of this Working Group, add your name to the Wiki page ! If we have a large enough group, we can start our own HP-UX Working Group. I started labeling all the HP-UX related issues and PRs so we can more easily track them:
PS If you no longer want to receive any messages from this pinboard, I apologize. Feel free to unsubscribe from this issue ticket. |
I refactored the swdepot module and added integration tests, you can find this at: ansible/ansible#51106 You need to clone my fork, checkout my branch, then run ansible-test:
You may have to modify the integration test at test/integration/targets/swdepot/tasks/main.yml to point the tests to your depot/repository. By default the tests uninstall and reinstall the 'unzip' package. |
Yeah, this is something that's on my list. Last year there was a re-org at work and, to cut a long story short, automation took a back seat while the new team bedded in. I've got access to HP-UX 11.11, 11.23, 11.31, 11.33, 11iv1, 11iv2, 11iv3 in house so I should be able to contribute some time to this. |
@davx8342 Welcome to the team ;-) I would really appreciate if you could test the swdepot refactored code and even test/fix the included integration test. |
We could collectively benefit from forming a Working Group related to HP-UX integration. We have quite some contributors on Github and users on IRC that are interested in improving this integration.
So this issue is a wake-up call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:
Since we don't have any HP-UX infrastructure for automated testing, collaborating on modules like this is important for the quality of the modules.
The text was updated successfully, but these errors were encountered: