►
From YouTube: GitLab 15.1 Kickoff - Verify:Runner
Description
15.1 Kickoff video for the GitLab Runner Group
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28861
A
Hi
everyone
darren
eastman
here,
product
manager
for
get
lab
runner.
This
is
the
gitlab
runner,
1501
kickoff,
video,
typically
gina
doll.
Our
designer
for
the
gitlab
running
team
is
with
me
on
these
videos.
Unfortunate
issues
are
ill
this
week
get
well
soon
here
so
on.
The
screen
is
the
1501
runner
group
iteration
plan.
A
If
you
go
to
this
issue,
you
will
see
that
we
have
this
plan
segmented
by
the
three
categories
that
comprise
the
runner
group,
and
so
in
here,
you'll
see
you're,
going
to
call
represented,
run
a
sas
as
well
as
run
the
fleet,
and
this
matches
our
direction
pages.
A
few
months
ago,
we
segmented
our
direction
pages
on
about.gitlab.com,
so
that
now
there
are
specific
direction
pages
for
each
of
these
categories.
A
One
of
the
which
is
around
the
management
of
runners
for
those
companies
or
those
customers
and
users
that
self-manage
what
we
typ.
What
we
refer
to
as
a
freight
or
significant
number
of
runners,
so
switching
gears
are
coming
back
and
speaking
specifically
what
we
work.
What
are
we
working
on
in
15.1
in
the
run
a
core
category,
as
I
mentioned
in
the
past
few
videos,
we
continue
to
focus
a
lot
of
our
investment
dollars
in
reducing
the
the
backlog
of
aged
severity,
2
or
priority
2
bugs.
A
So
that
remains
a
key
focus
from
us
from
a
product
perspective,
as
well
as
an
engineering
perspective,
is
reducing
the
backlog
of
those
wealth
in
the
core
on
the
code
base
itself.
So
if
you
go
to
this
issue
right
now,
you'll
notice
there's
quite
a
few
items
in
the
list.
By
the
time
we
formally
kick
off
the
development
effort
for
15.1,
we'll
likely
pair
this
list
down,
and
the
key
message
here
again
is
that
we're
really
trying
to
focus
on
prioritization
of
reducing
this
age
belt
backlog
in
terms
of
new
features.
A
I
want
to
call
your
attention
to
this
one
specific
new
feature
that
we
are
very
super
excited
about,
working
on
and
trying
to
deliver
an
mvc
for
n151,
and
that
feature
is
actually
in
support,
gitlab's
supply
chain
security
direction
and
strategy,
and
here
I'm
on
the
screen.
Right
now,
I'm
sharing
a
blog
post
that
was
with
my
sam
white.
One
of
the
leaders
is
driving
this
strategy
for
git
lab
and
it's
all
about
solving
the
entrance
client
chain
security
within
the
one
devops
platform
paradigm,
and
so
we
have
a
unique
opposition
position.
A
We
believe
at
github
to
solve
this
in
a
very
efficient
way,
and
so
what
we're?
Looking
at
n1501
specific
to
the
runner,
the
engine
that
executes
a
ci
job
is
the
ability
for
the
runner
to
generate
a
get
that
defined
software
attestation,
aka
metadata
during
job
ci,
job
execution,
and
so
that's
the
first
piece
of
the
puzzle
in
terms
of
establishing
provenance.
A
If
you
will,
in
terms
of
the
entire
software
development
life
cycle
or
the
entire
build
lifecycle,
and
so
this
is
a
key
thing
that
we
need
to
get
to
as
part
of
one
of
the
foundational
elements
to
enable
this
broader
vision
that
sound
highlighted
here.
In
terms
of
where
we
see
github's
github,
going
from
a
supply
chain,
security
directions,
point
of
view.
A
So
that's
it
for
ronald
paul.
If
we
run
assassin
1501
most
of
our
efforts
will
be
focused
on
maintenance
and
tech
that
worked
related
to
making
sure
that
the
gitlab.com
platform
is
healthy.
We
do
have
a
stretch
goal
in
terms
of
some
new
features
and
capabilities
that
we
might
hope
to
get
to.
But
it's
too
a
bit
too
soon
to
specifically
chat
about
those
we'll
see
how
things
go
as
we
start
executing
on
the
maintenance
world,
that's
required
for
gitlab.com
and
1591.
A
So,
right
now
for
an
assassin,
our
main
focus
1591
is
it's
a
maintenance
detected
efforts
that
we
need
to
to
get
to
to
ensure
the
continued
health
and
reliability
of
our
sas
platform
and
wonderfully
quite
a
number
of
as
the
run
of
18.
By
the
way,
just
a
quick
call
out
they've
been
doing
phenomenal
work
over
the
past
six
to
nine
months,
just
delivering
new
features
and
capabilities
across
the
admin
ui
experience
across
the
group
ui
experience
very
recently,
we
merged
capability
sets.
A
So
now
the
group
views
are
aligned
with
the
admin
views
and
that
kind
of
sort
of
like
very
quick
cadence
delivering
of
new
features
is
really
accelerating.
One
of
the
key
things
that
they're
working
on
on
from
that
team
and
1501
is
the
really
interesting
feature
of
giving
admin
users
first,
quick
visibility
in
terms
of
the
ownership
model
for
a
runner,
and
so
that
is
this
feature
here
that
we're
calling
there's
two
species
of
it.
But
I'll
just
go
ahead
and
pop
over
to
the
one
that
has
bone
design.