GitLab/Stewardship
< GitLab
This page is currently a draft.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
🚧 Here be Dragons If this table is missing areas of accountability, please add them. If you're unsure about ownership, put❓
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
🚧 Here be Dragons If this table is missing areas of accountability, please add them. If you're unsure about ownership, put❓
This table documents accountabilities for the various pieces of GitLab infrastructure.
| What | Accountable Team | Consulted Teams/Groups | Informed Teams/Groups |
|---|---|---|---|
| Security Upgrades | SRE Collaboration Services | NA | Release Engineering |
| Major Release Upgrades | SRE Collaboration Services | Release Engineering | wikitech-l@, ops-l@, #engineering-all
|
| Shared WMCS GitLab Runners | SRE Collaboration Services | Release Engineering | wikitech-l@, ops-l@, #engineering-all
|
| Shared third-party cloud GitLab Runners | Release Engineering | wikitech-l@, ops-l@, #engineering-all
| |
| Trusted GitLab Runners/sotware packaging | SRE Collaboration Services | Release Engineering | wikitech-l@, ops-l@, #engineering-all
|
| Monitoring GitLab availability | SRE Collaboration Services | ❓ | wikitech-l@, ops-l@, #engineering-all
|
| Responding to outages | SRE Collaboration Services | Release Engineering | wikitech-l@, ops-l@, #engineering-all
|
| Application-level technical support | Release Engineering | NA | NA |