►
From YouTube: GitLab 13.8 Kickoff -Release:Release
Description
GitLab 13.8 Kickoff -Release stage
13.8 Release planning issue - https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/27
A
A
So
today,
under
analytics,
you
have
a
ci
cd
section,
which
shows
the
pipeline
view,
and
this
will
add
additional
to
the
to
the
graph
that
exists
today.
It
will
add
the
deployment
statistics
so
you'll
see
deployment
frequency
for
different
intervals,
so
in
that
same
location,
we're
going
to
add
a
graph
directly
underneath
the
pipeline
joints,
this
kind
of
condenses
the
view
a
little
bit,
but
this
is
the
first
iteration
and
and
already
in
this
milestone,
we
kind
of
want
to
make
this
simpler.
A
So
we
have
an
additional
issue
to
introduce
tab
navigation
between
pipelines
and
deployments.
So
what
we
want
to
do
is,
instead
of
just
leaving
that
deployment
chart
directly
under
the
pipeline
view,
making
a
really
really
long
page.
You
want
to
introduce
tab
navigation,
so
you
can
see
you
will
have
this
new
tag
called
deployments
and
clicking
on.
It
will
show
that
graph
that
is
shown
in
the
previous
issue,
so
you'll
have
the
pipelines
in
one
view
and
deployments
in
another.
A
A
Let's
say
that
you're
you
want
your
qa
team
to
take
directly
from
the
mr,
the
build
artifacts
and
go
ahead
and
test
it,
and
so,
instead
of
them
having
to
you,
have
to
upload
this
to
somewhere
or
they
have
to
go
to
the
pipeline
view
and
then
click
from
there
to
download
artifacts.
This
will
be
accessible,
direct
directly
from
the
merge
request,
widget
itself,
making
it
just
so
much
quicker
and
easier
to
collaborate
from
a
single
location.
A
So
you'll
see
this
regular
download
and
you
can
download
the
artifacts
and
let's
say
you
are
testing
a
mobile
device
and
you
need
that
specific
apk.
You
just
download
it
and
continue
on
to
your
testing
upload
the
apk
to
the
mobile
phone
and
continue
testing
and
put
all
your
comments
on
the
merge
request
itself
without
needing
to
go
to
different
locations.
A
The
last
issue
that
I
want
to
discuss
is
pipeline.
Success
emails,
look
too
much
like
pipeline
failure
messages
and
what
we're
doing
here
is
a
small
tweak
to
also
make
this
easier
to
comprehend
and
more
visible.
So
today
you
get
a
notification
saying
that
your
pipeline
has
been
fixed
or
your
pipeline
is
fat,
has
failed
or
so
on,
and
so
forth
kind
of
looks
like
this,
and
the
message
looks
very
similar,
so
there's
just
a
change
of
one
word:
either
fixed
or
success
or
failed
and
that's
confusing
to
users.
A
So
what
we're
doing?
What
we're
doing
here
is
actually
taking
the
body
of
the
message
and
making
that
the
title
so
that
it's
much
easier
to
understand.
What's
going
on
so
now,
you'll
see
successful
pipeline
as
the
first
word
or
failed
pipeline
as
the
first
word
or
fixed
pipeline
as
a
first
word,
so
that
you
don't
have
to
drill
down
and
really
understand,
what's
going
on
with
your
pipeline.