►
From YouTube: GitLab 14.6 Kickoff - Verify:Pipeline Authoring
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
A
So
we
do
have
two
bug
fixes
that
we
want
to
take
it
in
into
this
iteration
and
again.
This
contributes
to
the
quality,
chaos
and
in
terms
of
a
feature,
and
we
want
to
start
working
on
this
epic
and
this
epic
triggering
and
retrying
job
actually
emerged
from
one
of
the
most
popular
issues
that
we
have
both
in
terms
of
ar
and
in
terms
of
requirement
from
the
customer.
It's
actually
issue
number
two
here
and
if
you
try
to
read
this
too,
you
can
see
so
first
of
all
a
lot
of
upvote.
A
A
Besides
a
bridge
job
now
bridger
became
more
and
more
popular
because
they
enabled
parent
child
pipeline
multi-project
pipeline
very
popular
use,
cases
in
monorepos
and
mo,
and
today
it's
practically
impossible
to
retry
to
retry
a
bridge
job
which
eventually
replies
the
downstream
pipeline,
now
think
about
it.
If,
as
a
user
now
today,
I
want
to
redrive
a
downstream
pipeline.
I
need
to
rewrite
the
whole
pipeline
in
order
to
do
that,
also
the
parent
pipeline
and-
and
it's
very
popular
today,
that
a
single
bridge
job
trigger
multiple,
downstream
pipelines.
A
A
So
in
this
in
this
iteration,
we
just
want
to
add
the
ability
for
user
to
retry
the
bridge
pipeline
by
creating
this
page
for
the
bridge
pipeline
and
this
button.
That
does
a
reply
now
what
it
will
do.
It
will
enable
us,
then,
in
future
iteration
to
add
more
actions
on
top
of
the
blade
job
and
eventually
we'll
be
able
to
bubble
up
those
actions
into
the
into
the
pipeline
graph,
but
still
more
to
come
on
that
so
in
the
first
iteration.
A
B
So
the
first
issue
that
I
will
work
on
is
solution
validation
for
the
pipeline
editor,
so
I've
been
working
on
this
issue
in
this
milestone
as
well,
but
in
14.6
I
will
be
wrapping
up
the
user
interviews
and
I'm
very
excited
about
the
insights
that
we
will
uncover
another
solution.
Validation
research
will
be
for
pipeline
simulation
of
dc.
B
Another
very
interesting
issue
that
I
will
be
working
on
is
this
ux
scorecard
for
pipeline
authoring.
B
It's
part
of
the
ux
department,
q4
okrs,
and
for
this
issue
I
will
be
collaborating
with
jarek
a
product
designer
on
the
foundations
team
and
together
we
will
do
a
walk
through
of
the
pipeline
authoring
experience
where
jarek
will
be
looking
at
a
product
with
fresh
eyes
as
someone
who's,
not
as
familiar
with
the
pipeline
authoring
experience
as
I
am,
and
hopefully
it
will
help
us
uncover
all
kinds
of
opportunities
for
improvement
when
it
comes
to
learnability
of
the
pipeline
authoring
tools
or
creating
a
cicd
pipeline
and
the
overall
usability
of
that
experience.
B
And
if
you
look
at
other
issues
here
really,
my
focus
will
be
on
usability
improvements
such
as
addressing
ux
depth,
ux
scorecard
recommendations
and
ux
research
that
helps
us
uncover
further
opportunities
for
improvement.