Handbook On-Call
Was this helpful?
Was this helpful?
You are here:
Handbook On-Call
GitLab recognizes that the Handbook is a critical part of empowering team members to do their jobs effectively. As such we have implemented a basic on-call process (refer to below) to ensure that someone is available to assist team members in the event that something is broken in the handbook or if they are having trouble with making updates to it.
Any issues should be reported in the channel in Slack.
If you do not get a response within the indicated feel free to DM the Editor team Engineering Manager or Product Manager (refer to ).
Issues should only be escalated to the Handbook On-Call team if it relates to:
Master being broken
Security incidents
Significant broken pages in production (e.g. the values page being unreachable)
Broken infrastructure
Bugs that prevents team members from accessing important information
Time sensitive updates to the Handbook where there are any issue in making the update
We are looking into formulating alternatives and the future.
When an issue is reported:
Acknowledge the team member and let them know you are looking into it
You can check on #production, #incident-management, and #is-this-known to see if it's a know issue with infrastructure or other problems.
Provide an update as soon as you are able to confirm their problem.
You can also post updates in #website and/or #handbook as appropriate.
Resolve the problem, or provide feedback to the team member on how they can resolve it.
Offer to have a Zoom call to help replicate or resolve the issue if it is not straight forward.
All broken CI pipelines for the master branch of the www-gitlab-com repo are automatically posted in the Slack channel. These reports should be investigated and addressed where needed.
Once a report has been looked at, please leave a comment stating the nature of the problem, action taken and add a ✅ reaction to the message to show that it has been handled.
Until recently members of the Static Site Editor team were part of the on-call process and members of the channel. Additionally any GitLab team member can volunteer to join the channel and help out.
Make sure you are set to receive notifications for the channel
The Handbook On-Call deals specifically with matters relating to the www-gitlab-com repo source code and configuration. If a reported issue relates to the GitLab product or the infrastructure running the website then it should be escalated to the Reliability Engineering team. To report an incident follow the instructions on the Incident Management page:
All incidents reported in the channel, during weekdays (Mon - Fri, 08:00 UTC+0 - 18:00 UTC-7), should receive an initial response of acknowledgement within 1 hour of it being reported.
There is also a .
If for some reason there is a large amount of failures resulting in spamming the channel, the error reporting can be turned off in the repo settings:
See for details on the current workarounds required for
To see the status of the merge train (useful when team members are reporting that their MRs seem 'stuck' on the train), see .
TL;DR for workaround: If the first/oldest MR iid in (sort=asc by ID) is actively running a pipeline and eventually gets merged, then things are moving along, just slowly. If the first one in the list isn't currently running any pipeline, remove it from the train and re-add it (it should go to the end).