Book Image

Mastering GitLab 12

By : Joost Evertse
Book Image

Mastering GitLab 12

By: Joost Evertse

Overview of this book

GitLab is an open source repository management and version control toolkit with functions for enterprises and personal software projects. It offers configurability options, extensions, and APIs that make it an ideal tool for enterprises to manage the software development life cycle. This book begins by explaining GitLab options and the components of the GitLab architecture. You will learn how to install and set up GitLab on-premises and in the cloud, along with understanding how to migrate code bases from different systems, such as GitHub, Concurrent Versions System, Team Foundation Version Control, and Subversion. Later chapters will help you implement DevOps culture by introducing the workflow management tools in GitLab and continuous integration/continuous deployment (CI/CD). In addition to this, the book will guide you through installing GitLab on a range of cloud platforms, monitoring with Prometheus, and deploying an environment with GitLab. You'll also focus on the GitLab CI component to assist you with creating development pipelines and jobs, along with helping you set up GitLab runners for your own project. Finally, you will be able to choose a high availability setup that fits your needs and helps you monitor and act on results obtained after testing. By the end of this book, you will have gained the expertise you need to use GitLab features effectively, and be able to integrate all phases in the development process.

Related Content you might be interested in

Current Title:

Small book image
Mastering GitLab 12
Joost Evertse
Aug, 2019 | 608 pages
Small book image
GitLab Quick Start Guide
Adam OGrady
Nov, 2018 | 180 pages
Small book image
Automating DevOps with GitLab CI/CD Pipelines
Chris Timberlake | Christopher Cowell | Nicholas Lotz
Feb, 2023 | 348 pages
Small book image
Getting Started with Terraform
Kirill Shirinkin
Jul, 2017 | 208 pages
Table of Contents (30 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Get in touch
Free Chapter
1
Section 1: Install and Set Up GitLab On-Premises or in the Cloud
Section 1: Install and Set Up GitLab On-Premises or in the Cloud
2
Introducing the GitLab Architecture
Introducing the GitLab Architecture
Technical requirements
The origins of GitLab
Exploring GitLab editions – CE and EE
The core system components of GitLab
GitLab CI
GitLab Runners
Cloud native
Summary
Questions
Further reading
3
Installing GitLab
Installing GitLab
Technical requirements
Installing GitLab using omnibus packages
Running from source
Using it from Docker
Deploying GitLab using Kubernetes
Summary
Questions
Further reading
4
Configuring GitLab Using the Web UI
Configuring GitLab Using the Web UI
Technical requirements
Configuring GitLab settings at the instance level
Configuring GitLab settings at the group level
Configuring GitLab settings at the project level
Summary
Questions
Further reading
5
Configuring GitLab from the Terminal
Configuring GitLab from the Terminal
Technical requirements
Configuring omnibus and GitLab installations from the terminal
Configuring source installations
Reconfiguring GitLab Docker containers
Changing GitLab in a Kubernetes environment
Summary
Questions
Further reading
6
Section 2: Migrating Data from Different Locations
Section 2: Migrating Data from Different Locations
7
Importing Your Project from GitHub to GitLab
Importing Your Project from GitHub to GitLab
Technical requirements
Using the GitHub integration feature
Using a GitHub token
Using a GitLab rake task
Summary
Questions
Further reading
8
Migrating from CVS
Migrating from CVS
Technical requirements
CVS versus Git
Preparing to migrate from CVS to Git
Running the conversion
Cleaning up after migration
Summary
Questions
Further reading
9
Switching from SVN
Switching from SVN
Technical requirements
The difference between SVN and Git
Mirroring SVN and GIT
Using svn2git to migrate in one cut
Summary
Questions
Further reading
10
Moving Repositories from TFS
Moving Repositories from TFS
Technical requirements
TFS versus Git
Centralized or decentralized
The git-tfs tool
Summary
Questions
Further reading
11
Section 3: Implement the GitLab DevOps Workflow
Section 3: Implement the GitLab DevOps Workflow
12
GitLab Vision - the Whole Toolchain in One Application
GitLab Vision - the Whole Toolchain in One Application
Technical requirements
The Agile Manifesto
XP
The DevOps movement
The toolchain
Summary
Questions
Further reading
13
Create Your Product, Verify, and Package it
Create Your Product, Verify, and Package it
Technical requirements
The GitLab workflow
DevOps phase – manage your ideas
DevOps phase – plan your feature
DevOps phase – create it
DevOps phase – verify your product
DevOps phase – package it for use
Summary
Questions
Further reading
14
The Release and Configure Phase
The Release and Configure Phase
Technical requirements
Continuous Deployment
Auto DevOps
Summary
Questions
Further reading
15
Monitoring with Prometheus
Monitoring with Prometheus
Technical requirements
Setting up Prometheus
Customizing monitoring
The static analysis of security vulnerabilities
Dynamic Application Security Testing
Dependency checking
Summary
Questions
Further reading
16
Integrating GitLab with CI/CD Tools
Integrating GitLab with CI/CD Tools
Technical requirements
Using Jira with GitLab
Connecting Jenkins to GitLab
Integrating with Mattermost
Using webhooks for events
Summary
Questions
Further reading
17
Section 4: Utilize GitLab CI and CI Runners
Section 4: Utilize GitLab CI and CI Runners
18
Setting Up Your Project for GitLab Continuous Integration
Setting Up Your Project for GitLab Continuous Integration
Technical requirements
Pipelines
Jobs
Creating .gitlab-ci.yml
Configuring a runner
Summary
Questions
Further reading
19
Installing and Configuring GitLab Runners
Installing and Configuring GitLab Runners
Technical requirements
The Runner client architecture
Creating a basic Runner with the shell executor
Summary
Questions
Further reading
20
Using GitLab Runners with Docker or Kubernetes
Using GitLab Runners with Docker or Kubernetes
Technical requirements
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
Summary
Questions
Further reading
21
Autoscaling GitLab CI Runners
Autoscaling GitLab CI Runners
Technical requirements
Runner client architecture
Setting up the environment
Configuring the Runner
Summary
Questions
Further reading
22
Monitoring CI Metrics
Monitoring CI Metrics
Technical requirements
Enabling monitoring for Runners
Editing the GitLab Runner configuration file
Runner business logic metrics
General process metrics
Summary
Questions
Further reading
23
Section 5: Scale the Server Infrastructure (High Availability Setup)
Section 5: Scale the Server Infrastructure (High Availability Setup)
24
Creating a Basic HA Architecture Using Horizontal Scaling
Creating a Basic HA Architecture Using Horizontal Scaling
Technical requirements
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
Summary
Questions
Further reading
25
Managing a Hybrid HA Environment
Managing a Hybrid HA Environment
Technical requirements
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
Script enhancements
Summary
Questions
Further reading
26
Making Your Environment Fully Distributed
Making Your Environment Fully Distributed
Technical requirements
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
Script enhancements
Summary
Questions
Further reading
27
Using Geo to Create Distributed Read-Only Copies of GitLab
Using Geo to Create Distributed Read-Only Copies of GitLab
Technical requirements
The basic architecture of this solution
Preparing the infrastructure
Setting up Geo
Summary
Questions
Further reading
28
Assessments
Assessments
Chapter 1: Introducing the GitLab Architecture
Chapter 2: Installing GitLab
Chapter 3: Configuring GitLab Using the Web UI
Chapter 4: Configuring GitLab from the Terminal
Chapter 5: Importing Your Project from GitHub to GitLab
Chapter 6: Migrating From CVS
Chapter 7: Switching from SVN
Chapter 8: Moving Repositories from TFS
Chapter 9: GitLab Vision: The Whole Toolchain in One Application
Chapter 10: Create Your Product, Verify, and Package it
Chapter 11: The Release and Configure Phase
Chapter 12: Monitoring with Prometheus
Chapter 13: Integrating GitLab with CI/CD Tools
Chapter 14: Setting Up Your Project for GitLab Continuous Integration
Chapter 15: Installing and Configuring GitLab Runners
Chapter 16: Using GitLab Runners with Docker or Kubernetes
Chapter 17: Autoscaling GitLab CI Runners
Chapter 18: Monitoring CI Metrics
Chapter 19: Creating a Basic HA Architecture by Using Horizontal Scaling
Chapter 20: Managing a Hybrid HA Environment
Chapter 21: Making Your Environment Fully Distributed
Chapter 22: Using Geo to Create Distributed Read-Only Copies of GitLab
29
Other Books You May Enjoy
Other Books You May Enjoy
Leave a review - let other readers know what you think

Editing the GitLab Runner configuration file

First, we have to configure the Runner to expose information, which is quite easy to do. The config.toml file, which resides at ~/.gitlab.runner on my system (macOS), has to be edited. We can enable the built-in server to serve information by adding a line with listen_address to this file, as shown in the following code block:

listen_address = ":9252"

After saving this file, we must restart our Runner with the following command (on macOS and a Homebrew installed Runner):

$ brew services  restart  gitlab-runner

On Linux or on a bare macOS installation, we can restart the Runner via the following command:

$ sudo killall -SIGHUP gitlab-runner

We can view the exposed information by opening the URL where it is running (in my case, http://192.168.178.82:9252), and then appending the metrics path (/metrics):

Now that we have exposed...

Previous Section
End of Section 4
Next Section