►
From YouTube: GitLab Runner Open Office Hours - February 13th, 2020
Description
On this call Steve from the runner team reviewed a Community Contribution from Pierre https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/1832
Topics covered involved how the runner interacts with Powershell and Dockerfiles
A
So
welcome
everyone.
This
is
the
second
gate
lab
runner,
open
office
hours
I'm
like
rush
them.
The
engineering
manager
get
lab
for
the
runner
group
and
intern
for
the
testing
group.
So
far
on
our
call,
we
have
three
of
our
back-end
engineers
for
the
runner
Steve
yogi,
Pedro,
Darren
Eastman
has
just
joined
our
product
manager
and
brake
mark
community
team.
B
On
right
now,
I
mean
we've
gotten
I,
think
three
or
four
mrs
come
in
for
the
for
the
hackathon
and
I
think
CP
you've
seen
one
of
those
already
so
appreciate.
Those
coming
in
and
yeah
I
mean
just
excited
about
having
office
hour
coincide
with
the
hackathon
and
I
think
this
just
brings
an
opportunity,
make
it
more
visible
for
more
people,
so
cool.
A
A
If,
barring
any
questions
we'll
do
some
live
code,
review
or
people
do
a
live
code
review,
probably
one
or
two
Amar's,
depending
on
how
much
we
can
get
through
yeah
other
than
that.
Typically,
what
we
do
is
we
do
get
quite
a
lot
of
contributions.
The
hackathon
I
think
has
a
little
bit
of
a
surgeon
that
even
on
top
of
regular-
and
so
we
typically
prioritize
things
based
on
a
three-tiered
priority
scheme.
By
default,
we
call
things
priority,
murray,
sorry,
I'm
gonna
hang
out
weird
I,
think
bait
pages.
Can
you
mute
yeah.
A
So
by
default,
things
come
in
and
we
give
them
a
priority
three.
This
is
just
going
to
work
to
fall
priority.
The
highest
priority
items
are
priority
ones.
We
limit
ourselves
basically
to
three
of
those
at
a
time.
Those
are
usually
end
up
being
quite
large
and
they
kind
of
speak
more
to
our
strategic
product
direction.
Like
things
we
would
add
ourselves
anyway,
but
maybe
thanks
the
community
contribution,
we're
able
to
get
the
code
in
the
quicker
and
then
somewhere
in
the
middle
of
the
p2s,
which
is
basically.
A
B
Yeah
I
see
a
couple
of
like
a
community
members
on
the
call
as
well
like
like
Brian
I'm
here
and
others
like.
If
you
there
are
specific
questions
regarding
how
the
reviews
are
done
or
if
there
are
any
specific
em
ours
that
you
want
Steve
to
kind
of
go
through
sort
of
live
on.
The
call
just
just
let
us
know
like
like,
like,
like
Kelly
I,
said
just
either
put
it
on
chat
or
just
verbalize
their.
Your
comment,
yeah.
D
D
Go
ahead,
yep
I
will
start
sharing
my
screen,
so
the
one
we're
talking
about
this
one
last
time
we
discussed
why
we
might
want
to
have
bash
on
Windows
and
the
possible
solutions
we
can
make
and
the
ideal
solution
with
was
to
have
the
full
kit
version
installed
on
our
helper
image,
and
the
reason
for
that
is
the
full
kit
version
has
a
Bosch
is
left
inside
of
it.
So
I
saw
that
Pierre
already
built
the
image.
D
Luckily,
and
it
seemed
to
be
fine,
but
first
thing
I
like
to
do
is
skim
through
quickly
the
changes
and
see
like
what
it's
doing,
and
things
like
that
so
I
see
first
thing
that
I
see
is
that
we
seem
to
be
removing
the
first
version.
So,
let's
start
from
the
beginning,
we're
removing
the
get
version
from
the
see.
I
am
a
definition
now.
D
Okay,
now
one
thing
that
I
say,
for
example,
I'm,
not
a
big
fan
of
one
merge,
quest
doing
multiple
things:
it's
not
the
reason
for
that.
Sometimes
one
gets
hard
to
review
and
two.
If
something
breaks,
it
gets
weird
and
funky
on
how
to
revert
things.
So
one
thing
I
see,
for
example,
here
we
change
the
get
version
now
for
now.
D
C
E
B
D
D
E
D
C
A
C
D
D
D
D
D
D
C
D
D
C
C
E
D
Person
is
completely
fine
and
having
one
commit
unless
like
make
sense,
to
have
a
second
comment.
For
example,
changing
some
other
file
somewhere
I
think
it
could
get.
History
is
quite
nice.
Every
time
I
merge.
A
a
Ana
mark.
I
always
take
a
look
at
the
comments,
because
I
find
good
comments
very,
very
useful,
and
if
it's
just
a
bunch
of
fixed
comments
from
review
and
things
like
that,
I
always
end
up
squashing.
That
much
because
those
aren't
really
helpful.
Angry.
D
D
D
E
C
C
Yeah
this
this
is
a
metal
package.
There
is
a
dot,
install
package
that
you
can
find
a
little
bit
later.
Yes,
this
one
and
then
you
click
there,
and
then
there
is
a
list
of
file
issues
scroll
a
little
bit
finds
right
and
then
you
can
click
on
yeah.
There
is
a
helper,
so
in
the
helper
there
is
the
how
you
select
different
options.
So
this
is
the
component
that
whistling
43
mean
43
time
for
this
we
fry.
D
C
D
D
There
is
something
I
never
done
before,
like
a
never
actually
a
chocolaty
stuff
out,
that's
one!
So
that's
really
smart!
Thank
you
for
that
I,
wonder
Panthro
or
Georgie.
Do
you
think
we
should
add
some
comment
here
to
specify
where
these
commands
came
from,
or
do
you
think
they're
too
highly
contextual
and
will
get
outdated
very
fast,
I.
A
D
C
E
D
D
So
in
the
future,
like
probably
we'll
come
to
this
in
a
year
or
two
and
I'm
pretty
sure
this
would
be
changed
so
and
even
I
would
also
link
to
the
feed
line
number
because
that's
super
helpful,
and
so
imagine
if
this
file
is
a
hundred
lines
long.
It
would
be
super
helpful,
so
click
on
the
line
number
and
it
will
give
you
just
one
as
well
right.
C
C
C
D
Do
build
it
on
the
CI,
but
I,
don't
think
we
build
it
for
forks.
So,
for
example,
let's
let's
go
on
one
request:
I
have
right
and
the
reason
we
don't
have
it
for
Forks
is
before
Windows
machines
for
only
a
a
internal
thing,
so
it
was
just
two
machines
that
to
run
or
to
manage,
but
since
we
released
when
those
shared
runners
now
we
run
all
the
windows
tests
on
those
windows
share
drives,
but
we
have
not
exposed
that
for
the
forks.
Yet
that's
just
purely.
C
D
Reference
right,
we
actually
do
have
integration
tests
here
in
the
ready
stage
where
we
validity
images,
so
it
should
make
sure
to
run
it.
So
in
this
case,
what
I
would
have
I
would
do
like,
for
example,
I,
don't
have
access
to
a
Windows
1803
image,
apart
from
the
one
we
have
in
C
Drive.
So
what
I
would
do
in
this
case?
I
would
push.
D
D
D
Georgie
and
Patrick:
do
you
have
any
preference
about
this
variables
like
I?
Do
like
them
having
them
under
the
variables
declaration
cuz?
Then
we
just
have
one
place
for
all
the
versions
that
we
install
everywhere.
It
doesn't
matter
if
it's
Windows,
Linux
or
anything
else,
but
I
also
can't
like
this
variable
does
not
need
to
be
available
for
tests
and
things
like
that.
So
I'm,
not
too
sure
about
it.
D
F
D
I
would
remove
it
because
this
comment
seems
like
not
a
smell
to
me,
but,
like
the
reason
we
have
to
put
a
comment
here
is
to
be
clear.
Why
we
have
it
here
right
so
like
if
we
have
to
have
a
comment,
why
we
have
it
here?
It
seems
like.
Oh,
it's
not
really
clear
why
we
do
have
it
here
so
having
it
in
the
global.
It's
just
simple
and
it's
super
clear
to
me
anyways,
but.
E
D
D
Know
I
would
much
rather
stick
to
you
good
version,
because
in
the
future
I
do
what
I
would
like
to
have
a
specific
version,
one
version
to
specify
for
Linux
as
well,
because
that's
what
efficiency
we
have
on
on
our
Alpine
images
right
like
we
do
not
specify
the
kit
version,
whatever
Alpine
provides
that
we
have
to
use
because
good
and
that
so
I
would
prove
this
back
to
to
play
where
it
was
and
have.
The
virus
is
a
single
source
of
truth.
D
D
Get
outdated
very
easily
and
we
would
forget
to
remove
that
comment
when
we
actually
implemented
I
feel
like
comments
like
those
feel
like
they
get
outdated.
We
do
have
some
comments
of
those
in
the
run
our
code
base,
where
we
should
do
this,
but
either
we
actually
did
it
and
forget
to
remove
the
comment
or
two
we
actually
never
did
it
so
yeah,
that's
just
my
opinion.
If
you
have
any
other
opinions,
feel
free
to
say
so,.
D
D
C
D
D
D
C
Actually
I've
done
some
integration
tests
manual
for
artifact
I
didn't
try
to
cash,
but
the
artifact
for
me
was
good
enough
to
make
sure
that
the
help
go.
Executive
order
was
actually
working
from
here.
You
are
testing
from
command,
so
I
was
just
made
sure
that
it
worked
from
the
batch
script
and
I
was
actually
just
surprised
that
everything
went
very
smooth
yeah.
D
The
damper
image
the
stuff
for
doctor
when
those
either
are
manually
tested
or
we
have
very
flaky
tests
on
them.
Well,
we
don't
look
at
at
the
moment.
Unfortunately,
I
do
have
some
requests
that
I
need
to
get
back
to
to
fix
some
of
those
tests,
but
I
just
haven't
had
the
time,
but
so
I
think
these
changes
do
look
good
as
soon
as
we
push
and.
D
C
D
D
The
windows,
people
like
the
kid
for
windows
people
know
that's
what
kid
on
the
first
version
works,
but
what
right
so
we
offload
that
stinking
to
them,
but
then
again
we
do
not
have
control
over
what
version
is
installed,
so
it
might
end
up
until
us
having
some
regressions
or
something
like
that.
So
do
you
think
that
would
be
a
problem?
Do
you
think
we
should
just
take
what
we
have
with
this
merge
request
and
maybe,
if
it
becomes
a
problem
in
the
future,
react
with
a
fix
it.
What
are
your
thoughts,
I
think.
D
So
the
reason
for
that
is
these
are
the
questions
like
I
maintain
our
maintainer
ends
up
asking
every
time
we
change
something
like
a
version
change
or
something
like
that,
because
we
have
to
be
careful
at
the
end
of
the
day
that
things
change
which
we
don't
have
control
over.
So
we
need
to
be
careful
of
what
we
allow
and
what
we
don't
allow
to
change
right
under
our
rock.
So
having
kettle
of
has
no
control
over.
It
might
seem
a
good
move
for
now,
since
the
app
top
seems
like
much
easier.
We.
D
C
C
D
D
So
one
thing
that's
Thomas
actually
brought
up
on
our
structure
and
today
is
the
importance
of
Mishra's
title
since
we
use
this
for
the
changeling.
So
this
is
very
descriptive
title,
but
at
the
end
of
the
day,
what
this
is
doing
is
installing
bash
on
our
windows,
helper
image
right
so
to
have
it
in
the
changelog
property,
because
users
are
more
interested.
How
we
have
person
on
windows
instead
of
we
installed
the
food
get
version.
What
does
that
mean
for
us?
So
what
I
would
change
that
to
is.
E
C
Yeah
I
wanted
also,
maybe
your
for
America,
so
I
don't
know
updating
to
talk
to,
because
you
know
the
release
not
is
a
thing
but
actually
updating
the
dog
who
make
people
aware
that
we
are
actually
supporting
mash
as
well,
it's
important,
so
it
was
in
my
previous
marriage
requests.
I,
don't
know
if
we
want
to
have
this
magistration
back
in
this
magic
way.
So
if
I
shall
do
it
in
another
one
up
to
you
too,.
D
Ferris,
that
is
a
very
good
point
that
I
forgot
to
add.
Yes,
we
do
need
to
add
documentation
in
this
modulus.
We
do
have
it
in
our
documentation
guides
that
the
documentation,
at
least
the
minimal
part
of
the
documentation,
should
be
in
the
MERIS
that
introduces
the
feature
or
change.
So
we
should
have
it
here
and
then
we
will
ping
our
technical
writer
to
take
a
look
at
it
and
do
all
the
magic
that
the
comparators
do.
Okay,.
D
D
D
D
D
D
And
on
setting
it
up,
so
at
the
end
of
the
day,
what
all
you
have
to
do
when
you're
set
up
you
just
run?
Jdk
start
it
will
start
all
the
services
here.
I
have
to
run
or
disable,
because
I
prefer
one
running
on
a
separate
instance,
just
because
I
kind
of
development
it,
but
that's
different.
And
now,
when
I
go
to
my
local
host
for
2000
and
the
soonest
is
finishes,
loading
I
should
get
local
declare.
Business.
D
D
Get
a
brunner
binary,
I
I
just
prefer
building
it
locally
on
my
Mac,
just
because
it's
much
good
I
guess
if
I
build
it
on
my
Windows
VM,
that
VM
has
on
shared
disk
and
the
first
and
that
gets
quite
slow,
so
I
just
went
Utley
here
and
that
we
do
have
a
make
file
doing
made
build
and
only
passing
the
platforms.
If
you
don't
pass
in
the
build
platforms,
it
will
just
build
for
any
blood.
For
me,
we
support.
So
this
is
quite
nice.
D
D
D
It
should
have
the
conflict
so
got.
Let
me
check,
let
me
check
not
neglected,
so
on
and
I
do
have
a
window.
Stocker
I
start.
Let's
point
it
to
the
right
at
me,
and
since
we
are
using
the
helper
image,
let's
point
to
a
specific
health
manage,
so
you
you
can
overwrite,
which
I
very
much
used,
and
since
we
want
to
make
sure
to
use
a
specific
one,
let's
let
us
overwrite
it
so
topical
damages
and
will
say
that
we
only
want
to
use
tests,
no
matter
what.
A
E
B
Yeah
I
think
one
other
comment:
I
want
to
make
was
I
mean
for
I,
think
Elliott
you've
been
opening
issues
prior
to
office
hours.
We
were
trying
to
do
this
once
a
month,
so
if
you
have
any
topics
or
Mrs
that
Steve
or
other
engineers
want
to
take,
a
look
at
in
future
calls
feel
free
to
add
comments
directly
on
the
under
the
issue,
or
you
can
ping
me
on
gator
and
then
happy
to
relay
the
message
to
all
you
and
the
team
yeah.
A
D
D
And
the
reason
like
you
could
use
get
lapto
contoured
should
we
run
the
job
and
that
might
be
quicker
instead
of
using
the
local
GDP.
The
reason
I
enjoy
using
the
local
JDK
is
things
are
all
private
and
I
can
share
two
tokens,
and,
but
it's
not
so
I,
don't
have
to
think
about
tokens
or
anything
like
that.
D
D
C
Old,
so
I
was
just
I
just
added
some
documentation.
I
took
the
documentation,
I
have
already
on
the
last
request
and
I
see
that
in
the
limitation
you
say
that
there
is
a
limitation.
Daniel
said
I
cannot
be
used.
So
this
is
a
new
benefit
of
this
is
nanosolar
can
be
used.
If
you
are
you,
you
are
installing
bosch
inside
this
nano
server.
D
C
C
D
No
suggestion
I
also
add
as
adding
the
comment
inside
of
the
stomach,
specifying
that
we're
overriding
the
shout
just
to
make
it
more
clear
to
the
user
who's
reading,
the
top
the
atomic
but
hey.
You
need
to
update
the
shell
to
a
specific
value,
think
we're
over
time.
So
we
don't
want
do
we
want
to
continue
or
what
are
your
thoughts
on
it.
A
I,
don't
think
real
harm
to
continuing
I
mean.
Obviously
people
can
drop
off
the
call
whenever
they
need
to.
Let's
not
take
it
too
much
longer,
like
I,
don't
think
another
hours,
gonna
be
the
most
engaging
content
but
yeah.
If
you
want
to
kind
of
like
a
wrap
up
your
train
of
thought
and
go
for
another
10
or
15
minutes,
I,
don't
think
that's
a
problem.
You
know.
What's
so.