This repository has been archived by the owner on Jun 10, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
/
index.html
251 lines (242 loc) · 7.53 KB
/
index.html
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
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<title>CI/CD</title>
<link rel="stylesheet" href="css/reset.css">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="css/theme/black.css">
<!-- Theme used for syntax highlighting of code -->
<link rel="stylesheet" href="lib/css/monokai.css">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
</head>
<body>
<div class="reveal">
<div class="slides">
<section>
<h1>CI/CD</h1>
<img src="assets/CI:CD%20big.png">
</section>
<section data-markdown>
<textarea data-template>
## CI/CD stands for...
- Continuous Integration
- Continuous Delivery
- <span data-fragment-index="1" class="fragment fade-left">Continuous Deployment</span>
</textarea>
</section>
<section>
<section>
<h2>Continuous Integration</h2>
CI is all about integrating code and making sure it works.
</section>
<section>
<img src="assets/continious-integration.png">
</section>
</section>
<section>
<section>
<h2>Continuous Delivery</h2>
Continuous delivery is an extension of continuous integration.
</section>
<section>
This means that on top of having automated testing, you also have to automate your release process which will allow deploy application at any point of time by clicking on a button.
</section>
<section>
<img src="assets/press%20button.png">
</section>
</section>
<section>
<section>
<h2>Continuous Deployment</h2>
Continuous deployment goes one step further than continuous delivery.
</section>
<section>
With this practice, every change that passes all stages of your production pipeline is released to your customers. There's no human intervention, and only a failed test will prevent a new change to be deployed to production.
</section>
<section>
<img src="assets/0_781mLWOCCsP5EAHa.png">
</section>
</section>
<section>
<h3>So what's the difference?</h3>
<img src="assets/CIvsCDvsCD.png">
</section>
<section>
<section>
<h2>Advantages and costs of implementing CI/CD</h2>
CI/CD is an investment!
</section>
</section>
<section>
<section data-markdown>
<textarea data-template>
### Continuous Integration - advantages:
- Less buggy product
- Building release is getting easier as all integration issues have been solved
- Whole team is reported about build process
</textarea>
</section>
<section data-markdown>
<textarea data-template>
### Continuous Integration - costs:
- Team needs to write automated tests
- Server for automated tests is required
- Devs need to merge their changes as often as possible
</textarea>
</section>
</section>
<section>
<section data-markdown>
<textarea data-template>
### Continuous Delivery - advantages:
- Automated process of deploying software
- Releases may happens more frequently
- Hotfixes and small improvements can be shipped to production much faster
</textarea>
</section>
<section data-markdown>
<textarea data-template>
### Continuous Delivery - costs:
- Strong foundations in CI process
- Special mindset while developing software is needed
</textarea>
</section>
</section>
<section>
<section data-markdown>
<textarea data-template>
### Continuous Deployment - advantages:
- No release days
- Release are less risky
- Team can fully focus on developing new features
</textarea>
</section>
<section data-markdown>
<textarea data-template>
### Continuous Deployment - costs:
- Testing culture must be at its best. CD process require the highest quality of tests
- Documentation needs to be updated frequently to keep up after deployments
- Overall process is knowlegde demanding and require experienced team
</textarea>
</section>
</section>
<section>
<section>
<h2>How to prepare project for CI/CD?</h2>
Following good practises is a good start...
<img src="assets/process.png">
</section>
<section>
<h3>Use logger middleware for yours apps</h3>
<img src="assets/console.png">
</section>
<section>
<h3>Use linters</h3>
A linter will help avoid errors, and things that could not be errors (but look like them) or could be potentially dangerous.
<img src="assets/linter.png">
</section>
<section>
<h3>Write at least basic unit tests</h3>
These are the foundations of a well-designed CI.
</section>
<section>
<h3>Dependencies should have fixed versions, use `~` instead of `^`</h3>
And don't forget to always commit at least one of yarn.lock or package-lock.json depending on which package manager you're using.
</section>
<section>
<h3>Use dockerfile</h3>
<img src="assets/dockerfile.png">
</section>
<section>
<h3>Create a foundations for integration tests</h3>
<ul>
<li>Prepare docker-compose.yml file</li>
<li>Make use of ORM's libraries like 'sequelize'</li>
</ul>
</section>
</section>
<section>
<section>
<h3>Jenkinsfile</h3>
<img src="assets/jenkins-logo.jpg">
</section>
<section>
<h3>Uses groovy syntax</h3>
<pre>
<code class="hljs" data-line-numbers="3-6">
def hashPath(packVer, length = 16) {
hash = sh(
script: "date | shasum -a 256 | awk \'{print substr(\$0,0,${length})}\'",
returnStdout: true
).trim()
ver = sh(
script: "echo ${packVer} | tr -d '.'",
returnStdout: true
).trim()
return "${ver}${hash}"
}
</code>
</pre>
</section>
<section>
<h3>Let you integrate with 3rd party software</h3>
<pre>
<code class="hljs" data-line-numbers="4-8">
post {
success {
slackSend(
channel: "$slackChannel",
color: 'good',
message: "App successfully deployed - *(${env.BUILD_NUMBER}) ${env.JOB_NAME}* (<${env.BUILD_URL}|Open>)"
)
}
}
</code>
</pre>
</section>
<section>
<h3>Easy integration with docker</h3>
<pre>
<code class="hljs" data-line-numbers="1-8">
agent {
docker {
image 'node:10.15'
args '-u root:root'
reuseNode true
}
}
</code>
</pre>
</section>
</section>
<section>
<h3>Thank you</h3>
You can find this presentation at https://github.com/tetrash/CI-CD-presentation
</section>
</div>
</div>
<script src="js/reveal.js"></script>
<script>
// More info about config & dependencies:
// - https://github.com/hakimel/reveal.js#configuration
// - https://github.com/hakimel/reveal.js#dependencies
Reveal.initialize({
dependencies: [
{ src: 'plugin/markdown/marked.js' },
{ src: 'plugin/markdown/markdown.js' },
{ src: 'plugin/notes/notes.js', async: true },
{ src: 'plugin/highlight/highlight.js', async: true }
]
});
</script>
</body>
</html>