►
Description
Speed run describing the use of the Configure multiple image pull policies for Docker executor feature that shipped in GitLab Runner 13.8.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26558
A
The
diagram
here
is
just
a
quick
depiction
of
the
environment
that
I'm
using
for
this.
For
the
speedrun,
I
have
a
github
runner
hosted
on
a
dedicated
virtual
machine.
That's
in
gcp
and
over
here
on
the
right
hand,
side
there's
a
dedicated
gitlab
instance
also
hosted
in
jcp
as
well.
So
the
runner
that
we'll
be
using
in
the
speedrunner
will
be
communicating
to
a
project
hosted
on
this
dedicated
github.
A
So
over
here,
I've
already
logged
in
to
my
instance
and
I've
opened
up
the
config.tumor
file
and
you'll
see
here
that
in
this
particular
section
I
actually
have
multiple
runners
sections
configured
in
this
oneconfigure.com
file.
The
section
we're
interested
in
is
right
here.
The
name
of
the
the
runner
in
question
is
test
docker,
dashboard
policy
and
the
configuration
change
of
saying
that
we're
we
now
have
a
part
of
click
net.
Eight
is
the
ability
here
in
our
c
and
pull
policy,
to
define
these
multiple
values
and
this
example.
A
We
have
always
is
one
value,
and
then
we
have,
if
not
present,
as
the
other
value
so
going
over
here,
take
a
look
at
running
a
pipeline
with
that
this
particular
project
already
has
been
set
up
and
configured
to
connect
to
that
runner.
It's
going
to
run
a
pipeline
in
the
show
and
in
real
time
in
the
execution
of
that
job,
using
the
new
co-policy.
A
A
So,
if
you're
interested
in
taking
a
look
at
just
testing
this
out
yourself,
the
related
knowledge
requests
which
is
associated
to
the
to
the
issue,
2658
steve,
who
is
the
developer
that
created
the
first
plc
on
this,
actually
has
a
very
nice
write-up
here.
That
shows
you
how
to
test
this
yourselves
very
quickly,
exactly
where
the
piling
right
following
setting
up
the
speed
run.
So
there
you
have
it.
That's
the
the
new
feature.