ChatOps on GitLab.com

ChatOps on GitLab.com allows GitLab team members to run various automation tasks on GitLab.com using Slack.

Requesting access

GitLab team-members may need access to ChatOps on GitLab.com for administration tasks such as:

  • Configuring feature flags.
  • Running EXPLAIN queries against the GitLab.com production replica.
  • Get deployment status of all of our environments or for a specific commit: /chatops run auto_deploy status [commit_sha]

To request access to ChatOps on GitLab.com:

  1. Sign in to Internal GitLab for Operations with one of the following methods:

    • The same username you use on GitLab.com. You may have to choose a different username later.
    • Clicking the Sign in with Google button to sign in with your GitLab.com email address.
    • Clicking the Sign in with Okta button to sign in with Okta.
  2. Confirm that your username in Internal GitLab for Operations is the same as your username in GitLab.com. If the usernames don't match, update the username in User Settings/Account for the Ops instance.

  3. Comment in your onboarding issue, and tag your onboarding buddy and your manager. Request they add you to the ops ChatOps project by running this command in the #chat-ops-test Slack channel, replacing <username> with your username: /chatops run member add <username> gitlab-com/chatops --ops

    Hi <__BUDDY_HANDLE__> and <__MANAGER_HANDLE__>, could you please add me to
    the ChatOps project in Ops by running this command:
    `/chatops run member add <username> gitlab-com/chatops --ops` in the
    `#chat-ops-test` Slack channel? Thanks in advance.
  4. Ensure you've set up two-factor authentication.

  5. After you're added to the ChatOps project, run this command to check your user status and ensure you can execute commands in the #chat-ops-test Slack channel:

    /chatops run user find <username>

    The bot guides you through the process of allowing your user to execute commands in the #chat-ops-test Slack channel.

  6. If you had to change your username for GitLab.com on the first step, make sure to reflect this information on the team page.

See also