►
From YouTube: Intro to GitLab CI/CD Webinar
Description
Come learn about what CI/CD is and how it can benefit your team. We will cover an overview of CI/CD and what it looks like in GitLab. We will also cover how to get started with your first CI/CD pipeline in GitLab and the basics of GitLab Runners.
A
Hello,
everyone
we
are
just
going
to
give
everybody
a
minute
or
so
to
get
started
to
join
and
yeah
we're
gonna
run
with
a
session,
so
bear
with
us
for
a
minute
grab
a
copy
grab
some
water,
and
we
will
be
starting
very
shortly.
A
A
Okay,
yeah,
as
far
as
I'm
wearing
the
previous
recording
has
been
sent
out
already.
If
you
did
receive
this
I
think
that's
something
we
can
follow
up
after
the
session.
So
what
they're
referring
to
is
that
we
had
a
previous
introductory
to
gitlab
session
last
week,
so
that
is
also
available.
I
think
we
are
good
to
go
we're
good
to
start
so
welcome
in
into
this
introduction
to
GitHub
session.
Today
we
are
going
to
be
going
over
a
foundational,
beginner
context
and
the
usage
of
cnfd
and
how
it
could
benefit
your
team.
A
If
you
were,
you
know
to
start
using
it,
we're
also
going
to
go
to
a
bit
of
an
overview
of
cicd
and
what
it
looks
like
in
GitHub
we're
going
to
get
started
with
your
first
CIT
Pipeline
and
the
basic
of
gitlab
Runners
as
well,
so
that
they
all
kind
of
make
sense
to
you.
What's
going
to
be
out
of
scope.
Hot
water
for
today
is
a
detailed
development
configuration
for
standard
CD
Runner,
also
in-depth
youth,
Vision
best
practices
for
project
management.
A
That's
not
going
to
be
part
of
it
in
system,
initial
setup
and
management.
I
just
wanted
to
kind
of
straight
for
everybody,
but
we
also
have
accused
the
board
by
our
association
architect
in
here.
So
thank
you
to
him
for
helping
us
and
yeah.
Let's
get
started,
so
let
me
quickly
introduce
myself.
My
name
is
Gregory
shoppingkuff
I'm,
a
customer
success
manager
here
for
strategic
Enterprise
account
and
I'm
coming
to
you
from
Dublin
Ireland
a
little
bit
about
myself
there
before
joining
it
lab
I
was
a
technical
account
manager
at
so
forth.
A
Marketing
working
for
marketing
Cloud,
where
they
both
slightly
different
problems.
So
in
terms
of
what
we're
going
to
be
covering
in
here
in
CISD
overview,
setup,
Runners
and
at
the
end,
we'll
have
plenty
of
time.
I
think
we
will
have
around
Maybe
15
to
20
minutes
to
discuss.
Then,
if
you
wanted
to
have
any
kind
of
difficult
questions,
and
you
wanted
to
speak
up
absolutely
you'd,
be
more
than
welcome
to
do
that.
A
No
before
we
get
started
yeah
it's
indeed,
some
of
you
might
not
not
working
like
the
relationship
from
one
Bridge
fly
around
working
elaboration
or
problem.
It
solves
essentially
you'd
love
with
a
figure
platform,
and
that
supports
four
ten
stages
of
the
developed
life
cycle,
and
you
can
see
them
there
in
the
middle.
It's
sort
of
one
interface,
one
unified
their
model
and
it's
a
fully
integrated
software
developer
platform
that
enables
Azure
teams
to
be.
You
know:
transparent,
effective
and
cohesive.
A
From
discussions
on
new
idea
to
production
right
all
the
same
platform,
you
can
manage
projects,
not
tools
with
good
luck.
You
get
a
complete
device
platform
and
within
one
application,
and
the
main
idea
here
is
that
you're
able
to
bridge
Dev
and
opt
in
the
main
purpose
of
today's
webinar
is
to
discuss
industry
Dynasty
and
how
it
empowers
all
teams
to
work
together
a
lot
more
efficiently.
So
a
couple
words
about
gitlab,
some
of
you.
A
If
you
have
been
to
one
of
our
webinars
before
you
might
have
seen,
this
provides
it's
the
only
one
that
happens
a
reference
from
previous
webinars
and
it
essentially
how
the
work
organized
in
GitHub
and
at
the
very
top,
you
see
guitar
groups
and
they
provide
capabilities
for
assembling
related
projects
together
and
brand
members
access
to
several
projects
at
once.
A
Some
groups,
on
the
left
hand
side.
You
see
that
they
are
nested
and
Trail
groups
for
additional
levels
of
organization.
Let's
say:
team,
a
functional
group,
a
business
Union
and
more
important
to
our
way
to
collaborate
on
work,
write
code
or
the
other
applications,
and
it
always
great
to
know
how
things
are
organized
now.
This
is
a
very
heavy
slide.
There's
also
there's
a
lot
of
I,
think
jargon
here
and
a
lot
of
technology
so
bear
with
me,
maybe
heavy,
but
it's
also
quite
interesting.
A
So,
let's
start
with
A
continuous
integration
and
continue
the
delivery
right.
What
are
they
and
they
can
be
thought
of
as
a
culture,
a
methodology
that
are
operating
principles
and
a
collection
of
practices
that
enable
application
development
seems
to
deliver
code
changes
what
frequently
inefficient
right.
A
Each
integration
would
then
be
verified
by
animated
pipeline
of
script
that
build
and
automated
tests
before
merging
them
into
the
main
branch.
So,
while
automated
testing
is
not
strictly
part
of
the
eye
is
typically
implied
so
one
step
further,
we
have
continued
delivery.
It's
the
practice
of
keeping
your
code
base
Deployable
at
any
point.
If
you're
making
sure
your
application
path
with
automated
tests,
you
have
to
have
all
the
configuration
necessary
to
push
it
into
your
production.
A
Many
teams
then
do
push
changes
that
has
the
automated
tests
or
production
environment
immediately
to
ensure
Advanced
kind
of
development,
Loop
and
the
last
but
not
least,
is
the
continuous
deployments.
It's
also
related
to
to
reduce
integration,
but
pushes
change
to
production
automatically.
A
A
The
old
leads
to
low
risk
relief,
pass
the
time
to
Market
high
quality
when
developers
have
automated
tools,
the
Discover
versions
within
minutes
in
the
free
Focus
efforts
on
you
know
something
else:
user
research.
And
what
have
you
also
over
costs
by
investing
and
build
as
deployment
and
environment
automation,
you
can
actually
reduce
the
cost
of
making
and
delivering
incremental
changes
to
Software.
A
So
that's
what
I
wanted
to
cover
on
this
slide
in
terms
of
what
is
cintd
I
know,
there's
a
lot
here:
you're,
probably
not
going
to
remember
all
of
it,
but
it
took
me
quite
a
while
to
get
my
hand
around
it,
the
first
time
wow
now.
So
why
use
it
right
because
yeah,
it
didn't,
encourages
collaboration
across
departments
and
make
cooperation
and
management.
Easy
assault
provides
the
if
you
were
the
following
very
specific
benefit
right:
yeah
I
did
that
very
quickly.
A
You
can
fix
there
while
they're
fresh
and
you
might
try
to
get
the
feedback
right
away.
It's
like
random
account.
You
know
the
problems
were
faced
because
you
just
walked
in
the
code
and
Community
deployment
delivered
by
quickly
and
more
often
because
you
can
get
past
if
you
buy
from
what.
If
your
end
users
care
about
yeah
I
also
would
do
for
the
situation
problems
and
we
need
a
deployment
it
converts.
A
Every
change
is
reasonable
right,
more
iteration
and
the
forward
is
the
risk
of
each
release
and
allow
really
to
be
boring
right
because
the
impact
isn't
high
if
the
changes
are
very
small.
This
is,
regarding
that
well,
NCI
allow
teams
to
develop
faster,
more
confidence
among
Developers
what
we're
making.
A
So
this
is
notify
that
might
be
familiar.
You
might
have
seen
this
around.
If
not,
let
me
walk
you
through
this.
Let
me
there
are
many
steps
to
get
from
an
idea
to
production
solution
rate,
and
this
graphic
shows
the
gitlab
4
process
and
this
weapons
can
apply
to
anything
about
a
feature
and
security
vulnerability.
A
So
we
should
get
two
great
lines
like
one
goal
from
Top,
not
straight
and
one
likely
above
it
and
they
represent
two
branches.
So
with
all
the
work
being
done
on
a
feature
Branch
at
the
top,
where
you
see
a
lot
of
who
scored
me
to
add
all
of
that
right
suppose
if
I
walk
between
this
line
here
unlock
one
side,
everything
starts
with
an
epic.
Epic
is
a
it's
a
collection
of
issues
that
are
grouped
by
dream
right.
A
Then
they
are
assigned
to
a
milestone,
the
specific
time
frame
in
which
they
will
have
to
be
completed
by
then
they
are
within
them.
You
will
have
issues
and
the
issues
are
fundamental
kind
of
planning,
an
object
where
or
is
planned
and
is
done
in
this
car,
and
after
that
you
would
assign
that
issue
in
future
brand
at
the
top.
Now,
as
you
can
see
here,
we're
going
out
to
create
merger
class,
it's
the
white,
actual
change
is
happening
or
the
new
feature
is
being
developed
and
developers
done
the
work.
A
A
Loop
goes
at
the
very
top
and
the
fixes
then,
are
supposed
to
be
that
bucket,
developer
who's
introduced
this
right
and
until
they're
done
developer,
will
not
be
able
to
get
the
approval
process
or
even
get
the
review
off
where
it
could
be
able
to
give
you
review
the
changes,
or
maybe
that
would
be
up
to
18.,
wants
to
know
what's
been
interested
in
each
one.
A
And
after
that,
if
everything's
happy
collaboration,
review
done,
approval
has
gone,
then
the
merge,
quick
feature
branch
is
accepted
into
main.
It
is
in
release
and
deployed
to
production.
So
this
is
the
GitHub
recommended
process
so
because
GitHub
allow
a
wide
variety
of
branching
strategies
and
workflow
and
because
of
what
we're
seeing
is
main
Innovation
end
up
with
workflow
that
are
not
like
this.
They
are
different,
it
might
be
complicated,
but
not
clearly
defined
or
not
integrated.
A
At
all,
so
before
we
propose,
which
is
here
on
the
screen,
is
the
it's
not
kind
of
a
best
practice.
Can
you
define
kind
of
best
practice,
but
depending
on
where
you
work
or
where
you
might
be
implementing,
it
might
be
different,
which
is
okay,
so
also,
let's
start
with
galaxian,
and
see
the
overview,
because
GitHub
encompasses
the
entire
off
of
the
development
life
cycle
could
use
integration
to
the
art,
automated
testing,
building
and
deployment
they're
fully
integrated
the
gitlab.
A
They
can
run
into
multiple
stages,
they're
scalable,
everything
that
we're
going
to
cover
in
the
next
couple
of
slide.
Now
we
know
what
the
whole
world
I
suppose,
let's
zoom
in
a
little
bit
on
the
cint
pipeline
in
very
kind
of
specific
term,
like
I've,
discussed
what
it
is
first
of
all
right.
So
this
lock
pipeline
is
the
fundamental
building
block
of
continuous
integration
and
deliver
in
deployment
all
the
terms,
but
we
have
just
just
passed.
A
Pop
button
will
be
created
when
a
new
push
is
made
a
pretty
good
lab
Repository.
The
pipeline
will
then
immediately
run
when
it
is
an
idle
gitlab,
Runner
or
I'll,
be
putting
you
if
available,
Runners
are
being
requested
if
you've
never
heard
the
term
Runner.
At
the
end
of
this
presentation,
we're
going
to
cover
this
in
kind
of
enough
detail,
if
you
understand,
but
basically
GitHub
Runner,
it's
it's
an
agent
that
will
do
the
work
right
so
when
the
pipeline
is
triggered
from
from
the
left
side
to
the
right.
A
We're
looking
at
this
kind
of
infographic
about
the
trigger
is
made
directly
to
the
server
or
when
you
put
from
your
local
to
the
server
right.
Local
equipment
do
not
trigger
CI
pipeline.
So
then
doing
this
cyber
point.
We
see
that
you
get
that
integration
paper
happening
there
might
be
half
or
dynamic
applications.
Security
scanning
is
done
and
at
the
end
we
see
during
the
review
of
the
Union
production.
A
A
Apologies,
so
guitar
safely
performs
the
ball
with
that
automatically
right.
It
do
your
application,
it
runs.
You
need
an
integration
paths.
It
looks
at
the
live
review
of
your
development
Branch,
with
review
apps
Point
number
three
on
the
picture
and
then
deploys
to
multiple
environments
and
like
staging
my
production.
A
The
slide
is
kind
of
covered.
Now
we
can
talk
about
the
main
concept
inside
the
pipeline
right.
So,
let's
start
with
jobs
right
job
defined.
What
we
want
to
accomplish
in
our
point
fine,
for
example,
job
that
complete
or
Tech
code
and
stages
would
Define
when
or
how
to
run
those
draw.
For
example,
they
just
don't
run
tracks
of
the
pages
that
compile
the
code
by
default.
That
pipeline
will
have
three
stage
and
therefore,
usually
build
tests
and
deploy.
A
I
think
you've
got
no
job
will
simply
be
more
as
well.
So,
let's
kind
of
discuss
this
I
suppose
they'll
be
a
screenshot
below
that
you're.
Seeing
here
this
is
a
kind
of
not
a
typical
pipeline,
but
just
an
example
where
we
can
discuss
the
build
stage
where
the
application
has
been
built,
and
during
the
past
stage
we
see
the
open
number
testing
that
is
happening
at
duration
unit
yeah.
A
Then
it
is
before
the
staging
and
then
a
part
of
primary
deployment,
then
pushed
into
production
so
job
that
I
executed
by
Runners
right
and
multiple
job
in
the
same
stage
are
executed
in
parallel
and
if
enough,
current
Runners
are
available.
So
if
all
the
jobs
are
not
they
each
exceed
the
pipeline
was
on
to
the
next
stage.
A
Any
job
in
a
stage
fails.
The
next
stage
is
usually
not
executed
in
pipelines
and
Pipeline
and
early
in
general,
a
pipelines
are
included
automatically
and
require
no
intervention
once
created.
However,
there
are
also
times
when
you
can
manually
interact
with
that
point.
Depending
on
how
you
address
up.
A
A
Now,
let's
talk
actually
a
little
bit
about
the
CI
in
TDS
setup.
This
is
going
to
get
a
little
bit
more
technical
button,
not
a
whole
lot
as
well,
I
promise.
So
what
we
see
here
on
left
hand
side,
we
are
seeing
dot.
Gitlab
ciao
have
example
right,
and
the
ammo
file
provides
the
instructions
for
pipeline
it's
located
in
the
directory
of
the
project
repository
and
it
covers
the
stages
of
the
job
or
in
each
section.
What
we're
seeing
here.
A
So
it's
a
very
basic
example
of
the
file,
obviously,
which
is
written
in
yaml
syntax
in
like
a
third
noodle
project
in
a
full
reversion
control,
along
with
the
rest
of
your
code
in
GitHub
in
Block
guitar
file,
you
can
Define
the
scripts.
You
want
to
write
a
configuration
files
and
templates.
A
But
this
file
has
just
a
few
section
by
the
jobs
and
stages
in
a
pipeline.
So
I
thought
let's
take
a
look
at
every
single
one
of
them,
so
the
first,
the
first
part
here.
You
should
see
kind
of
right
highlight
over
there,
but
this
section
defines
the
station
for
the
pipeline.
Here
you
can
see
they
are
specified
and
build
and
deployed.
A
Then
we
have
a
variable
in
between
example.com
now,
the
second
part
where
the
section
represents
build
job.
You
can
see
that
the
page
is
defined
and
built
followed
by
the
script
of
the
jaw
and
an
only
payment
I3.
The
section
represents
deploy
job.
You
can
see
that
the
stages
that
have
either
deployed
and
they're
also
environment
variables
and
only
statement
included
for
the
job,
we're
going
to
discuss
all
those
additional
statements
and
slightly
ahead.
A
There
are
many
other
questions
and
types
of
contents.
You
can
include
in
that
video
file
and
with
fourth,
obviously
we're
going
to
be
discussing
the
very
basic
ones
and
what
we
have
expensive
implementation
if
you
want
to
utilize
more
technical
models
as
well,
so
everything
that
you
see
here
from
the
image
all
the
way
to
when
there's
a
cancellation,
those
configurations
have
several
different
references
and
obviously,
if
you're
looking
at
the
rewards
that
are
used
in
a
yaml
file
on
our
dot
website.
A
So
all
that
we
are
going
to
touch
on
right
now
so
again,
a
little
bit
more
around
stages,
let's
go
kind
of
going
to
find
the
concept
that
they
just
accept
for
a
job
with
logical
faction
and
while
jobs
to
form
the
task
so
by
default.
There's
four
stages
in
this
example
is:
do
test
reviewing
the
point
and
you
can
use
the
stage
to
Define,
which
stage
a
job
runs
in,
and
jobs
of
the
same
page
I'd
be
good
in
parallel,
subject
to
certain
conditions.
A
Right,
like
I,
said
they
do
separate
jobs
in
The
Logical
section
in
a
while
job
is
performed.
Talk
about
applying
configuration
obviously
will
begin
with
a
job,
and
jobs
are
the
most
fundamental
element
of
cim
or
file
and
the
yaml
file
trigger
scripts,
which
will
do
the
work
in
order
to
create
the
first
pipeline.
You
can
start
with
whatever
build.
You
have
a
deploy
command,
which
you
currently
use
right
now,
if
you
are
right.
A
Jobs
are
defined
with
constraints
stating
on
their
what
condition
they
should
be
executed,
top
level
elements
with
an
aperture
name,
and
they
must
contain
a
fifth
script.
Clause
they're
not
limited
in
how
many
they
can
be
found
right
and
the
script
towards
it
only
required
keyword
that
a
job
need
executed
by
the
one.
A
So
those
are
the
basic
parameters
that
you
would
have
as
an
example
as
well.
A
Now,
let's
talk
about
an
image
right.
The
image
keyword
is
the
name
of
the
docker
image
that
Docker
executor
uses
to
run
the
entity
job.
So
by
default
the
executor
posts
images
from
Docker
hub.
However,
you
can
configure
the
registry
location,
you
know,
I,
guess
a
lot
broader,
but
I
think
yeah.
Okay,
sorry
now
images
of
this,
like
I,
said
a
pull
from
Docker
Hub.
A
By
default,
you
can
use
a
public
email,
unlocking
by
PC
image
will
be
0.3
or
you
can
also
use
the
cut
images
and
it
can
also
be
stored
in
a
GitHub
container
registry.
As
an
example,
you
can
ask
the
ICD
jobs
anywhere
or
whatever
you
would
want
and
easily
repeatable
reliable
environment,
but
basically
to
achieve
it
with
compare
English
within
a
global
scope
or
inside
your
job
definition
on
the
local
image
or
in
a
local
store.
A
Image
with
additional
functionality
right
here,
we're
calling
the
password
layer
from
our
database
there
is
for
base
image.
There
is
going
to
be
used
in
global
in
a
local
as
the
image
key
award
here.
Is
this
simple
additional
image
from
Docker
hub
and
can
also
be
pulled?
Something
in
the
industry
which
are
away
variables,
are
Global
and
local
well
and
allow
us
to
Define
gamma
wire
s
and
have
an
order
in
the
viable
hierarchy?
Well,
variables
can
be
defined
also
in
GitHub
itself.
A
You
should
go
to
your
project
if
I
remember
correctly
as
settings.
Yes,
the
variable
and
yeah.
You
can
also
put
variables
after
the
images
or
historical
infection
CC
on
everybody,
services
and
variables.
A
So
so
far,
let's
see
what's
included
in
our
yaml
file.
So
now,
at
the
very
top
we
see
image
but
we're
using
activity
related
container.
A
Now
we
have
additional
Services,
which
is
all
graphs
all
graphs
they
just
we
are
free
with
one
job
and
deploy
code,
both
the
code
part
of
the
deploy
page,
as
you
can
see,
we're
setting
all
configurations
in
one
file
yeah-
and
this
is
a
very
basic
example.
A
Let's
talk
about
environments,
environments
describe
where
code
is
deployed
so
each
time
a
guitar
version,
both
the
environment,
a
deployment
is
created
and
the
environment
keyboard
defines
where
the
app
and
deployed
and
it's
defined
by
three
key
requirements
which
I
I
guess.
You
know
at
that
point
already
know,
which
is
the
name
URL
and
one.
A
Oh
I
suppose,
let's
say
we
want
to
deploy
changes,
but
all
all
branches
but
may
try
to
be
extra
safe.
So
we
can
do
this
with
only
and
accept
payment
right.
We
hear
on
left
hand
side,
basically
we're
saying
deployed
to
all
branches.
Is
that
making?
If
you
see
in
the
middle,
you
have
only
right.
Just
accept
me,
that's
what
I'm,
referring
to
here.
A
Obviously
we
released
An
approved,
ruled
syntax.
That
is
a
lot
more
powerful
and
then
on
the
NXX
payment,
but
we
might
still
be
seeing
this,
but
what
only
does
is
the
name
of
the
branch
they
execute
on.
So
in
that
case,
all
branches
like
that
branches
not
to
execute
on
it's
all
branches,
except
for
main
branch.
So
there
will
see
many
advantages
which
are
possible.
I
would
refer
you
again
to
our
technical
documentation.
A
A
So,
in
this
case,
rules
are
a
great
option,
so,
as
you
can
see
in
the
rule
section
in
this
example
in
the
middle,
so
we're
showing
the
same
rule
I've
applied
before,
but
this
time
would
rule
instead
of
only
that
side
rule
that
evaluate
in
order
until
the
first
match
when
matched
the
job
is
either
included
or
excluded
from
the
pipeline,
depending
on
the
configuration
form,
if
included
the
job,
all
the
hardware
attribute
added
to
it.
A
So
we
cover
a
lot
more
of
this
in
our
Advanced
Workshop.
We
can
register
as
well
but
I
think
at
this
point.
That
would
be
hope.
This
works
now,
the
before
and
after
script
awards
that
can
be
used
for
healthkeeping
right
before
script
runs
build
environment
set
up
so
after
people
don't
build
environments
clean
up
as
an
example.
A
This
is
only
less
than
three
institutions
where
you're,
not
using
continuation
so
before
screen
towards
the
use
to
define
an
array
of
commands
that
should
run
before
each
job
but
after
artifacts
are
restored.
A
A
A
A
A
If
you
use
cache
in
artifact
to
store
the
same
path
in
your
job,
the
cashmere
might
be
all
written
because
caches
are
restored
before
artifact.
A
A
So,
let's
take
a
look
at
what
our
gitlab
CI,
the
Gamma
1
looks
like
so
far,
so
it's
called
build.
It
stage
build.
We
have
a
script
command,
build
only
domain
and
artifact
only
paid
on
success,
and
we
have
a
part
bin
Target
so
point
we
have
added
passion
Architects
after
that
about
now.
Let's
talk
about
time
in
GitHub,
we
use
hacks
this
next
specific
Runner
right.
Remember
it's
an
agent
that
doesn't
work
we're
going
to
cover
slide
later
from
the
list
of
all
Runners
that
are
available
per
project.
A
When
you
register
Runner,
you
can
specify
the
runner
time,
for
example,
Ruby
program,
postgres
development
and,
and
he
likes
the
icons-
are
not
the
same
as
a
guitar
I
think
that's
the
items
associated
with
the
runners
and
good
times
are
associated
with
marketing
a
specific
units
right
if
that
was
confusing,
let
me
repeat
that
again,
a
good
laps,
yeah
I
thought
I'm,
not
the
theme
are
associated
with
Runner
and
get
down
are
associated
with
our
marking.
A
specific
document
so
in
this
example
only
execute
the
job
on
Runners
with
Ruby
and
math
fund.
A
So
now
we've
added
that
tag
to
our
file
in
in
a
minute
that
you
see
here,
paragraph
or
ethics
and
iOS.
A
So
if
you
think
of
GitHub
file
as
instructions
for
your
job,
you
can
think
of
GitHub
Runner
as
the
agent
but
runs
the
ultra.
It
doesn't
work
basically
right.
So
in
order
to
use
GitHub
yourself
for
your
GitHub
administrator,
that's
for
Define
a
pipeline
within
the
Yahoo
file
called
a
bucket
La
yeah
and
then
install
and
configure
GitHub
Runner.
A
A
You
can
think
of,
for
example,
of
the
brains
and
Runner
as
the
body
right
and
a
guitar
Runner
is
an
application
agent
written
in
gold
and
will
run
job
specified
in
the
ammo
file.
Using
an
API
to
communicate
with
GitHub
you'll
get
up
administrator
can
configure
should
run
as
wrong
all
the
project
or
you
can
set
up
the
neuron
project
a
little
bit
about
running
architecture,
Runners
connect
to
a
gitlab
server
and
simply
ask
hey:
is
there
any
work
to
do?
If
there
is
they're
going
to
do
it?
A
Performance
could
be
installed
anywhere.
Where
you
can
build
gold
buyers,
they
could
be
installed,
Linux,
kubernetes
Docker.
What
have
you
look
at
that
Runner?
Is
it
lightweight
highly
scalable
agents
that
are
fixed
up
by
CI
job
through
the
corner
coordinator,
API
of
gitlab
cintd,
which
will
then
run
the
job
and
send
their
note
back
to
gitlab
instance
right?
A
What
can
it
be
installed
limit,
macquest,
Windows,
FreeBSD,
bare
metal,
europation,
Docker,
all
those
places
the
club
Runner
can
also
pick
any
programming
languages,
including
Java,
python,
C,
HP
and
many
other,
and
these
are
typically
created
by
your
admins
and
made
visible
and
GitHub
UI
for
certain
tasks
and
job
referring
to
the
Run
themselves
in
terms
of
Runners.
We
know
what
they
are
now,
but
they
also
can
be
something
they
can
be
assured
or
specific,
photographer
and
Target
or
protected.
A
So
assured,
Runners
are
available
to
all
groups
and
projects
in
a
gitlab
instance
to
the
ground
are
associated
with
specific
projects.
I
typically
want
project.
At
a
time
group
products
are
available
to
All
by
direct
enzyme
groups.
In
a
group.
Now,
let's
discuss
shared
and
versus
specific
children
is
available
to
every
project
that
make
it
loud,
instant
or
you
can
use
shade
Runners
when
you
multiple
job
with
similar
requirements,
rather
than
having
multiple
Runners
idling
for
many
projects,
you
can
have
a
few
Runners
that
handle
a
multiple
project.
A
This
process,
you're,
probably
using
a
fair
usage
queue.
You
prevents
project
from
creating
hundreds
of
jobs
and
using
all
available
shade,
Runner
resources.
So
the
fair
usage
to
algorithm
then
I
find
the
job
based
on
the
projects
that
have
the
fewest
number
of
jobs
already
running
on
a
shared
Runner
right.
So
the
last
I
guess
that
particular
project
is
performing
work.
We'll
have
the
warrant
list
will
be
assigned
to
it
kind
of
makes
sense
the
specific
runners
they
do
it.
A
When
you
want
to
run
us,
you
know
to
perform
to
be
working
on
specific
projects.
Actually,
for
example,
when
you
have
job
specific
requirements
like
I,
deploy
a
job
that
requires
credentials
or
projects
with
a
lot
of
CI
activity
that
can
benefit
from
being
separate
from
other
runners,
and
you
can
set
up
a
specific
partner
to
be
used
by
both
a
project
right.
A
Sometimes
you
have
very
specific
Runners.
You
know,
let's
say
windows
for
testing
a
Windows
build
right
and
targets
are
used
to
ensure
that
the
correct
Runner
is
working
on
a
current
job
next
and
you
can
use
Tag
to
ensure
that
each
job
uses
the
correct
Runner
specifically.
A
So
what
targets
do
they
allow
to
lock
it
up
to
select
a
runner
from
a
pooling
algorithm
right
attack?
Runner
will
only
be
selected
the
wrong
job,
but
with
a
specific
Cloud
right.
My
quest,
my
quest
work.
A
A
I'm
not
sure
it'll
be
more
updated
right
or
not,
though
more
now,
okay,
right
so
executors.
So
this
is
last
couple
of
slides
that
are
left
and
Runners
Implement
number
of
executes
that
can
be
used
around
your
build
in
different
scenarios.
The
executor
provides
dependency
is
where
you
build
and
that
will
be
installed
in
the
environment
required
for
GitHub
Runner,
okay,
sub
run.
A
It
can
be
configured
with
multiple
execute
environments,
depending
on
how
you
want
your
Runner
to
carry
out
Construction,
the
executors,
allow
you
to
specify
a
urine
activation
environments,
for
example,
when
the
GitHub
Runner
does
not
provide
an
Executor.
For
example,
LX
containers
you're
able
to
provide
your
own
execute
both
the
GitHub
Runner,
the
provision
and
clean
and
clean
up
any
environments.
You
want
to
use
there's
two
more
common
Executives,
shell
and
docker.
A
Shell
is
the
most
basic,
which
means
whatever
the
runner
has
available
in
its
environment
is
what
it
can
actually
do.
Execute
Pepsi,
pbda,
dot,
machine
shell
and
over
all
those
examples.
Are
there
now
as
well
executed
a
little
bit
common
will
be
able
to
walk
parallel
platform
on
top
of
virtualbox
same
thing.
In
this
page,
so
right
at
this
point,
I
think
that
really
brings
us
up
to
the
end
of
it.
A
In
other
summary,
I
wanted
to
mention
that
if
you
want,
if
you'd
like
this
type
of
learning,
there's
a
link
there
and
you
can
step
updated
more
webinars,
we
run
them
every
month
with
a
lot
of
them
and
Us
hours.
It
is
a
kind
of
summary.
We
cover
the
foundational,
beginner
concept
and
usage
European.
Hopefully
it
was
beneficial.
A
We
do
work
on
feedback,
so
please
reach
out,
add
it
to
myself
or
leave
your
feedback
in
the
job
that
we
know
where
you
know
this
special
review,
where
it
was
too
fast
or
too
small,
or
maybe
you
want
initial
content
for
this
type
of
question
right,
keep
in
mind,
it
is
an
introduction
to
the
cncd.
So
maybe
there
was
a
bit
of
repetition,
but
yeah
now
I
think
we're
going
to
get
the
Q
a
parts
and
we're
going
to
take
some
questions.
So
thank
you.
A
Right
so
I'm
just
going
to
answer
a
couple
questions
that
the
the
previous
recording
I
think
as
I
said
before,
has
been
sent
already-
probably
yeah.
A
Hopefully
the
voice
is,
you
know,
has
been
a
little
bit
better
now.
A
A
A
A
So
just
give
me
a
second
here:
I'm
just
going
to
pause.
The
screen
sharing
and
yeah
you're
gonna
get
the
answer.
Any
questions
in
a
moment.
A
So,
thank
you.
Everyone
I
think
at
this
point
we
are
going
to
answer
all
the
questions
and
hopefully
send
them
out
to
all
the
attendees
after
the
session.
So
hopefully
you
found
the
session
useful.
At
this
point.
We
are
going
to
wrap
this
up
and
apologies
for
the
problems
with
the
voice
and
yeah.
Thank
you.
So
much
for
attending.