►
From YouTube: GitLab 12.10 Kickoff - Verify:Runner
Description
GitLab 12.10 release milestone kickoff video for GitLab Runner.
A
Hello,
everyone
Danny's
meeting
a
proud
man
to
forget
that
runner
today,
I'm
going
to
spend
a
few
minutes
reviewing
a
few
of
the
key
issues
that
we
were
looking
to
deliver
and
the
1201
zero
release
and
total
one
zero
we're
investing
quite
a
bit
of
time
working
to
resolve
a
number
of
high-priority
P,
2
bucks,
the
first
of
which
is
issue
number
one.
Three,
seven,
nine,
this
Bob,
who
uses
of
get
lab
Runner
results
an
error,
no
such
file
directory
for
approximately
one
in
ten
bills.
A
At
the
moment,
there's
an
active
community
merger
quest,
merge,
request,
number
193
for
that
one
implemented
well
introducing
new
environment
variable
get
my
underscore
Runner
underscore
disable
underscore
scale
that
will
be
set
to
true
when
your
insulin
get
that
one
from
a
package.
This
will
also
create
a
get
them
when
they
use
a
home
directory
without
the
files
instead
of
inside
a
scale
with
this
implemented.
This
removes
all
this
long
standing
above
the
other
Picchu
brother.
One
enjoy
your
attention
today
that
we're
looking
to
deliver
in
12.10.
It's
issue
number
four,
three
to
seven
dr.
A
config
already
in
use
my
container.
This
is
the
Bob,
where
I
get
that
bonus
running
the
same
job
multiple
times
get
in
the
panic
conflicts
but
container
names.
The
results
in
an
error
and
the
original
via
the
container
name,
is
already
in
use
by
another
container
ID.
At
the
moment,
there
is
a
binary
package
for
the
active,
merge
request
and
our
number
one
eight
zero
one.
A
So
if
you're
interested
in
the
preview
release
of
this,
you
can
come
to
amount
more
in
201
and
link
to
the
actual
action
to
the
binary
where
that
fix
is
a
movement
implemented.
Our
goal
is
to
rapid
review
of
this
open,
mr
and
merge
to
fix
in
so
that
we
can
ship
this
file
name
12.10
the
NEX
active
issue
and
bother
promoted
to
resolve
in
1201
zero.
It's
issue
number
three
through
seven
six.
We
hope
the
resolve
is
in
the
past
couple
of
through
these
milestones,
but
there
are
a
number
of
open.
Merge.
A
Request
are
still
under
review
at
the
moment.
So
our
goal
then,
is
to
get
this
wrapped
up
and
release
milestone,
so
we
can
shut
the
fix
in
12
and
0.
So,
just
a
quick
recap:
the
proposal
is
being
implemented,
but
I
relate
a
merge
request,
for
this
particular
bug
is
that,
instead
of
immediately
tuning
the
processes
using
sick
healing,
ignoring
the
results
with
attempt
to
gracefully
shut
down
the
process
by
first
in
the
signature
and
only
after
specific
time
and
duration
has
expired,
ten
minutes
will
be
to
me
the
process
using
sick
kill.
A
This
is
a
little
high
priority
mode
that
we
have
time
to
resolve
in
12.9,
but
unfortunately,
we
weren't
able
to
do
so.
Our
goal
plan
for
12:01
zero
is
to
make
meaningful
progress
towards
implementing
a
solution,
as
I
mentioned
in
previous
release.
Kpop
videos
they
push
it
we
are
trying
to
implement
this
plan
to
take
is
to
implement
a
retry
mechanism.
This
basically
means
that
when
we
try
each
risk
request
sends
in
dr.
A
This
will
allow
us
to
have
a
snapshot
of
the
current
state
if
to
reach
find
mechanism
does
not
completely
solved
above
then,
the
additional
ones
that
we'll
be
able
to
capture
will
provide
the
data
we
need
to
determine
the
root
cause,
of
course,
compare
the
final
fix
so
again,
we'll
implement
a
retry
mechanism
first,
and
hopefully
we
that
we
get
meaningful
progress
towards
getting
final
solution
for
four
four
five
zero.
So,
okay
going
here
again
in
1201
series
to
me
meaningful
progress
or
moving
the
ball
forward
here
so
disappear.
Summarize.
A
We
currently
have
four
very
in-depth
p2
s
to
belt
that
we're
actively
looking
to
resolve
at
12:01
zero.
From
a
future
perspective,
we
have
a
couple
of
features
that
were
swimming
for
attention
to
in
terms
of
new
capabilities
that
we're
learning
to
release
in
12
1
0
in
1259.
You
may
have
known
as
a
human
noticing
over
at
least
some
you
know,
and
they
were
really
supposed
to
12th
at
9.
We
have
reached
the
updated
or
Windows
lifecycle
policy.
A
There
is
not
the
revised
policy
now
such
a
target
time
frame,
but
when
we
will
add
new,
get
not
run
a
help
of
images
that
include
the
latest
Windows
super
version.
Send
me
a
note.
Send
me,
you
know,
China
released
with
into
this
new
policy
net
and
12.10
will
be
adding
support
for
Microsoft
Windows
Server
version
1903.
So
much
semi-annual
China
release
to
beget
that
on
a
project.
A
They
will
feature
a
new
feature
capability
that
we
were
looking
to
an
internal
one.
Zero
I
was
related
to
for
its
issue.
Them
48:43
and
definition
of
the
description
is
run
at
the
script.
People
Anna
javis,
cancel
in
layman's
term.
Wellness
means
is
that
and
gets
up
on
a
13
dunno
will
be
introducing
a
new
stick
and
in
get
WI
there
were
none
able
a
user
to
cancel
a
job
at
any
of
the
stages.
A
This
new
behavior
that
will
interest
in
the
run
and
twelve
that
one
zero
and
then
is
that
if
a
job
is
canceled,
the
runner
will
be
able
to
stop
will
be
list,
will
stop
execution
of
any
before
script,
skirt
or
prior
stages
and
execute
stage
is
defined.
An
actor
script
archive
cash
from
upload
artifacts.
Sorry,
in
this
issue
for
a
four
three
four,
eight
four
three,
it's
precursor
to
us
implementing
in
13,
1
0,
this
new
state.
A
In
the
get
that
mean
you
I,
they
were
gonna
enable
a
user
to
cancel
a
job
at
any
of
the
stages
and,
finally,
in
terms
of
new
capabilities,
I'm,
going
to
call
your
attention
to
you
in
12
and
one
zero
is
then
you'd
be
looking
to
add
even
continuing
an
investigation
more
than
we
did
in
12
that
nine
related
to
a
Polish
I'll
call
support
and
get
that
Mona.
We've
been
looking
to
add
partial
cross,
6
support
for
the
duck
window,
executor
and
hopefully
for
the
show,
executor,
12
and
12
the
1
0.
A
Those
are
main
issues
in
terms
of
new
features
capabilities,
as
well
as
bug
fixes
that
we
will
need
to
deliver
in
1201
0.
As
always,
if
you
have
any
questions
related
to
a
feature
or
above
on
issue,
feel
free
to
tell
me
directly
on
the
issue
in
get
that
understand
me
and
Darren
Eastman.
You
can
also,
of
course,
drop
me
an
email
as
well.
My
name
Bohlander,
says
d
Eastman
and
get
that
done.
Thank
you
and
talk
to
you,
sir.