►
From YouTube: GitLab 13.2 Kickoff - Verify:Continuous Integration
Description
Correction of a misstatement in the video: the 13.2 release date is July 22 (not June 22).
Feature issues discussed in the video:
https://gitlab.com/gitlab-org/gitlab/-/issues/197140
https://gitlab.com/gitlab-org/gitlab/-/issues/219431
https://gitlab.com/gitlab-org/gitlab/-/issues/12136
A
A
Okay,
so
we're
here
today
to
go
through
the
features
plan
for
the
kickoff
of
milestone,
13.2,
which
you
will
be
releasing
on
June
22nd.
What
I'm
sharing
here
with
you
is
a
list
of
the
direction
issues
which
are
our
planned
feature.
Development
in
milestone,
13.2
you'll,
see
that
last
on
the
list
is
some
improvements
are
being
due
to
the
merge
train
capabilities,
as
well
as
continuing
work
on
the
CI
link
tool
and
a
UX
improvement.
That's
planned
for
parent-child
pipeline
feature
so
going
right
into
it.
A
If
we
look
at
the
first
issue,
that
was
on
the
list,
let
me
refresh
don't
know
where
that
message
came
from
you'll
see
that
the
problem
that
we're
trying
to
solve
here
is
that
the
current
visualization
of
a
parent-child
pipeline
doesn't
really
depict
which
jobs
trigger
a
specific
child
pipeline.
So
I'm
going
to
hand
it
up
Dimitri
to
talk
about
how
we
would
want
to
go
about
solving
for
this
Thank.
B
You
Tao
in
order
to
improve
this
situation,
we're
thinking,
visual
connection
between
a
trigger
job
and
a
child
slash
downstream
pipeline.
Now,
by
adding
in
the
additional
information
into
the
child's
list
downstream
note
optionally,
we're
exploring
if
we
need
to
highlight
trigger
job
as
well.
Back
to
you.
A
So
when
doing
this,
we're
hoping
to
in
showing
the
correlation
between
a
job
and
the
pipeline,
it
triggers
it'll
not
only
make
it
easier
to
understand
a
pipeline.
We're
hoping
it'll
also
help
you
trace
the
behavior
of
a
failed
pipeline
when
there's
clearly
visible
dependencies
that
you
can
use
for
your
troubleshooting.
A
Next
is
an
issue
we
have
for
continued
work
on
the
CI
and
link
tool.
So
the
problem
here
is
with
the
availability
of
the
new
features
that
we're
releasing
every
month
or
advanced
features
for
configuring.
Your
CI
a
see
the
pipeline.
Sometimes
it's
really
difficult
to
come
up
with
to
keep
up
with
how
to
correctly
use
them
in
your
get
lab
CI
mo
file
Dmitry's
going
to
walk
through
how
we
could
approach
this
problem.
A
B
You
in
the
previous
milestone,
we
implemented
the
framework
to
support
various
types
of
messages,
and
the
proposal
in
this
issue
is
to
display
messaging
about
the
applications,
as
well
as
warnings
and
errors.
Additionally,
we
want
to
make
sure
our
messaging
is
consistent
across
our
sea
islands
and
page
and
the
pipeline
detail
page
making
sure
we
don't
downgrade
any
other
information
and
make
sure
the
information
architecture
of
the
page
is
consistent.
A
Is
this
issue
to
added
to
do
tasks
according
to
merge,
train
events
and
the
event
that
were
specifically
trying
to
solve
for
in
this
issue
is
when
the
burst
train
drops
the
mr
that
you
submitted
for
merging
so
currently,
there's
no
notification
when
the
mrs
dropped,
and
so
therefore
you
don't
have
any
idea
that
there's
further
action
you
need
to
take
dmitri.
How
would
you
envision
us
solving
for
this?
Yes,.
A
You'll
notice
that
the
issue
does
distinguish
between
the
type
of
events
that
will
trigger
the
to
do.
We
certainly
wouldn't
need
to
create
it
to
do
when
the
cans,
the
users
themselves
cancel
the
emerge
and
then,
finally,
in
solving
for
this
problem,
what
we
want
to
do
is
help
you
know
when
your
Mr
is
not
going
to
be
merged
so
that
you
can
proactively
make
changes
and
react,
make
the
necessary
changes
before
submitting
it
again
for
merging.
A
B
You
Town
yeah
for
planned
UX
work
for
targeting
future
milestones
in
terms
of
user
value.
We
have
three
main
themes
currently
planned,
which
is
one
of
them.
Soon
up
is
to
collect
feedback
through
our
UI,
our
UI
for
the
directed
exactly
graph
feature
which
we're
going
to
introduce
as
a
betta
in
a
13.1
release.
B
This
will
initially
only
be
visible
on
github.com
and
we're
inviting
our
users,
through
our
interface,
to
leave
feedback
in
a
publication,
we're
going
to
guide
that
issue
to
receive
feedback
which
we
can
work
with
and
create
insights
and
opportunities
out
of
so
that
is
currently
in
progress.
The
other
two
themes
involve
Jenkins
the
Jenkins
wrapper
solution,
so
we're
going
to
focus
on
solution
validating
that
initial
work.
We
have
already
done
on
this
theme.
A
That
wraps
it
up
for
what
we
have
planned
for
at
13.2,
Thank,
You,
vesica
and
Demetri
for
joining
me
today.
If
you
have
any
questions,
feel
free
to
ping
us
directly
and
mention
us
in
the
issues
themselves.
I
will
link
to
the
issues
that
we
discussed
at
the
bottom
of
this
video
thanks
everyone
and
have
a
great
day.