CI/CD template maintainers
Issue
This issue is to discuss GitLab CI/CD template reviewers and maintainers. There are a few topics, all around determining DRIs and more maintainers, as well as what reviewers/maintainers should be responsible for. In general, CI/CD template maintainers are responsible for ensuring that all templates meet the CI/CD template development guide requirements: https://docs.gitlab.com/ee/development/cicd/templates.html
-
There are not many CI/CD template maintainers right now: https://docs.gitlab.com/ee/development/code_review.html#reviewer-roulette.
If a handful are on leave or busy, that means all pings will go to the few remaining maintainers. For example,
@hfyngvason
is currently on parental leave until late September, leaving only 3 maintainers. At this moment, Shinya is set to💡 , removing him from roulette while he focuses on deliverables, and Laura is set to3️⃣ . That means only Laura and Marcel get pings, and if she hits 3 assigned MRs, then💯 of roulette pings go to Marcel. -
Should backend specs always be reviewed by the template reviewer/maintainer? Up to this point, I only focused on template content, but it was raised in gitlab-org/gitlab!91705 (comment 1019264313) that this might inspire people to avoid testing the templates. We should probably make it clear that testing is recommended, and that template maintainers should review all template-related specs.
-
Should one team be responsible for CI/CD template maintenance? The grouppipeline authoring team is responsible for the backend CI/CD template code, so should they also be the CI/CD template maintainers?