GitLab - ansible/community GitHub Wiki
THIS PAGE IS OLD and no longer maintained. For questions, please use the Ansible forum.
GitLab Working Group
The GitLab Working Group collaborates on GitLab-related functionality in Ansible.
News
- Created the Module development guidelines Wiki
- We formed a Working Group to improve the GitLab-specific support in Ansible.
- We have a GitLab pinboard, subscribe to it to stay informed!
- There is no automated testing infrastructure for GitLab, individual testing by contributors/users is critical. This is why we need integration tests for every GitLab module.
Community
| Name | GitHub (+ IRC) | Role | Affiliation |
|---|---|---|---|
| Guillaume Martinez | Lunik | Lead | Independent |
| Andrea Tartaglia | Shaps / shaps | Lead | Independent |
| Marcus Watkins | marwatk | Reviewer | Independent |
| Waheed Barghouti | waheedi | Reviewer | Independent |
| Werner Dijkerman | dj-wasabi | Reviewer | Independent |
Add yourself to this list as a Reviewer (help review PRs) or as a Member (discuss issues/roadmap).
Process
- We have GitLab module guidelines
Ideas
- Move all GitLab modules in its own gitlab/ sub-directory
- Add See Also sections to GitLab modules referring related modules and websites
- Properly capitalize GitLab (we are using Gitlab everywhere, while upstream is using GitLab)
- Add specific GitLab documentation to documentation website
- Determine which upstream library (if any) to use for all modules
Action plan
v2.8 release
- New GitLab modules to review:
- GitLab runners dynamic inventory #42664
- Add missing integration tests to existing modules #51490:
- gitlab_deploy_key
- gitlab_group
- gitlab_hooks
- gitlab_project
- gitlab_runner
- gitlab_user
- Review open pull-requests -- open PRs
- Review open issues -- open issues
future
- TBD