Wiki for Gitlab.com (GLU) Onboarding & Troubleshooting
GitLab.com Onboarding Instructions & Troubleshooting
Onboarding Instructions
1) Initiate GLU Onboarding Request and IT Activities
- Team lead defines:
- Which Subgroup and Permissions will be needed. (“e.g. Subgroup = “ENR” and Permissions = “Developer/Maintainer/Reporter”) – these are the specs for Gitlab.com.
- Which team DLs to be added to (if not done so already). Eng.GitLab.Users will always be added.
- Team lead or User enter ESD Ticket - Request a Service -> Software -> GitLab Ultimate and CC User or Team Lead.
- IT configures AD and DUO according to the request*
- Wait 12 hours min or ask IT to “Fast Track”
2) User identifies which Use Case to follow
- User clicks https://gitlab.com/groups/e3803/-/saml/sso?token=sxVswZpZ
- If user gets an email from gitlab.com (check SPAM and Barracuda), the user is Use Case 1
- If user sees this login screen, follow Use Case 2
3) Use Case 1: User has NO existing GitLab account
Use these instructions if no GitLab account ever existed, OR an account was deleted from GitLab
-
Provided you've been invited to your group,click https://gitlab.com/groups/e3803/-/saml/sso?token=sxVswZpZ and click "Sign In" at the bottom.
ii. User will be redirected to DUO Authentication, once authenticated user will see the Edifecs group https://gitlab.com/e3803
-
Step 5 below should have been completed by the onboarding team. However, if this wasn’t done (you only see “Guest” permissions when you log in), ask your Team Lead to follow Step 5, or reply to the ESD ticket asking for assistance.
4) Use Case 2: User has existing GitLab account
Use this use case if the user has existing GitLab account, or was deleted from AD and then rejoined.
- Click https://gitlab.com/groups/e3803/-/saml/sso?token=sxVswZpZ
- User will be redirected to DUO authentication. Procede with authentication.
- User is redirected to "Username and Pwd" screen below.
b. you don't have or know your pwd, click "Forgot your password?" to reset.
c. Sign in using credentials. User will see this screen:
d. Click "Authorize"
e. Reauthenticate with Duo if necessary. You can now view the Edifecs GitLab instance at https://gitlab.com/e3803.
5) Joining your group with elevated permissions
- Ask your Team Lead (Edifecs GitLab Subgroup Owner/Maintainer) to change your Subgroup/Permissions by sending a Direct Invite.
- Owner/Maintainer navigates to Edifecs\<Subgroup> -> Manage -> "Invite Members"
- Select User Name, Role, click "Invite"
- User will be sent email confirming they are member of the group with a direct link.
- User clicks the direct link and authenticates with Duo to access the group.
NOTES
See Permissions and roles | GitLab to determine which Roles to assign your User.
3) Minimum Access and Guest Access levels
- Neither Minimal Access nor Guest permission levels consume a license. Guests CAN SEE the code and perform other operations noted in Permissions.
- Minimal Access will NOT be able to see https://gitlab.com/e3803 (they will receive error 404). Users can still be added with a Direct Invite by a Team Owner/Maintainer to any subgroup with elevated permissions.
4) Adding users to ROOT Edifecs instance*
Pooja will work with Team Lead and/or User to designate if they should have Edifecs ROOT access to one of these specific AD roles. If none is provided, Guest will be used.
- SERVICE-DUO-GitLab-Guests
- SERVICE-DUO-GitLab-Reporters
- SERVICE-DUO-GitLab-Developers
- SERVICE-DUO-GitLab-Maintainers
- SERVICE-DUO-GitLab-Owners
- SERVICE-DUO-GitLab-MinimalAccess
5) Changing an Edifecs ROOT user Permissions
As an Edifecs ROOT Owner or Maintainer, you will NOT be able to change permissions for any user within the UI and have the change persist. To definitively change the user's root permissions, open an IT ticket to change the AD Security Group according to above options.
6) Support Tickets
- In order to create Support requests with Gitlab, open an ESD ticket to have you added to the Gitlab Edifecs Organization. This ticket should CC Denis Kosenko and Pooja Chaudhry. We will add you by editing the contacts.yaml · master · Support / zd-global-orgs / Organization 4981772409372 · GitLab with your name and email.
- You will then create an account (this is not linked to our Edifecs instance, it is a separate ticketing system altogether) at GitLab Support Site.
- Log in to the site and create your tickets. You can see ALL Organization tickets as per screenshot below:
7) Edifecs GitLab Onboarding & Sprint Management Wiki: New User Onboarding and Sprint Management · Wiki · Edifecs · GitLab
- To educated onboarded GitLab users on Edifecs PDLC as implemented through the platform.
-
This is accessible ONLY to onboarded Gitlab users, through the “Plan -> Wiki” (left-hand navigation) of our core Edifecs instance.
8) Internal Edifecs Gitlab Ultimate (Gitlab.com) Teams Channel
- For GitLab users to ask for internal community-style support or guidance from other users of the platform
- As per the communication plan, these often become Support Tickets or Feature Requests if not internally resolved.
9) Gitlab Documentation Online: GitLab Documentation
- Reference for their customers shows what’s new and what version we are currently using in top right corner, also good primer info for new users
- Doesn’t require login (publicly accessible)