►
From YouTube: 2022-06-20 Delivery team weekly EMEA/AMER
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
So
welcome
everyone
happy
monday,
let's
get
started
so
we've
got
a
few
announcements
up
there.
Actually
I
was
going
to
read
only,
but
unless
you
want
to
give
us
a
quick
run
through
of
d,
I
think
this
is
worthy,
moreover,
than
just
a
read-only
right.
B
Yeah
sure
so
we
have
been
affected
by
this
problem.
There
was
even
more
frequent
recently
where,
basically
due
to
a
design
of
our
pipeline
engine,
if
our
pipeline
from
downstream
project
quality
in
this
case,
our
quality
pipeline
failed-
and
this
failed.
The
whole
deployment
pipeline
and
some
qa
engineer
restarted
the
the
pipeline
itself.
B
Then
they
were
taking
ownership
of
everything
upstream
and
we
were,
and
those
department
were
just
blocked
because
then
they
had
no
permission
to
trigger
a
real
deployment
in
downstream
into
the
deployed
project.
So
we've
been
working
with
them
to
find
a
workaround.
B
Last
week
we
implemented
one
which
was
kind
of
a
bit
too
complex.
We
were
creating
a
new
child
pipeline
that
was
verifying
the
the
ownership
as
well,
but
then
we
realized
that,
in
order
to
do
so,
we
had
to
give
all
the
quality
department
permission
to
create
tags
on
oops
on
the
route
on
release
tools.
B
So
we
quickly
gave
this
for
a
couple
of
days
just
to
it
was
still
better
than
because
the
deployment
itself
was
still
protected
because
they
had
no
permission
to
trigger
a
deployment,
but
so
they
could
run
a
pipeline
in
release
tools,
but
we
changed
this
again,
so
it's
no
longer
triggering
a
dynamic
child
pipeline,
but
the
the
check
itself
is
just
regular
job.
So
now
we
have
the
simpler
and
workaround
that
is
actually
working.
We
tested
it
this
morning
and
yeah.
So
that's
it.
A
And
everyone
who
joined
in
that
discussion
so
ruben
myra.
I
know
you
were
still
on
there
but
like
we're
done
for
getting
this
unblocked
so
rapidly
like
yeah.
So
it's
a
real
huge
one.
B
Thank
you
and
thank
you,
everyone
for
the
help.
So
discussion
point
it's
it's
still
kind
of
an
announcement,
but
I
wanted
to
quickly
understand
if
people
are
aware
of
this,
so
it
is
possible
to
join
release
management
temporarily.
You
get
all
the
permission.
You
get
part
of
the
release,
manager's
luck
handle,
which
means
that
if
you
are
covering
for
someone
for
half
a
day
one
day
whatever
you
can
get
all
the
baking
time
notification,
people
pinging
release,
managers,
everything
you
get
it
and
overnight
overnight
for
us
in
europe,
so
four
a.m.
B
You
can
see
it
resets,
because
it's
the
point
in
time
when
we
rechain,
we
align
all
the
permissions.
So
if
you
forget
to
remove
the
to
forget
to
remove
this
temporary
things,
it
just
goes
away.
So
if
you
want
to
rejoin
or
to
leave
early,
there's
there's
a
documentation
there
that
explain
you
how
to
join,
how
to
live.
B
Is
that
just
for
the
slack
handle,
or
also
for
the
great
gitlab
handle
everything
you'll
get
all
the
permission
on
all
the
projects,
which
also
means
going
to
give
an
example
if
you
are
covering
for
a
patch
release,
so
this
is
something
that
happened
with.
Graham
gray
was
trying
to
do
a
patch
release
and
it
was
not
officially
a
release
manager,
so
he
couldn't
merge
the
blog
post.
I
think
I
don't
remember
it
was
something
they
couldn't
merge
or
maybe
it
could
emerge
on
the
stable
on
the
state.
B
B
A
Awesome
thanks
thanks
for
that,
thanks
for
sharing
that
what
I
might
do,
I
haven't
put
it
on
here,
but
what
I'm
vaguely
thinking
about
is
for
that
page
in
the
docs.
I
may
split
that
in
half
and
have
it
so
we
have
a
release
management
page
for
I'm,
a
brand
new
release
manager,
I'm
about
to
start,
and
then
we
can
have
a
a
second
page,
which
is
I'm
a
returning
release
manager
and
it
might
have
more
stuff,
that's
more
relevant
to
you
know.
A
B
Yeah,
even
in
terms
of
surprise,
if
matt
or
jenny
are
going
to
try
that
pipeline
will
just
fail
for
them,
because
you
first
need
to
be
to
do
the
first
enrollment
as
a
release
management
there
is
manager.
So
it
means
that
you
first
need
to
add
yourself
into
config
slash,
release
manager.yaml,
so
you
have
their
your
name,
your
username,
on
all
the
environments,
your
slack
handle,
and
then
you
are
allowed
to
to
run
the
thing.
A
And
don't
worry
about
doing
that
just
yet!
You
too,
like
we
have
another
onboarding
issue
for
onboarding
into
release
management
that
will
will
open
up
for
you
in
a
like,
maybe
a
month
or
so.
A
Awesome
should
we
jump
to
three.
B
Yeah,
unless
there
are
other
discussion,
do
we
want
to
add
last
minute
we
can
jump
into
three
okay.
No
one
is
picking
so
yes,
the
first
part
of
three
is
just
just
a
call
for
help.
It's
related
to
the
first
announcement
we
did.
B
If
the
validate
ownership
check
is
failing,
you
will
see
a
message
like
this
one
that
I
screenshot
you
see
failed
job
bottom
right,
corner,
failed
job,
validate
ownership,
something
name
of
the
environment.
Please
please,
please.
If
you
see
this
act,
so
restart
the
thing,
because
this
may
happen
not
during
so
this
happened
before
the
promotion.
This
could
happen
between
staging
canary
staging
production
staging.
B
So
maybe
there's
no
release
manager
around
closely
looking
at
this
type
of
error,
but
the
pipeline
will
not
restart
until
someone
clicked
that
button,
so
everyone
that
is
in
that
config
release
manager
yaml.
If
they
see
something
like
this,
please
click
the
fail
job
and
retry
the
job.
It
will
just
reset
the
pipeline
and
it
will
work
as
as
expected.
A
B
B
Of
us,
we
can
even
automate
this
with
the
what's
the
name
with
the
web
books,
so
that
actually
is
real
time
but
yeah.
If
someone
wants
to
log
an
issue
about
this,
we
can
take
a
look
but
yeah
in
the
meantime,
if
you
see
the
failure,
please
retry
it
and
then
I'm
going
to
quickly
go
through
the
numbers
release
of
the
release
this
week,
because
there
are
some
cool
things
to
see
show.
B
B
I
mean
we
were.
We
were
doing
good,
we're
doing
well
every
day
with
some
very
good
day
and
some
kind
of
we're
wasting
one
or
two
packages.
So
I
think
that
we're
wasting
one
package
is
okay,
it's
normal,
because
you
always
want
to
have
something
in
the
pipeline
ready
for
next
right
so
and
so
it's
kind
of
makes
sense
to
always
have
something
ready.
There
is
running.
Sometimes
we
had
things
like
here
when
we
have
three
packages,
because
these
are
all
the
problems
that
we
had.
I
think
that's
the
note
yeah.
B
That's
the
pipeline
ownership
problem,
so
we
were
hitting
really
hard
this
week
on
the
pipeline
ownership.
That's
why
we're
also
trying
to
have
the
fix,
so
I
mean
compare
it
to
that.
We
compare
later
so
that's
that
one.
This
is
the
the
number
of
active
pipeline.
That's
interesting,
because
we
finally
have
almost
one
week
of
data,
even
though
we
have
a
window
here
with
which
was
completely
broken.
B
So
when
we
introduced
the
fix
for
the
pipeline
ownership,
we
broke
the
the
metric
itself,
so
everything
in
here
makes
no
sense,
but
basically
what
I
said
here:
okay,
so
that's
the
when
staging
was
offline
for
doing
a
composition
test,
then
we
had
a
couple
of
qa
failure,
an
omnibus
problem
and
finally,
a
broken
deployment
to
pipeline
ownership.
So
we
can
clearly
see
this
ramping
up.
B
B
So
basically,
we
had
over
the
weekend
three
pipeline,
three
packages
ready
for
promotion,
but
obviously
no
one
was
promoting
over
the
weekend,
so
this
is
kind
of
a
baseline,
so
we
ended
up
the
week
with
three
things:
three
packages
after
the
last
successful
deployment
and
that's
this
morning,
so
we
started
building
new
packages,
and
so
we
saw
the
numbers
going
up
and
then
we
see
going
down
for
every
deployment.
So
we
started
week
as
expected
with.
We
are
deploying
everything
this
morning
so
so
far
everything
is
in
promotion.
B
B
A
B
A
Yeah,
I
think
it's
like
the
15th
is
the
really
interesting
one,
because
I
think
when
you
see
mttp
low
it's
often
because
we've
had
a
couple
that
are
significantly
below.
So
I
think
if
you
look
compared
to
the
7th
to
the
11th,
I
think
the
real
difference
is
that
we
had
a
nice
chunk
between
the
14th
and
the
16th,
where
it
was
like
consistently
below
or
right
on
it,
so
that
will
have
a
huge
impact
on
mttp.
So
yeah,
that's
really
good.
B
A
Difficulty,
which
is
the
key
metrics
so
because
mttp
is
also
a
key
metric
like
so
it
won't
come
out
of
the
handbook,
but
certainly
if
somebody
wants
to
have
a
chat
with
marion
about
the
slack
alert
I
it
must
be
on
his
account.
I
guess
right
because
it's
always
been
there.
So
if
someone
wants
to
get
that
switched
over
to
the
one
other
product,
then
yeah
go
for
it.
B
I
think
we
need
to
wait
for
there's
an
issue.
The
theme
is
working
on,
which
is
about
having
the
url
to
so
the
the
page
that
was
showing,
because
I'm
no
longer
sharing.
No
I'm
not
the
page
that
I
was
showing
is
always
reset
to
last
week,
and
you
can't
really
so
they're
working
on
some
way
to
and
also
you
could,
because
there's
the
same
page
for
all
the
for
different
metrics,
I
think
so
they're
working
on
something
where
the
url
reflects
the
date
range
and
what
you
are
looking
at
right.