►
Description
We hosted a virtual meetup as part of the GitLab Community Day: CI featuring Michael Friedrich, Developer Evangelist at GitLab, on 2020/12/01.
The recordings features an introduction to GitLab CI including some demos. You can follow along via the links below.
Slides: https://docs.google.com/presentation/d/1oJLEL2OVm0gz8qvIlqpoidGdmsGt1exT2pwbZjaVTaE/edit?usp=sharing
Repository: https://gitlab.com/gitlab-com/marketing/corporate_marketing/developer-evangelism/code/ci-community-day-2020
---
Watch more videos from the GitLab Developer Evangelism team: https://www.youtube.com/playlist?list=PL05JrBw4t0Kq-bYO9jCJaN45BBpzWSLAQ
Find upcoming virtual meetups and resources to plan your own here: https://about.gitlab.com/community/virtual-meetups/
A
All
right,
hi
everyone-
my
name
is
john
coughlin,
I'm
on
the
community
relations
team
at
get
lab,
and
I'm
really
excited
to
be
with
you
all
today
for
our
first
global
community
day
meetup.
This
is
a
new
thing
that
we're
trying
we're
doing
three
meetups
to
allow
everybody
across
all
time
zones
to
participate
in
a
meetup
event.
On
the
same
day,
with
the
focus
on
the
same
topic
and
today
we'll
be
focusing
on
continuous
integration.
A
I
always
like
to
start
our
meetups
by
reminding
folks
about
our
code
of
conduct
at
gitlab.
One
of
our
values
is
diversity,
inclusion
and
belonging,
and
we
like
that
to
extend
to
our
community
and
so
in
order
to
ensure
that
the
community
is
welcoming
and
inclusive.
We
ask
everyone
to
abide
by
our
code
of
conduct
which
I'm
sharing
in
the
zoom
chat
right
now.
So
please
take
a
look
at
that.
You
know
and
and
follow
the
kind
of
guidelines
laid
out
there.
A
If
folks
want
to
report
any
type
of
abusive,
behavior
or
code
of
conduct
violations,
you
can
send
me
a
dm
in
the
zoom
chat
or
you
can
email
conduct
gitlab.com.
I
will
put
that
in
the
zoom
chat
as
well
and
we'll
work
with
you
to
resolve
any
of
your
concerns,
so
with
that
I'm
just
going
to
get
into
a
quick
overview
of
git
lab,
as
we
may
have
some
folks
that
are
new
to
our
community
here,
gitlab's,
a
complete
devops
tool
chain
delivered
as
a
single
application.
A
There's
one
interface,
one
conversation
one
permission
model
and
we
have
thousands
of
features.
We
release
new
features
every
month
on
the
22nd,
so
there's
always
something
new
and
interesting
to
kind
of
play
with
in
gitlab
and
we're
cons
continuously
improving
the
existing
features
as
well-
and
I
think
you
know
if
you
take
a
deep
dive
into
what
gitlab
has
to
offer
you'd
be
pretty
amazed
by
what
we
can
do.
Gitlab
is
an
open
core
company,
so
we
have
an
open
source
version
that
everyone
can
contribute
to
and
there's
many
people
on.
A
This
call
that
I
recognize
from
our
community
who
have
contributed
to
git
lab.
So,
thank
you
for
those
contributions
and,
if
you're
interested
in
getting
started,
you
know
any
type
of
contribution
helps
so
whether
it's
a
documentation,
update
a
translation
or
code
contribution,
or
even
you
know,
organizing
a
meetup
doing
a
tech
talk.
Writing
a
blog
post.
We
appreciate
all
contributions
from
folks
in
our
community,
some
other
cool
things
about
get
lab
pre
covered.
We
are
one
of
the
largest
all-remote
companies
in
the
world.
A
A
I'd
love
for
everyone
to
share
where
they're
joining
from
in
the
zoom
chat.
This
is
a
global
event,
and
so
it's
always
interesting
to
see
where
folks
are
kind
of
joining
us
from
and
lastly,
you
know
close
your
tabs
mute
slack
and
just
you
know,
try
and
relax
and
enjoy
the
presentation
from
michael,
oh
and
one
more
thing:
there's
a
hashtag.
If
you
want
to
tweet
about
this,
it's
hashtag
gitlab
community
day.
I
will
put
that
in
the
chat
as
well.
A
B
Thanks
officially,
I
have
30
minutes,
but
I'm
known
to
be
to
extend
it,
maybe
but
yeah.
I
want
to
want
to
dive
into
best
practices
with
gitlab
cicd.
I've
shared
the
slides
in
the
zoom
chat,
so
you
can
follow
along
and
you
when,
when
we
jump
into
the
exercises
later
on,
you
can
also
do
it
either
in
the
session
or
do
it
as
in
chronology.
B
Today.
It's
me,
we
are
on
the
team,
so
you
know
john
already
brenda
and
I've
seen
is
also
on
the
call
and
abu
bakr
who's
also
on
our
developer
eventualist
team
for
the
agenda
today.
First
off,
I
want
to
start
with
a
like
short
introduction.
What
is
ci
cd?
Then
we
dive
a
little
bit
into
the
first
steps,
with
practical
exercises
later
on,
checking
out
the
go
project
and
doing
checking
out
some
cr
security
practices.
B
B
B
Okay,
then,
let's
dive
a
little
bit
into
an
introduction
and
like
hear
a
little
bit
about
the
key
concepts
of
ci
cd.
So
you
need
to
know
what
is
a
job
where
you
want
to
execute
something.
You
have
a
pipeline
which
is
kind
of
a
set
of
stages.
You
might
hear
about
environments
and
environment
variables,
which
can
be
used
for
pyramid
for
parametrizing
jobs,
for
example,
you
wanna
hear,
or
you
wanna
remember,
chop
artifacts
as
outputs
and
oftentimes.
We
reference
gitlab
runner,
which
is
a
job
executor.
B
B
You
can
also
run
it
in
kubernetes
and,
for
example,
for
auto
scaling
in
aws.
You
could
also
use
docker
machine
and
it
kind
of
it
actually
connects
to
a
gitlab
server
and
can
be
attached
to
groups
to
single
projects
to
the
global
instance
and
and
the
like,
coming
from
the
gitlab
runner
to
the
pipelines.
This
is
a
basic
example.
How
a
pipeline
could
look
like
you
start
your
code.
You
commit
something.
You
run
the
unit
test
in
your
ci
pipeline.
You
run
integration
tests
and
later
on,
you
deploy
it
into
a
staging
environment.
B
B
B
You
get
fast
feedback,
you
can
fix
problems
fast
and
you
don't
like
have
to
fix
the
bug
when
it's
in
production,
because
oftentimes
our
development
cycles
require
us
to
ship
fast,
because
otherwise
a
competitor
would
probably
copy
the
idea
or
we
want
to
just
see
something
going
on.
Like
tick,
tock
started
out
some
somehow
and
it
might
not
be
perfect,
but
still
you
want
to
ship
fast.
There
are
some
processes
and
toolings
involved
in
inside
the
cicd
workflow,
which
can
help
you
achieve
that.
B
As
I
said
before,
we
do
have
jobs
and
stages,
so
we
can
have
a
simple
pipeline
which
we
will
try
out
in
a
few
minutes
where
we
want
to
just
build
the
code.
We
want
to
test
the
code.
We
want
to
deploy
the
code,
build
packages
and
deploy
to
production,
for
instance,
but
we
also
have
different,
or
we
have
more
advanced
possibilities
where
we
can
say
hey,
I
want
to
maybe
run
run.
B
It
run
chops
asynchronously
because
there
could
be
some
blocking
mechanisms
inside
I
could
run
or
I
can
run
pipelines
over
multiple
projects.
I
can
run
a
parent
pipeline
which
triggers
a
child
pipeline,
isn't
quitely
and
even
more
than
that-
and
there
is
also
mention
of
merge
strange.
This
is
this
is
also
an
advanced
example.
It's
just
here
that
you
have
heard
some
of
the
things,
but
today
we
also
want
to
look
into
what's
possible,
but
start
with
the
small
things.
B
One
of
the
things
which
also
came
came
in
recently,
so
the
visualization
layer,
where
we
also
are
iterating
on
and
improving
the
general
pipeline.
For
you,
this
one
is
especially
interesting
because
you
can
figure
out
the
critical
path.
So
how
long
does
my
ci
power
plan
take
to
complete
and
maybe
figure
out
where
you
can
improve
the
pipeline
efficiency
and
saving
cloud
resources
and
and
costs
in
the
long
run?
B
So,
for
example,
if
a
public
run
takes
seven
minutes,
you
might
kind
of
want
to
investigate
and
optimize
and
refactor
the
pipelines
later
on,
for
the
configuration
we'll
probably
or
you
have
probably
heard
about
the
yammer
configuration
format
in
the
dot
gitlab
dash
ci
dot
yammer.
There
are
several
templates
around
making
your
lives
easier.
We
will
try
that
later
on
in
a
go
project,
and
we
also
do
have
other
devops,
which
is
an
opinion
opinionated
collection
of
ci
cd
templates.
B
Other
than
that,
if
you
say
hey,
I
want
to
dive
a
little
more
deep
from
cicd
to
security.
Our
security
tests
also
run
in
ci
cd
pipelines,
and
you
can,
for
example,
detect
secrets.
You
can
detect
static
security
problems,
automated
dynamic
application,
security
testing,
so
meaning
to
say
you
run
a
rest
api
and
you
simulate
some
security
problems.
Lately
there
was
fast
testing
being
added
and
there's
so
much
more.
I
think
yeah
chaos.
B
Engineering
is
not
not
on
the
plate,
but
this
is
definitely
something
to
look
out
for
next
year,
but
anyhow,
this
is
lots
of
theory.
Let's
dive
a
little
bit
into
the
first
steps
with
ci
cd.
So
just
to
remember,
we
kind
of
want
to
work
on
to
something
we're
saying
now.
I
have
assigned
a
task
to
myself.
I
want
to
create
a
much
request.
B
So
there
is
no
terminal
involved
right
now,
we're
just
doing
everything
in
the
browser
we
will
be
creating
a
gitlab
ci
configuration
file
and
one
of
the
things
we
want
to
do
is
we
want
to
run
a
job
called
test,
underscore
simple,
which
executes
a
script
which
is
exit
one
and
the
image
is
alpine,
because
this
is
the
smallest
one
you
can
actually
use.
If
you
have
forked
the
repository
repository
already,
you
can
just
jump
in
right
here.
B
The
web
id
can
be
accessed
from
the
shiny
button
over
here
and
then
I'm
saying
I
want
to
add
a
new
file
which
is
in
the
menu,
and
I
don't
need
to
type
it
it's
already.
I
can
select
it
and
then
say
hey,
I
want
to
say
it's
image
and
it's
alpine
and
the
colon
means
that
the
lat
we're
using
the
latest
tag,
and
let
me
just
check
what
let's
test
underscore
simple:
this
is
the
job
definition
and
the
job
name.
This
can
be
freely
defined.
B
We
want
to
execute
a
script
and
this
needs
a
dash,
and
then
we
just
say
we
want
to
execute
exit
one.
Then
I
say
I
want
to
commit
it.
The
branch
name
should
be
ci-test,
so
we
don't
commit
anything
to
the
main
branch
now
and
we
say
we
want
to
add
as
ci
config
and,
let's
just
start
a
new
match
request
and
I
can
assign
it
to
me
and
then
we're
just
waiting
for
the
pipeline
to
kick
off
to
start,
hopefully
fast
enough.
B
The
thing
is
now:
it's
broken
and
one
of
the
reasons-
maybe
you
can
guess
it
already
why
it's
broken,
but
I
want
to
just
go
in
there
and
check
it
and
I'm
navigating
into
the
chops
output,
and
I
can
see
what's
going
on
so
actually
the
gitlib
runner
fetches
the
job,
it's
executing
a
docker
image,
starting
the
docker
image.
So
it's
it's
my
sandbox
environment,
where
I
can
run
the
tests
and
it
it
will
be
the
same.
Every
time
it
gets
gets
executed.
B
B
So,
in
order
to
kind
of
say,
hey,
I
want
to
fix
this
now,
let's
just
navigate
back
into
our
merge
request,
which
can
be
accessed
over
here,
for
example,
and
we
can
also
edit
a
much
request
inside
the
web
ide
seeing
here.
This
is
the
diff
view,
but
I
could
also
just
say:
hey,
I'm
stepping
back
over
here
and
making
this
a
zero
zero
means,
no
error
or
keyword
in
a
linux
terminal,
unix
terminal
and
we
commit
the
change
into
the
same
branch
and
say:
hey.
We
have
one,
we
fixed
the
ci
test.
B
B
I
can
see
at
the
bottom
that
the
pipeline
is
running,
so
this
is
like
the
same
as
you
get
within
with
the
visual
studio
code,
gitlab
workflow
extension,
or
you
could
also
click
here
on
the
rocket
icon
to
see
what
what
the
pipeline
status
is
meaning
to
say,
you
don't
don't
need
to
leave
the
context
now
you
don't
need
to
switch
context
and
maybe
get
distracted
and
then
coming
back
again.
So
the
thing
is
now:
this
pipeline
succeeded
exit
zero
and
everything
is
fine.
B
B
Variable,
for
example,
the
build
type
and
you
can
specify,
beat
release
debug
and
everything
else
and
accessing
it
is
just
like
you
would
access
if,
if
the
job
gets
executed
on
linux
or
unix,
just
like
he
would
access
available
in
in
the
shell
syntax,
I
think
for
for
windows,
you
need
to
use
the
percentage
sign,
or
is
it
dot
end
something
around
that
so
in
this?
In
this
regard,
we
can
just
reuse
the
rivers
and
instrument
how
the
job
behaves
from
the
outside.
B
B
When
we
dive
a
little
deeper
into
a
go
project,
so
we
kind
of
say
hey:
we
have
some
code
now
and
we
inherited
this
from
a
former
colleague
or
we
just
want
to
start
maintaining
it
and
probably
have
migrated
it
from
svn
or
something
else
other
than
git
and
the
code
doesn't
have
any
tests.
So
one
thing
is:
the
repository
provides
us
with
some
go
code,
and
this
typically
looks
like
this.
B
We
have
the
main.go,
it
executes,
something
says
hello,
but
we're
not
sure
if,
if
this
will
be
working
and
and
how
how
things
are
going
so
the
first
iteration
of
the
first
step
is:
we
want
to
know
whether
it's
builds
or
not,
and
the
thing
is
well
how
to
start
start
with
that.
The
good
thing
is
so
the
we're
lucky
to
have
a
ci
cd
pipelines.
B
And
templates
in
that
regard,
so
it's
possible
that
we
navigate
into
our
repository
now
and
use
the
web
id
again
and
we
want
to
edit
or
we
want
to
create
a
new
gitlab,
cr
yaml
file
and
right
now
we're
hopping
over
here
into
the
templates
and
a
little
bit
down
below.
There
should
be
the
gold
template
which
we
can
reuse
again.
B
B
So
in
that
regard
it
prepares
the
go
environment.
This
is
basically
some
swim
link
magic.
The
most
important
parts
are
happening
down
below,
so
we're
defining
stages
in
the
test
stage.
The
format
job
is
running,
which
basically
does
some
formatting
for
go
and
detects
whether
the
syntax
is
correct
and
also
executes
unit
tests,
which
might
have
been
defined
already.
B
The
compile
stage
actually
built
the
binary
and
within
the
dash.o
flag
you
get
the
tanuki
binary,
which
then
gets
attached
to
the
chop
artifacts.
So
you
can
actually
download
the
binary
and
test
it
do
something
with
it
pass
it
along
and
things
like
that
whenever
the
artifact
is
available,
you
can
also,
for
example,
interact
with
it
using
the
rest
api
trigger
some
child
pipelines
or
do
whatever
you
want.
B
The
thing
is
now
I'm
interested
in
that
the
job
workers
that
is
the
code
building
for
some
reason,
the
pipeline
status
is
red,
and
this
is
not
good.
Let's
just
see
how
things
are
going,
the
test
job
or
the
test
stage
with
the
format
shop
failed
and,
as
you
can
see,
when
the
first
job
failed.
The
second
job
doesn't
execute.
B
Let's
just
check
in
there
and
say:
hey
what's
going
on,
I
want
to
know
it.
Everything
which
is
green
is
not
interesting
currently,
but
there
we
see
it.
We
have
an
undeclared
name
os,
so
probably
in
main.go,
in
line
12
and
character,
16
there's
something
going
on.
I
think
I
think
about
it
to
open
a
future
request.
Just
click
on
that,
but
yeah.
If
we
navigate
back
into
our
merch
request
now
and.
B
We
have
line
12
here,
it's
using
os.getends,
which
is
reading
an
environment
variable
and
we
probably
should
just
import
os
and
later
on
we're
also
using
fmt.
So
I've
prepared
it
over
here
already.
We
just
need
to
import
fmt
and
os.
So
just
removing
these
commented
out
functionalities
and
then
we
can
say:
okay
fix
the
build.
Oh
no,
that's
not!
A
good
commission
commit
message,
fix
missing
imports
for
os
fmt
functions.
B
But
for
now
we
want
to
just
hopefully
see
something
and
at
this
point
we're
using
the
gitlab.com
shared
runners
fleet
now,
which
is
running,
which
is
using
the
same
pool
for
everyone.
If
you
have
heavily
built
or
heavy
jobs
where
you
rely
upon,
I
would
totally
recommend
to
use
your
own
runners
assign
resources
for
it
and,
if
you're,
for
example,
using
a
self-hosted
environment,
you
could
also
go
the
way
and
say
hey.
B
This
specific
runner
is
assigned
to
a
group
which
compiles
a
c
plus
plus
code
or
rust
code,
because
this
can
like
take
a
lot
of
resources
and
the
other
runner
which
has
not
so
many
resources
just
runs
some
javascript
or
some
node.js
test
or
something
else
which
doesn't
need
heavy
resources
for
compiling
okay.
The
job
continued
actually
we're
interested
in
the
entire
pipeline,
just
because
we
have
the
format
shop
and
it's
actually
building
something
for
us,
and
in
the
moment
I
clicked
on
it.
It
already
succeeded,
so
this
is
wonderful.
B
B
B
Therefore,
we
open
up
the
much
request
again
navigate
into
the
web
ide.
If
you
haven't
done
so,
you
can
also
switch
branches
and
merge
requests
within
the
web.
Ide,
and
one
thing
we
want
to
do
is
we
want
to
edit
the
github,
ci
yammer
and
add
a
new
job
at
the
bottom
and
call
it
run.
I
think
let
me
just
check
yeah,
we
want
to
add
it
to
the
employ
stage
and
we
also
execute
the
script,
and
this
is
a
dash
dot,
slash
tanuki.
We
want
to
execute
the
tanuki
binary.
B
We
just
want
to
see
what's
printed
on
on
std
out
and
even
start
it.
This
is
the
same
as
when
you're
running
any
any
type
of
cli
command,
just
to
see
how
things
are
going.
We
commit
this
at
run.
Job
for
tenuki
executions
are
sound
strange
and
we're
committing
this
and
again
waiting
for
the
cicd
builds
to
continue
and
we
can
see
on
the
right
hand,
side.
B
B
This
can
be
done,
for
example,
with
adding
a
unit
test
stage
running
a
specific
script,
then
with
go
test
cover
and
it
have.
I
have
that
visualized
inside
the
merge
request,
other
things
which
are
possible
like
when
you're
not
talking
about
golang
junit,
is
a
like
a
standard
format
which
requires
you
to
generate
some
xml
report
format.
It
can
then
pass
that
and
integrate
it
within
the
much
request
view
and
you
get
a
nice
overview
which
jobs
have
executed,
specific
tests
and
even
more
so.
B
This
is
a
nice
way
to
integrate
that
still
talking
and
we
want
to
see
whether
it's
actually
being
running
so
yeah.
In
this
case,
it's
running
it's
saying
hello
and
we
have
the
tanuki
summoned,
and
hopefully
everyone
else
has.
If
you
do
have,
please
take
a
screenshot
share
it
on
twitter,
with
our
gitlab
community
day.
B
B
One
thing
about
cicd
or
ci
security:
is
it's
not
only
about
unit
tests
and
testing
your
code
and
building
your
code
and
running
your
code?
You
also
want
to
want
to
make
sure
that
no
one
accidentally
pushes
any
secrets
or
credentials
oftentimes.
It
could
be
your
dot
end
environment,
which
has
been
added
to
the
git
repository
or
there's
a
certain
aws
key
hard
coded
in
your
test
scripts,
or
maybe
even
hard
coded
somewhere
else
in
the
source
code,
and
it's
oftentimes.
B
It's
really
hard
to
detect
it
because
you
don't
know
the
regular
expression
or
the
the
terminology
of
specific
keywords,
and
there
are
certain
mechanisms
available,
so
called
security
scanners
or
secrets
scanners,
which
know
about
these
they're
all
open
source
and
gitlab
integrates
them
into
the
ci
cd
pipeline,
and
one
of
the
things
we
can
do
is
it's
super
easy.
You
don't
need
to
write
your
own
job.
B
You
can
just
include
a
template
which
is
also
like
hidden
in
the
auto
devops
templates,
just
for
secret
detection,
and
if
we
navigate
back
into
our
ci
cd
configuration
which
is
over
here,
we
can
also
just
say
hey.
We
want
to
include
this
template,
oh
okay,
I
need
to
type
it
no
copy
paste
for
me
we
want
to
include,
or
maybe
yeah,
I
have
prepared
an
entire
complete
solution,
and
this
is
this
is
where
you
can
kind
of
verify.
B
If
everything
worked
out
for
you
just
this
is
kind
of
the
the
god
cheat.
If,
if
you
want
to
master
everything,
we
can
just
include
the
security
template
just
need
to
yeah
context,
and
we
say,
let's
put
it
over
here,
we
want
to
include
the
secret
detection
template.
I
could
just
open
the
documentation
and
copy
it
from
there,
and
I
also
have
the
possibility
to
parametrize.
B
A
B
B
B
If
I
want
to
check
it
out
in
a
way
of
going
back
into
my
merch
request,
which
should
be
over
here,
it's
still
running,
but
the
security
scanning
will
be
embedded
in
here.
If,
if
you
do
have
a
gold
plan,
for
instance,
but
still
could
also
like,
say
hey,
I
want
to
pass
this
and
I've
added
an
aws
key
by
accident
by
accident.
Yeah.
B
B
This
actually
just
tells
me
yeah.
You
have
been
adding
something
or
it
already
exists,
and
this
aws
key
needs
to
be
revoked
and
you
need
to
do
some
rollbacks.
You
could
also
like
create
a
confidential
issue.
Out
of
that,
or
even
say,
I
want
to
dismiss
this
vulnerability,
but
I
wouldn't
recommend
to
do
it.
B
Another
way
of
like
looking
into
this
is
to
test
your
code
for
static
vulnerabilities,
which
could
be
something
like
you
do,
a
chmod
777
for
something
like
having
a
world
readable
and
writable
file
and
reading
from
that
could
also
lead
into
unwanted
behavior,
or
maybe
even
privacy,
leaks
security
problems
and
the
like.
So
this
one
is
just
check.
B
B
B
B
B
B
Pressing
f5,
okay
continued,
and
now
we
have
four
potential
vulnerabilities.
One
of
them
is
two
of
them
are
medium,
which
means
unsafe
method
close
on
type,
okay,
something
I
did
by
accident.
I
didn't
really
plan
with
that
vulnerability,
and
the
nice
thing
is,
I
just
can
click
over
here
and
I'm
opening
direct.
I
can
see
directly
in
the
line
where
the
where
the
problem
is
going
on.
It's
unsafe,
oh
yeah.
I
didn't
check
whether
this
creates
something
useful,
so
I'm
not
checking
the
error
code
in
that
regard,
and
probably
we
shouldn't
do
that.
B
B
Okay,
there
is
way
more
than
that,
so
you
can
use
different
crcd
security
scanning
mechanisms.
I
would
also
recommend
checking
out
the
first
testing.
I
find
it
fascinating
to
kind
of
imagine
what's
what's
going
on
and
battle
test,
your
application,
but
yeah
anyhow,
the
thing
is
self
practice.
This
is
your
kind
of
home
exercise.
B
You
can
inspect
inspect
or
you
can
see
that
the
test
coverage
drops
or
increases
and
yeah
it
at
your
own
function,
tests
into
the
test
framework
for
with
go.
If
you
haven't
done
it
before,
I
just
want
to
learn,
go
and
last
but
not
least,
I
would
recommend
to
add
some
tests
and
coverage
pipelines
status
patches.
So
you
don't
need
to
edit
the
whitney
readmemd,
like
you
know,
probably
from
other
keep
vendors.
B
You
can
just
edit
the
project
settings
and
have
that
available
natively
inside
your
gitlab
project
other
than
that.
What's
next
lots
of
things
because
ci
cd
is
not,
we
didn't
touch
many
things
today,
but
I
would
totally
recommend
to
check
out
environments
combined
with
review
apps,
making
your
life
easier
check
out
how
githubs
with
kubernetes,
terraform
and
nzip
works
figure
check
out
the
pipeline
efficiency
documentation.
B
Seeing
is
believing,
I
hope,
to
see
in
our
future
meetups
or
like
online
check
out
the
training
resources
linked
and
if
there
are
any.
Hopefully
there
are
many
questions
now.
Please
shoot
I'm
happy
to
happy
to
help,
and
if
not
today,
just
ping
me
on
on
twitter
or
ping
us
on
twitter
and
we're
happy
to
help
thanks.
A
B
B
I
would
say
it's
hard
pick
a
topic
make
a
wish
list
find,
find,
find
people
of
of
interest
or
like
find
it
find
a
common
topic
we
also
or
I'm
I'm
also
hosting
a
coffee
chat
round,
which
is
called
everyone
can
contribute
coffee
or
coffee.
This
is
an
english
version.
We
also
have
a
german
version.
This
there
is
some.
This
is
one
of
the
things
where
we
just
want
to
try
things
out.
So
lately
we
tried
out
grafana
temple
specific
things
with
captain
for
cd.
B
A
And
michael,
what's
the
best
way
for
folks
to
contact
you
if
they
have
a
topic
or
even
if
they'd
like
to
you
know,
be
involved
in
one
of
the
conversations,
I
know
you
have
a
project
for
your
coffee
chat
groups,
but
is
that
the
best
way
for
people
to
get
in
touch
or
is
it
through
twitter?
How
do
you
recommend
people
reach
out.
B
So
I
I'm
super
fast
on
twitter,
sometimes
I'm
taking
time
off,
because
mental
health
is
important,
but
if
you
want
to
reach
out,
my
dms
are
open
on
twitter,
but
you
can
also
like
just
tag
me
or
add
me
on
on
twitter,
and
we
can
make
things
happen.
Apart
from
that,
we
can
also
move
into
coffee,
chats
and
other
things
around.
B
A
A
A
All
right,
so
I
just
have
a
few
remarks.
I'd
like
to
share
before
we
wrap
things
up
and
and
end
the
session.
First
of
all,
I
want
to
you
know
thank
michael
for
a
presentation.
One
thing
we
do
at
all
of
our
virtual
meetups
is
unmute
and
give
a
round
of
applause
to
our
presenter.
So
if
folks
will
join
me
by
unmuting
themselves
and
just
giving
michael
a
round
of
applause,
we
can't
all
be
together,
but
we
can
still
show
our
appreciation.
Thank
you,
michael.
A
A
Doing
an
ama
and
they'll
also
be
doing
a
sneak
preview
of
the
roadmap
and
the
visual
pipeline
builder.
So
you'll
get
a
look
into
kind
of
some
of
our
plans
for
the
future
for
ci
and
it
should
be
a
pretty
exciting
event
and
pretty
interesting
as
well.
So
I
hope
you'll
join
us
there
there's
also
through
our
get
lab
chicago
group.
A
Another
meet
up
next
week
with
a
focus
on
ci
and
that's
going
to
be.
I'm
sorry,
that's
actually
later
this
week.
So
that's
on
thursday
december
3rd
and
I'll
put
a
link
to
that
in
the
chat
as
well.
So
if
you're
looking
for
more
gitlab
ci
content,
I'd
recommend
registering
for
those
meetups
and
participating
in
them.
I
think
those
will
both
be
good
events.
A
I
especially
encourage
you
to
join
the
ama
with
our
gilab
ci
fcit,
for
folks
that
are
wondering
about
the
swag
that
was
promised,
we'll
be
sending
out
a
follow-up
form
to
everyone.
So
keep
your
eyes
peeled
for
that.
That's
going
to
be
sent
via
meetup,
so
make
sure
you
have
notifications
turned
on
for
your
meetup
account
and
we'll
be
reaching
out
through
the
meetup
group
to
collect
contact
information
so
that
we
can
send
out
some
a
special
kind
of
thank
you
to
everyone
for
participating
today
and
then.
A
Lastly,
you
know
virtual
meetups
have
really
become
part
of
our
community
over
the
last,
I
guess
eight
months
and
we
intend
to
keep
them
going
for.
As
you
know,
as
long
as
we
can't
be
together
in
person
and
likely,
you
know
even
bringing
the
community
together
virtually
after
that
and
so
we'd
love
for
you
to
remain
involved
either.
You
know
as
an
attendee
or
as
a
speaker,
or
you
know,
someone
who
proposes
topics.
A
So
if
you
have
a
talk
that
you'd
like
to
give
or
a
topic,
you'd
like
to
talk
about
or
topic
you'd
like
to
hear
about,
we
love
your
feedback
to
kind
of
help.
Us
make
sure
that
this
group
is
representing
the
interests
of
the
community
and
you
can
reach
out
to
us
evangelist,
gitlab.com
and
we'll.
You
know
we
can
start
a
conversation
on
you
know
having
you
come
and
speak
to
the
group
or
trying
to
find
a
speaker
to
address
a
topic
that
you're
interested
in.
A
So
please
feedback
really
is
helpful
to
us
and
we'd
love
to
hear
from
you
and
with
that
I
think
we'll
wrap
things
up
for
the
day.
Thanks
again,
everyone
for
being
here.
Thank
you,
michael
great,
to
see
so
many
folks
participating
and
if
you
want
to
give
michael
kudos,
it's
at
dns
m-I-c-h-I
and
you
can
tweet
with
git
lab
community
day
and
I
hope
to
see
you
at
a
virtual
meetup
again
soon
thanks
everyone.