Gitlab hero border pattern left svg Gitlab hero border pattern right svg

System Requirements for GitLab Professional Services Training Sessions

Pre-Training System Requirements for Attendees

In advance of attending training sessions delivered by GitLab Professional Services, there are a few tasks that need to be done on your side to ensure a smooth learning experience. Most of the training modules will include a presentation and demo which you can follow along with on your system, as well as one or more hands-on labs. To ensure you can practice what you are learning, you need to use your own laptop/system and come prepared with the course specific requirements. Please review the following requirements ahead of your scheduled training session.

Attendee Laptops

Here are some things you should take care of ahead of the session to make sure your laptop system is ready.

  • System: Each attendee must bring their own laptop running macOS, Linux, or Windows. Please review the system requirements here to confirm your laptop meets them.
  • Internet Access: Your laptop should have internet access and at least http, https.

GitLab Demo Cloud Access

Our trainers will set up a unique invitation code for course attendees to access the GitLab Demo Cloud, which you will use as a sandbox during the training sessions. You will be able to create credentials to access the Demo Cloud using the invitation code provided on the day of the training. This will enable you to access GitLab's paid features and capabilities during the training session that are not available with the free version of GitLab. Please make sure you can land on both the invitation site and the GitLab Demo Cloud URLs and resolve any firewall issues ahead of the training.

Course-Specific Requirements

GitLab with Git Basics

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Verify Git installation: Your laptop likely already has Git installed. To verify, follow these instructions.
    • macOS: Type git in the Terminal application. If it’s not installed, it will prompt you to install it.
    • Linux: sudo yum install git-all or sudo apt-get install git-all
    • Windows 10: Windows Subsystem for Linux
    • Other versions of Windows: See Git for Windows
  • Generate SSH keys: Follow the instructions here
  • Browser: No Internet Explorer

GitLab CI/CD Training

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer

GitLab for System Administrators

  • Managed Lab: If GitLab is providing virtual machines (VMs) for your training delivery (an option your organization can choose to add on), you don't need to do anything else. If VMs are not being used for your training, you can buiild your own VMs on your own systems to set up a GitLab sandbox instance for the class. Every student will need 2 VMs for the Class. One VM will be used for installing a GitLab instance and a second for installing and connecting to the Runner. Each host should have a DNS fully qualified domain name. The GitLab VMs and Runner VMs should be able to access each other through ports 80 and 443. Each student should be able to access the Fully Qualified Domain Name in a browser from their workstation. The Operating System should be RedHat, CentOS or Ubuntu. Minimum requirements would be 4x CPU and 4GB RAM. It is suggested to use 8x CPU and 16GB RAM for the GitLab Instances per student. Students shoould be able to have ssh access to each VM and have sudo rights to root access.
  • Docker: If GitLab is providing virtual machines (VMs) for your training delivery (an option your organization can choose to add on), you don't need to install Docker. If VMs are not being used for your training, you can install Docker on your own systems to set up a GitLab sandbox instance. It's important to install Docker prior to the start of the training session so that you can fully participate in the hands-on activities during the session. If you are not able to install Docker on your system, you will still be able to view the trainer's demonstration of the steps during the session. Install Docker on your laptop from here access: Workstations should have ssh access to the Lab VMs. For *Nix workstations (Mac and Linux), this is usually defaulted into the terminal. For Windows workstations we recomend git bash. %a{href: "https://gitforwindows.org/", target: "_blank"} Git for Windows here Windows 10 or above can be used, but is not the preferred method. If your OS does not have a pre-installed SSH client, you will need to install it prior to class.
  • Browser: No Internet Explorer

Project Management with GitLab

  • GitLab Access: Access to GitLab such as through the GitLab Demo Cloud environment is required for each attendee to participate in the hands-on activities.
  • Browser: No Internet Explorer

GitLab InnerSourcing Training

Licenses: The following features covered in this session are only available for Silver/Gold & Premier/Ultimate GitLab Licenses:
  • Multi-Level Epics
  • Roadmaps
  • Incremental Rollout
  • Package Registry
  • Container Registry
  • Dependency Proxy
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license