►
From YouTube: Weekly Mac Shared Runners Sync - 20200929
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
so
let's
go
to
the
agenda.
A
Yeah,
so
it
seems
at
least
it
would
warrant.
You
know
regarding
this
docker
question
it
would
warrant.
Knowing
the
the
scenario
where
we
could,
perhaps
just
as
steve
was
mentioning,
do
the
work
in
a
linux
machine
and
get
the
results
as
an
artifact.
Maybe
I
don't
know,
but
it's
certainly
worth
exploring,
but.
B
Yeah,
if
he
wants
to
use
linux
container,
might
as
well
just
use
our
linux,
vm
storage,.
C
Gotcha,
okay,
that
makes
more
sense
to
me.
So
what
I'll
do
is
I'll
I'll
respond
back
to
him,
and
this
is
actually
a
really
interesting
point
not
for
this
call,
but
maybe
folks
just
need
an
understanding
of
how
best
to
construct
pipelines,
which
is
not
really
our
responsibility,
but
I
see
it
for
your
point.
I
had
a
comment
I'll
respond
back
to
madison's
comment
that
helps
me.
C
Too,
I
know
we
jump
to
number
two.
Do
we
want
to
talk
about
number
one?
I
just
copy
the
current
date
from
the
last
agenda
on
pager
and
if
you
want
to
cover
number
one
or
let's
move
on.
A
Well,
there's
not
many
changes.
You
know,
we've
just
been
provisioning
vms
for
customers.
C
Okay
and
then
I
painted
a
few
folks
last
night
and
a
few
folks
responding
back
so
I'm
trying
to
respond
back
to
their
pings
and
ping.
You
as
well,
okay,
so
number
three.
My
question
was,
I
know
pedro
and
steve.
Both
of
you
are
pretty
well
versed
in
the
whole
image
creation
process.
I
just
wanted
to
just
kind
of
if
you
can
verbalize
me
at
a
high
level
kind
of
like
image,
creation
and
management
process
for
the
pm.
C
What's
getting
attention
kind
of
what
that
process
looks
like
I'm
just
and
the
reason
I'm
asking
that
I'm
starting
to
think
about,
and
maybe
steve
and
peter
you
already
talked
about
it.
Thinking
about
like
long
term,
we
go
to
ga
how
much
work
it
is
for
us
to
maintain
the
image
like
how
flexible
and
how
quick
can
we
be
to
like
add
new
capabilities
to
the
image.
I
just
want
to
understand:
what's
really
going
into
the
image
management
creation
process
right
now,.
A
C
Yeah
the
developer.
That
so
say
you
were
on
boarding
a
brand
new
engineer
to
the
runner
team,
and
you
said:
hey
you're
responsible
for
updating
our
mac
os
imaging.
What
does
that
person
actually
have
to
do
to
add
something?
Like
say
we
had
to
add
xcode
12
ga
to
the
image
like
what
does
that
person
actually
have
to
do
to
get
all
that
stuff
done.
A
A
A
B
What
we
want
in
a
job
description
would
be
these
and
like
the
developer,
needs
to
know
ansible,
kevlar
ci
and
that's
pretty
much
it
and
then
some
scripts,
because
everything
is
automated
through
ansible
and
that's
just
like,
let's
say
hey,
we
want
to
change
the
gitlab
runner
username
for
something
else.
It's
a
matter
of
updating
the
script
to
do
so.
B
A
I
think
also,
you
know,
ansible
knowledge
is
not
really.
I
think
what
is
more
important
is
knowing
the
mac
os
system.
You
know
how
the
os
works.
Ansible
knowledge,
you
can
quickly.
A
You
know
by
looking
at
the
other
files
how
they're
structured
you
can
pick
it
up
relatively
quickly,
but
I
noticed
that
what
ended
up
taking
more
time
is
how
to
get
you
know
the
user
set
up.
You
know
the
user
account
set
up
on
on
mac
with
the
certain
rights
and
so
yeah.
That's
the
the
part
that
takes
more
time
in
setting
up
the
image.
C
And
my
last
kind
of
question
just
for
today
and
I'm
probably
probably
have
a
full-on
conversations
on
this-
I
know
we're
still
obviously,
in
the
beginning
of
closed
beta
today.
Can
I
assume
that
real
in
terms
of
that
process,
you
just
described
hey.
I
go
into
this
to
the
apple
store
I
download
x412.
C
B
And
we're
gonna
start
to
create
the
issue
for
this,
but
let's
find
me
and
better
discuss
the
way
to
version
them,
so
we're
gonna
follow
the
same
versioning
scheme
we
do
on
windows
and
on
our
linux
runners.
Basically,
every
time
we
merge
on
master,
we
will
have
some
manual
jobs,
which
we
call
publish
and
then
this
basically
will
create
a
vm,
an
image
and
orca
with
the
date
timestamp.
B
So
imagine,
2020,
09,
28,
right
and
then
users
will
use
that
image,
and
this
gives
us
a
way
to
slowly
upgrade
like
it
can
be
manually
or
through
the
auto
scaler.
So
in
the
auto
scaler
for
windows,
we
specify
what
image
to
use
right
from
gcp,
and
this
will
work
the
same
like
we
specify
hey
for
new
jobs,
use
the
image
with
listening
and
like
that
we
can
properly
tag
them
and
roll
them
out.
C
B
B
A
So,
on
point
five:
it's
a
simple
question.
As
I
was
provisioning,
today's
vm,
I
noticed
that
we're
still
using
13.1.1
for
the
gitlab
runner
should
we
use
a
more
recent
version.
B
It's
worth
the
time
to
update
it.
For
now
we
can
update
it
once
in
a
while.
A
Okay,
yeah,
so
are
there
any
more
subjects
to
cover
or
smoke
any
last
questions?
A
Okay,
so
we're
done
for
this
week,
stop
the
recording.