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.
Table of Contents (30 chapters)
Free Chapter
1
Section 1: Install and Set Up GitLab On-Premises or in the Cloud
6
Section 2: Migrating Data from Different Locations
11
Section 3: Implement the GitLab DevOps Workflow
17
Section 4: Utilize GitLab CI and CI Runners
23
Section 5: Scale the Server Infrastructure (High Availability Setup)

Configuring source installations

The main configuration file to change is gitlab.yml, which is usually found in /home/git/gitlab/config. It follows the .yml standard and this has several implications. The first one is that indentation is very important. If you just copy and paste configuration, you will find that it can mess up the file contents. Another important feature that is used in the gitlab.yml file is utilizing anchors and aliases (&base) to specify different configuration targets. In practice, this means that the main configuration for all environments is specified in the config file (production: &base).

Below the production: &base target , the other environments are specified, and they refer to &base but override certain key-value pairs. How does GitLab know which environment information should be used? That is determined by the RAILS_ENV variable used...