-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathPITCHME.md.part-one
139 lines (84 loc) · 3.49 KB
/
PITCHME.md.part-one
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
# GitLab CI/CD Tutorial
Aleksey Tsalolikhin
28 October 2017
---
## Table of contents
- Introduction
- Setting up your CI/CD infrastructure
- Configuring CI/CD pipelines
- Would you like to know more?
---
## Introduction
### GitLab
[GitLab](https://about.gitlab.com) is a Web application for working together on code. In addition to a Git data store, it has everything you need for a modern workflow: ticketing system, issue boards, code review, CI/CD, chat and more -- all smoothly integrated in one UI.
GitLab.com is the public service; the software is also available for private (on-prem) use in the Community Edition (open source, free of charge) and the Enterprise Edition (commercial -- ask me for a discount code).
---
## Introduction
### GitLab CI/CD (Runner Server)
GitLab comes with an add-on package called Runner Server which provides runners. Simply put, a runner is what runs the tests. Runners can run build jobs, test jobs, and deploy jobs. Or actually any kind of job! Runner Server works with GitLab through GitLab Server's API.
---?include=01_05-architecture.md
---
## Introduction
### Lab exercise
In this tutorial, you will set up:
- GitLab Server
- Runner Server
- UAT environment
- Production environment
Using these building blocks, you will set up a **CI/CD pipeline**:
You will then re-use the UAT and Production environments in the Jenkins tutorial.
---
## Introduction
### Lab exercise
The pipeline could be fully automated:
---?include=01_10-installing-gitlab-server.md
---?include=01_12-setting-up-a-project.md
---?include=01_13-enabling-ci-on-a-project.md
---?include=01_15-installing-docker.md
---?include=01_20-installing-gitlab-ci.md
---
<!-- setting up runners -->
---?include=01_22-registering-our-first-runner.md
---?include=01_25-register-and-enable-Docker-runner.md
---?include=01_26-test-docker-runner.md
---?include=01_27-change-docker-image.md
<!-- setting up UAT and Prod environments -->
---?include=01_91-set-up-prod-and-stg-web-sites.md
---?include=01_92-deploy-using-ssh.md
---?include=01_93-deploy-via-git.md
---
## Configuring CI/CD pipelines
### Introduction
Now our infrastructure is set up. We have:
- GitLab Server (for our GitLab Web application)
- Runner Server (to provider runners, to run CI builds and tests, and CD jobs)
- a mock Stage environment (for User Acceptance Testing)
- a mock Prod environment
This next section will deal with configuring CI/CD pipelines.
It's purpose is to get you more familiar with GitLab's CI syntax and capabilities.
First, let's go over some key definitions.
---?include=02_00-key-definitions.md
<!-- Continuous Integration -->
---?include=02_01-single-test-job.md
---?include=02_02-simple-3-stage-shell-pipeline.md
---?include=02_03-simple-3-stage-docker-pipeline.md
---?include=02_05-parallel-jobs.md
---?include=02_30-custom-stages.md
---?include=02_40-testing-with-phpunit.md
- Continuous Delivery
---?include=02_42-deploying-to-stage-via-ssh.md
---?include=02_44-set-up-git-pulls-from-mock-envs.md
---?include=02_45-deploying-to-stage-via-git.md
---?include=02_50-manual-deploy-to-production.md
---?include=02_55-continuous-deployment.md
- Troubleshooting
---?include=02_90-debugging-builds.md
---?include=02_100-increasing-loglevel.md
---?include=02_110-gitlab-logs.md
---?include=02_115-interactive-containers.md
---?include=02_118-env-vars.md
---?include=02_120-debugging.md
---?include=bookmarks.md