►
From YouTube: GitLab 16.0: create a GitLab Runner demo
Description
This video provides an overview and demo of the workflow to create a GitLab Runner as of GitLab 16.0. Links mentioned in the video are provided below.
API docs:
- REST: https://docs.gitlab.com/ee/api/users.html#create-a-ci-runner
- GraphQL: https://docs.gitlab.com/ee/api/graphql/reference/#mutationrunnercreate
Feedback issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/387993
Next Runner Token Architecture:
https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/#next-gitlab-runner-token-architecture
A
Hey
everyone
Dion
Eastman,
here,
I'm
joined
with
Pedro
and
Regina,
and
today
we're
going
to
cover
the
new
Runner
creation
flow
and
getlab
is
coming
on
16.0
and
Gina
and
Pedro
also
do
a
demo
of
a
new
creation
Pro
as
well.
So,
let's
put
it
I'm
just
going
to
share
my
screen
and
I'll,
give
it
a
quick
overview,
a
bit
of
background
in
terms
of
what
we've
been
doing
since
we
last
met.
A
Let's
see
if
we
can
get
a
slideshow
thing
to
look
actually,
probably
not
because
every
time
I
do
slideshows
and
zoom
I
I
can
never
tell
you
how
to
get
out
of
the
sideshow.
So
anyway,
today
we'll
cover
the
new
running
creation
school.
That's
coming
in
16.0!
This
is
a
quick
background.
It's
basically
a
new
workflow
for
creating
a
runner
by
authorized
users
and
get
that
instances
and
replaces
the
previous
workflow
that
used
and
always
available,
always
visible
registration
token.
A
Actually,
we
started
masking
it
a
few,
a
few
releases
back,
but
it
always
available
registration
token,
that
is,
scope
to
an
instance
level,
a
group
or
project,
and
you
can
see
a
nice
little
diagram
here
that
Jimmy
put
together.
That
kind
of
shows
the
the
current
the
the
Legacy
registration
process
flow,
so
just
kind
of
quick
comparing
the
the
sort
of
the
legs,
the
registration,
Pro
method
with
the
new
process
and
the
new
in
the
registration
in
the
old
method,
you're
just
basically
going
to
the
UI.
A
A
So
if
you
have
workflows
or
use
cases
where
the
reviews
of
the
auth
token
or
the
reviews
of
the
runner
configuration
I
should
say
to
be
more
specific
is
warranted.
That
is
supported
with
the
new
method
and
I
think
Pedro,
amigo,
I'm,
sorry,
Miguel
Gina
will
touch
a
bit
more
about
that
as
they
go
through
the
demo.
A
The
other
thing
that
also
I
want
to
call
in
terms
of
the
new
process.
The
generated
authentication
token
is
only
visible
once
in
the
UI.
So
as
you're
going
through
the
workflow
you'll
see
that
in
a
demo,
once
you
go
through
the
creation
step,
the
token
is
that
split
at
the
end
is
only
visible
once
in
the
UI.
So
for
now
you
have
to
copy
the
registration
token
string
to
register
running.
A
You
know
and
check
that
get
repository
out
run
scripts
Etc.
So
you
want
to
make
sure
that
your
authentication
token
is
stored
in
a
super
location,
so
secure
sort
of
location
and
so
forth,
and
then
for
automation.
You
can
use
the
API
to
generate
an
auth
token.
That's
go
to
the
instance
group
of
project
I.
Think
page.
You
want
to
make
a
point
about
the
API
So.
B
Currently
we
in
the
old
registration
methods,
we
expose
an
API
that
allows
you
to
register
or
create
a
runner,
and
typically
people
do
this
before
executing
a
job.
They
will
create
a
runner
ad
hoc
with
a
given
configuration
and
receive
an
authentication
token
and
and
use
that
for
the
for
running
the
the
job.
So
the
difference
is
that
in
the
new
methods,
you
would
create
the
the
configuration
in
in
the
UI.
B
So
this
removes
the
needs
lots
of
times
to
use
the
rest
API
to
to
interact
with
gitlab
in
order
to
have
access
to
a
runner.
You
just
have
to
know
the
the
authentication
token
we
still
have
the
ability
to
create
new
Runners
through
a
rest,
API
or
graphql
endpoint
graphql
mutation,
depending
on
your
your
preference,
but
that
should
be
less
often
needed
to
restart
into
that.
It's
only
needed
if
you
need
ad
hoc
configurations,
so
you
you
would
in
a
situation
where
you
don't
know
upfront.
B
What
tags
will
be
needed,
or
other
configurations
like
that
that
are
decided
at
creation
time?
Then
you
would
resort
to
those
apis
and
we
can
link
at
the
end
of
the
the
video
you
know
on
the
notes
we
can
put
the
the
links
up
to
to
those
apis
so
yeah.
That's
the
callouts
I
wanted
to
make
thanks
awesome.
A
Thanks
Pedro
I
just
wrap
up
the
slide,
so
we
can
get
into
a
demo
in
terms
of
the
the
status
of
the
feature.
So
the
new
creation
workflows
for
the
admin
areas
equipment
projects-
that's
going
to
be
available
as
of
your
gitlab
16.0
version
as
shipping
here
in
a
couple
of
days
and
and
they
get
a
call
out
to
make-
is
that
we
are
planning
to
completely
remove
the
Legacy
registration,
token
method
from
gitlab
and
gitlab
17
at
all,
which
is
next
year.
So
the
new
creation.
A
A
B
A
Got
it
so
it's
kind
of
a
nice
mechanism
for
folks
to
test
out
a
new
application
flow
and
if
you
wanted
to
always
go
back
and
work
out
things
with
the
Automation
and
that
sort
of
thing
hey,
that's
a
good
call
out
Pedro.
Thank
you.
Okay,
I'm,
going
to
stop,
sharing
and
pass
it
over
to
I.
Think
Gina
you're
going
to
do
the
demo.
C
C
And
here
you'll
see
a
couple
things
up:
top
is
you'll
see
a
message
to
provide
feedback
about
this
new
flow.
We're
really
looking
forward
to
hearing
what
you
think
about
it.
If
you
don't
want
to
see
it,
you
can
dismiss
it
and
it
will
never
be
seen
again
and
then
we
also
have.
This
alert
basically
is
saying
exactly
what
Darren
was
saying
about
when
we
deprecate
the
old
registration
process
and
we
link
you
to
gitlab
Runner
160,
just
to
see
the
release
notes
there.
C
So
you
can
learn
more
if
you
need
it
further
information,
but
I'm
gonna
delete
that
as
well,
and
so
my
first
thing
that
I'm
picking
here
is
a
platform
to
create
the
runner
on
and
for
my
instance,
I'm
just
going
to
do
Mac
OS
I'm
downloading
it
on
my
operating
system,
my
current
MAC
and
then
these
details
are
optional
but
you're.
Welcome
to
I
know
a
lot
of
us
use,
Runner
descriptions
to
identify
Runners.
C
C
You'll
see
here
is
the
runner
token,
which
Darren
also
mentioned
that
it
only
shows
in
the
UI
once
so.
If
you're
going
to
copy
it
make
sure
to
store
it
in
a
very
secure
location.
Otherwise,
if
you
don't
need
it
again,
then
you
don't
have
to
copy
it
and
then
I've
already
choose
chosen
an
Executor,
but
we've
heard
that
sometimes
it's
difficult
to
choose
those
because
you're
not
sure
which,
which
one
to
choose
basically.
C
So
we
do
link
out
to
documentation
that
gives
a
really
great
table
of
which
one
to
use
it
for
which
scenarios
and
then
the
last
step
here
it
is
optional,
depending
on
how
you've
set
up
your
runner
system.
But
for
me,
I
need
to
run
this
command
for
the
runner
to
be
available
to
run
jobs.
So
I'm
going
to
run,
gitlab
runner
run.
C
And
I
see
this
message
so
I'm
going
to
clone.
Stop
that
so
now,
I've
gotten
a
success
message
that
I've
created
a
new
Runner
I'm,
going
to
go
back
to
the
runners
page
and
I
should
see
my
new
Runner
back
at
this
page
yep
there
it
is,
and
it's
online
and
then
per
usual.
You
can
click
into
it
and
see
details
and
jobs
from
there.
C
This
gift
is
going
pretty
fast,
but
you'll
be
able
to
see
how
many
are
in
a
group.
And
then,
when
you
click
into
the
runner,
you'll
be
able
to
see
the
details
of
those
like
the
status
system,
ID
version
Etc
and
then
also
the
jobs
that
each
one
of
those
system
IDs
have
run.
We
call
them
Runner
managers,
but
each
one
has
its
unique
system
ID,
which
is
how
we
tell
them
apart
and
I
will
stop
sharing
now.
C
Yes,
great
Point,
okay,
so
in
all
of
your
in
all
the
views
you'll
see
this
Kebab
button
and
it
shows
still
the
registration
token
that
you
can
use
to
register
in
the
old
method,
as
well
as
their
old
registration
instructions
in
that
modal.
So
you
can
still
just
copy
this
single
command
and
run
it
here.
I'll!
Do
it
just
for
this.
C
Right
and
then
so,
you
also
get
this
warning
message
that
says
that
the
support
for
registration
tokens
will
it's
deprecated
and
will
be
removed
in
170,
like
theater
was
saying
so
in
this
case,
when
I
refresh
this.
It
actually
should
show
me
this.
This
Runner
yep
didn't
contact,
because
I
have
to
run
that
but
anyways.
C
A
A
Well
folks,
as
Junior
and
Petra
said,
we'll
link
on
when
we
post
a
video
to
get
that
filter,
We'll,
add
some
links
and
maybe
the
feedback
issues,
maybe
they're
epics.
So
if
you
have
any
questions
about
a
new
flow,
whether
it's
automation,
questions,
timing,
usability,
just
go
ahead
and-
and
you
know
ping
us
on
the
on
the
feedback
issue-
we'd
love
to
hear
your
comments
as
we
continue
to
evalness
I'm
gdm
Pages.
Thank
you
so
much
for
joining
me
on
the
demo
on
the
great
book
and
getting
us
to
the
statuses.