►
From YouTube: Weekly Mac Shared Runners Sync - 20200909
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
I've
been
working
on
having
the
built
by
a
child
build
pipeline
for
each
of
the
xcode
versions.
A
Initially
I
I
did
it
like
this,
so
we
generated
the
base
where
we
change
the
admin
passwords
we
perform
the
os
upgrades.
Then
I
install
all
the
package
managers
in
the
following
job
and
save
that
image
and
then
use
that
image
for
the
child
pipeline
with
all
the
parallel
jobs
for
the
xcode
versions
and
then
use
those
to
creates
the
the
runner.
A
A
Well,
the
runner
one
just
takes
the
xcode
and
installs
the
specific
version
of
of
the
runner.
So
if
you
just
want
to
do
a
new
release
with
a
different
runner
version,
it's
really
quick
because
it
just
takes
the
xcode
and
does
a
quick
installation
of
of
the
runner.
So
with
the
new
approach.
A
A
Yeah
yeah,
the
following
point
is
that
I
was
going
through
issues
with
the
the
pipeline.
So
if
I
show
you
here,
my.
A
Actually,
this,
let
me
just
reset
so
it's
okay.
So
in
this
case
I
built
a
separate
mr
on
top
of
the
xcode
one,
and
what
happens
is
that
it
just
built
some
of
the
jobs,
so
it
didn't
go
through
the
base
tool
chain.
A
So
what
I
ended
up
doing
is
this:
if
we're
doing
a
merge
requests
and
we're
not
going
through
the
default
branch,
we're
not
merging
to
the
default
branch,
we
make
sure
we
build
and
if
we're
going
to
the
default
branch,
we
can
optimize
and
just
do
those
if
so
most
of
the
time
it
will
take
these
take
into
consideration
these
changes.
But
if
we're
building
multiple
mrs
on
top
of
a
another,
we
don't
gain
those
optimizations.
A
B
A
B
But
no
you
want
to
target.
So
even
if
I
open
up
a
merge
request,
that
is
not.
That
is
only
updating
the
runner
right.
I
don't
want
to
build
the
tool
chain
for
me
right.
I
wanted
to
just
run
export.
A
A
Yeah
it
should
in
this
case.
Well,
if
I
go
to
the
runner
one,
so
in
this
case
yeah
it
will
build
xcode
and
runner
in
the
same
job.
Okay,.
B
A
Okay,
mr
branch,
okay,
so
this
same
thing
yeah
actually,
so
it
should
just
be
a
certain
place.
Okay,
I'll
take
care
of
that
cool
thanks.
A
Okay,
so
yeah,
I
guess
this
one
is.
A
C
We
can
try
without
it
right
and
to
see
what
kind
of
feedback
we
get.
What
we
should
do
is
let
me
just
double
check
this
so
right
now
in
the
proposed
xcode
versions
in
the
closed
beta
image,
I
do
have
s
code9.
So
what
if
I
take
up?
If
what,
if
I
make
a
note
I'll
put
a
comma
in
the
issue-
hey
folks,
we're
removing
xcode
9
as
well
as
xcode
7
from
the.
A
Image
just
to
be
clear:
it's
not
a
big
deal
to
to
support
it.
It
might
be
in
terms
of
space.
You
know,
quota.
C
A
But
you
know,
if
I
show
you
the
I
already
created
the
high
sierra
based
image.
So
if
I
do
an
image
list,
it's
it
doesn't
take
a
lot
of
space,
it's
16
gigs.
A
So
basically,
if
we
don't
do
a
lot
of
parallel,
mrs
at
the
same
time
you
know
it
shouldn't
take
a
lot
a
lot
of
space-
and
here
I
already
have
you-
know
one
job
that
creates
10.13
base,
image
and
another
10.15
and
then
same
thing
for
tool
chain,
and
then
it
goes
on
to
the
xcodes
and
then
based
on
the
version
of
the
x
codes.
A
A
C
Personally
speaking,
I'm
okay
leaving
it
out
and
seeing
what
kind
of
feedback
we
get
right
because
we
can
get
like
those
12
customers
of
silence
like
yeah
only
x
going
on,
and
then
you
know,
maybe
I
get
the
one
customer
says
they
absolutely
need
it.
But
I
said,
let's
that's
not
included
for
the
closed
beta
and
let's
see
what
kind
of
feedback
we
get.
That's
just
my
goal.
A
Okay,
yeah,
the
the
thing
I
I
find
interesting
is
why
7.41,
I
think,
works
on
catalina
and
just
not
941,
and
the
only
the
only
thing
in
particular
about
xcode
9
is
the.
Is
it
it's?
The
last
version
to
support
32
build
bit
build
versions,
so
you
know
we
might
have
a
customer
that
wants
the
latest
one
and
needs
to
support
32-bit.
B
A
B
Worry
about
these
weird
educations,
let's
just
focus
on
like
the
latest
and
greatest
and
then
will
direct
issues
to
users
to
your
issue
that
support
further
macos
version.
I.
B
B
A
B
I
would
just
remove
the
apple
for
now
and
just
see
what
users
want
because
like
if
no
one
asks
for
it,
there's
no
point
for
us
to
support
it
yeah.
So
if
you
can
leave
an
update
on
the
issue
while
we're
removing
it
and
things
like
that,
that
would
be.
A
Perfect:
okay,
just
take
a
note.
A
There,
the
next
thing
is,
you
probably
received
an
email
about
this
logic
monitor,
so
I
had
to
contact
them
because
we
were
getting.
A
A
Okay,
yeah.
B
C
I
just
checked
this
morning:
we
now
have
12
customer
requests
for
customer
search
user
requests
to
get
access
to
closed
beta.
I
haven't
responded
back
anyone
as
yet,
but
I
will
review
kind
of
all
of
our
notes
that
we
took
last
week,
but
maybe
steve
ray
did
this
with
elliot,
but
I
I
we
haven't
had
a
good
discussion
about
the
the
mac
stuff
so
and
now
what
I
want
him
today,
I'm
going
to
review
everything
I'm
going
to
make
you
know
should
make
sure
we're
synced
up
and
so
on.
C
So
just
want
to
share
that
with
you
with
everyone.
That's
it
for
myself.
A
C
B
C
B
A
A
I'm
just
yeah,
I
already
merged
the
one
about
slip,
splitting
the
ci
job
so
well.
One
of
them
is
really
it's
just
like
a
documentation
thing,
adding
linting
for
documentation.
So,
okay,
it's
a
small
job,
awesome.
B
C
C
C
B
Yeah,
because
last
week
was
mostly
focusing
on
the
job
blocks
for
the
kubernetes
migration,
and
this
week
is
trying
to
wrap
up
the
after
school
stuff.
So
I
don't
think
I'll
have
time
to
review
anything
this
week
regarding
microwaves,
okay,
that.
B
C
Since
the
I
didn't,
I
haven't
thought
of
since
the
thing
pedro
have
you
had
any
slack
conversations
with
them
by
chance.
B
B
Yeah
yeah,
it
doesn't
have
to
be
all
the
merch
requests
merged.
We
just
need
to
use
an
image
that
was
produced
by
those
requests.
A
Yeah
I
can
reach
out
to
the
the
person
who
pinged
us
about
it.
I
think
it
was
lippert,
so
we
could
reach
out
to
him
and
see
if
his
you
know
how
his
schedule
is
looking
like
if
he
would
have
some
time
to
work
on
that,
getting
it
on
our.
C
C
And
the
only
one,
I
think
I
don't
have
any
agenda.
So,
let's
see
everyone
know
the
other
thing,
so
we
need
to
go
through
the
process.
Stuff
again
talk
to
elliot.
The
other
thing
in
parallel
I
have
to
do
later
on
this
week,
is
still
come
back
on
how
we
do
pricing,
since
all
those
pricing
changes
has
been
in
last
week,
it's
become
very
apparent.
I
need
to
figure
out
what
we
have
to
do
in
terms
of
the
back
end,
where
to
figure
out
the
pricing
changes.
That's
another
thing.
C
It's
only
in
gitlab.com
so
like
nothing
not
for
closed
beta,
but
when,
when
we
go
ga,
how
are
we
going
to
price
this?
You
know,
obviously,
everyone's
been
talking
about
sort
of
this
credit
model.
C
The
credit
models
right
now.
The
credit
model
that
commute
came
up
with
so
a
is
that
the
money
we're
going
to
use
and
then,
if
so,
if
that's
the
model,
what's
the
factors
we're
going
to
apply
for
the
macos
stuff
and
then
do
we
have
to
make
any
other
changes
and
get
real
important
to
start
measuring.
B
Changes
wise,
I
think
that
should
be
done,
because
that
is
what
camille
and
alexi
were
working
on
a
few
months
back
implementing
the
factors,
basically,
so
that
I
I
think
it
should
all
be
done,
and
then
it's
a
matter
of
just
setting
up
the
vectors.
As
you
said,.
C
And
there
was
one
other
thing.
Let
me
just
have
this.
I
want
to
look
at
today
with
elliot.
Let
me
just
add
it
here.
I
want
to
just
double
check
what
we
have
to
do
with
this
issue.
That
can
you,
if
anything
I
created,
I
hadn't,
looked
in
a
while,
so
I
was
looking
at
it.
I
was
trying
to
look
at
it
in
the
context
of
all
of
those
pricing
discussions.
C
So
here
the
fact
is
was
done
so
I
need
a
double
check.
Okay,
the
factors
table
is
there
and
how
does
it
tie
to
this
other
thing
that
timmy
was
talking
about
you
know,
so
that's
the
that's
one
thing
I
want
to
make
sure
I
get
straight
because
we
don't
need
it
for
closed
beta,
but
I
need
to
kick
up
the
discussions,
hopefully
the
next
couple
of
weeks,
with
all
of
the
leadership
team
around
hey.