Mastering GitLab 12: Implement DevOps culture and repository management solutions

Exploring GitLab editions – CE and EE

The origins of GitLab

The core system components of GitLab

Installing GitLab

Installing GitLab using omnibus packages

Running from source

Using it from Docker

Deploying GitLab using Kubernetes

Configuring GitLab Using the Web UI

Configuring GitLab settings at the instance level

Configuring GitLab settings at the group level

Configuring GitLab settings at the project level

Configuring GitLab from the Terminal

Configuring omnibus and GitLab installations from the terminal

Configuring source installations

Reconfiguring GitLab Docker containers

Changing GitLab in a Kubernetes environment

Section 2: Migrating Data from Different Locations

Importing Your Project from GitHub to GitLab

Using the GitHub integration feature

Using a GitHub token

Using a GitLab rake task

Migrating from CVS

Preparing to migrate from CVS to Git

CVS versus Git

Running the conversion

Cleaning up after migration

Switching from SVN

The difference between SVN and Git

Mirroring SVN and GIT

Using svn2git to migrate in one cut

Moving Repositories from TFS

Centralized or decentralized

TFS versus Git

Section 3: Implement the GitLab DevOps Workflow

GitLab Vision - the Whole Toolchain in One Application

Create Your Product, Verify, and Package it

DevOps phase – manage your ideas

The GitLab workflow

DevOps phase – plan your feature

DevOps phase – create it

DevOps phase – verify your product

DevOps phase – package it for use

The Release and Configure Phase

Continuous Deployment

Monitoring with Prometheus

The static analysis of security vulnerabilities

Setting up Prometheus

Customizing monitoring

Dynamic Application Security Testing

Integrating GitLab with CI/CD Tools

Connecting Jenkins to GitLab

Using Jira with GitLab

Integrating with Mattermost

Using webhooks for events

Section 4: Utilize GitLab CI and CI Runners

Setting Up Your Project for GitLab Continuous Integration

Pipelines

Jobs

Creating .gitlab-ci.yml

Installing and Configuring GitLab Runners

The Runner client architecture

Creating a basic Runner with the shell executor

Using GitLab Runners with Docker or Kubernetes

Runner client architecture

Creating your own Dockerized GitLab Runner

Using a prebuilt Docker container to deploy GitLab Runners

Using a Kubernetes cluster to spawn GitLab Runners

Autoscaling GitLab CI Runners

Runner client architecture

Setting up the environment

Configuring the Runner

Monitoring CI Metrics

Enabling monitoring for Runners

Editing the GitLab Runner configuration file

Runner business logic metrics

General process metrics

Section 5: Scale the Server Infrastructure (High Availability Setup)

Creating a Basic HA Architecture Using Horizontal Scaling

The underlying architecture of this solution

Setting up the bastion hosts

Configuring the database nodes

The Redis configuration

Connecting the shared filesystem

Setting up the application servers

Managing a Hybrid HA Environment

The basic architecture of this solution

A renewed Terraform configuration

Splitting application components into frontend and middleware tiers

Connecting the shared filesystem

Changes in Ansible files

Making Your Environment Fully Distributed

The basic architecture of this solution

Performing changes to the Terraform configuration

Splitting more application components

The clustered Redis/Sentinel configuration

Changes in Ansible files

Using Geo to Create Distributed Read-Only Copies of GitLab