GitLab Training

This training is provided by a developer who uses Git, GitLab and GitHub on a daily basis. Best practices originate from years of experience and students get the chance to discuss, question and improve their skills. 

The training participants gain an in-depth insight into the Git basics, configuration and shell and GUI clients. The different states from modified to staging to good commits are practiced too. The students also learn about GitLab basics with repository and user management and continue to practice Git version control with real-life exercises. How to examine the git history, compare specific commits or branches, get an idea about HEAD and smart pointers are given time too. 

With tips from daily development tasks, this training adds more best practices where applicable: cherry-pick, rebase, squash or even stash changes away for a moment. Students will learn their different use cases and discuss the pros and cons of merging and rebasing and why amending a commit causes problems with fast-foward history. 

Moving along from standalone environments, participants collaborate with others and get an overview on different Git workflows. This includes standalone repositories, feature branches, Gitflow, GitHub workflows with Pull Requests and GitLab workflows with Merge Requests. Exercises include to learn how Git commits and Merge Requests can automatically resolve or update issues in GitLab. 

Continuing with practices, the training goes deep into continuous integration, deployment and delivery (CI/CD) with GitLab in DevOps environments. This includes test and production pipelines. The training uses the GitLab runners with Docker containers to test and generate content from the training repository. Part of the training includes that users actively add notes to their own documentation and generate HTML docs with GitLab CI in the end. 

On top of that, the training provides more hints on GitLab usage, tools for working with Git and anything proven useful for daily best practice. There's also room to discuss possible migrations from SVN to Git/GitLab with hints from years of experience by the trainer. 

Training location/ duration:

2-day training | Nuremberg | from 9.00 to 5.00 pm

Next trainings

January 2019
22.01.2019 - 23.01.2019
June 2019
25.06.2019 - 26.06.2019
July 2019
23.07.2019 - 24.07.2019
December 2019
17.12.2019 - 18.12.2019

Content:

  • Introduction to Git and its history
  • Git basics, client installation, shell integration, GUI clients
  • Understand the three states: modified, staging and committed
  • Connect a local repository to a remote repository, specifically GitLab
  • Introduction into GitLab: Users, roles, projects
  • Learn about GitLab issue management, boards, integration with commits
  • How GitLab is managed, administration tips, customizing (theming, logos)
  • Continuous Integration/Deployment/Delivery (CI/CD) with GitLab
  • More ways to integrate Git with GitLab, apps, clients, development IDEs
  • Advanced topics: Webhooks, Pipelines and own container registries for CI/CD
  • GitLab API, monitoring checks
  • Migration from SVN or existing Git servers

Price:

The training fee is 1.550,- € excl. VAT

It includes the following:

  • 2 days training attendance in small groups
  • Coffee breaks incl. snacks twice a day
  • Lunch (incl. 1 beverage)
  • Dinner (incl. 2 beverages)
  • Free notebook during the training session
  • Training material
  • Free WiFi-access

Accomodation:
We are happy to assist you booking a hotel room. Please do not hesitate to contact us. 

Target group:

Developer and administrators are all welcome to the training. But basic development knowledge is required.

Conception:

To ensure an aim-oriented and efficient realization of this training the number of participants is limited. This enables an intense examination of the course content and the opportunity to settle individual questions and problems.

The exchange between the participants is of particular importance for us. This is also the reason why all participants are invited to dinner so that a lot of scope for discussions and exchange of experience is allowed between the participants outside the workshop hours.