►
From YouTube: Verify Group discusses Pipeline Dashboard MVC
Description
In this video, the Verify Group (Product, Frontend and UX) take a look at the current state of the upcoming GitLab 11.8 feature Pipeline Dashboard.
We go through the application and original designs and ask a lot of questions about where we are and where we're going.
To add your feedback - check out the issue here: https://gitlab.com/gitlab-org/gitlab-ee/issues/7861
Of note - forgot to start recording so it picks up right in the middle :)
A
B
Absolutely
understood
and
I
completely
agree,
Dimitri.
Absolutely
so
I'll
work
with
her
and
see
if
we
can't
get
that
done.
I
feel
good
I'm.
Just
I
was
a
little
bit
hesitant
about
the
or
concerned
about
having
it
done
by
the
first,
but
I
feel
pretty
good
like
we
can
have
it
done
by
you
know
by
the
end
of
the
milestone,
so
I'll
work
with
her
to
make
sure
that
we
can
stay
on
top
of
that
I'll.
Keep
you
guys
posted,
but
nice
he's
looking
good
by
the
way
Thanks.
C
The
one
other
thing
was
that
this
like
commit
component
was
previously
written.
So
it's
a
little
bit
it's
slightly
different
from
design.
I,
don't
know
if
you
noticed
instead
of
a
branch
icon,
it's
a
fork,
icon,
you'll
notice
that
I
have
this
like
random,
because
the
backend
for
the
pipeline
status
is
isn't
done.
So
every
two
minutes
when
it
pulls
I,
make
a
random
adjustments
for
the
statuses,
so
it
just
barely
changed
everything
anyway.
If
you
commits
like
this,
this
is
a
fork
icon.
C
A
It's
looking
good,
in
my
opinion,
what
we're
trying
to
do
so
from
my
perspective
and
from
the
legs
design
perspective.
What
we're
trying
to
do,
and
this
influences
or
designs
quite
a
bit,
is
that
they're
trying
to
adhere
to
this
8
pixel
or
4
pixel,
or
you
know
the
smallest
increment.
We
would
go
towards
it.
I
believe
2
pixel
grid.
So
the
same.
What
we're
trying
to
weed
out
out
of
the
entire
front
end?
A
C
A
C
C
D
C
D
A
C
D
A
Just
just
the
question
and
I'm
actually
interested
in
the
toward
Scott
and
John
is
that
for
these
kinds
of
changes
right?
So
it's
it's!
It's
almost
we're
almost
like.
Let's,
let's
be,
let's
be,
let's
be
clear
on
this.
We're
sure
that
this
is
this
needs
to
be
changed
towards,
like
the
branch
light
instead
of
a
for
guide
right,
so
I
always
wonder
what
the
workflow
or
the
mindset
is
of
front-end
in
order
to
change,
because
it
touches
some
a
lot
more
views
than
just
the
view
that
we're
tech
fun
right
so
I,
sometimes
wonder
like.
A
Can
we
just
include
it
into
the
scope
or
just
into
the
same
merged
quest
we're
trying
to
implement
this
feature
that
change
at
all
those
other
views
as
well
or
do
you
rather
do
it
in
a
separate,
merge
request?
And
then
you
know
get
it
reviewed
by
different
people.
If
that
is
needed,
or
something
like
that,
I
always
wondered
I,
don't
want
to
lose
philosophy
over
these
things
and
not
get
them
changed.
I
want
to
get
them
changed
without
you
know,
having
too
much
friction
in
our
process.
A
C
B
Just
to
add
on
to
that
I
think
the
the
the
con
of
that,
in
my
mind,
is
also
that
we
can
lose
track
of
these
things.
Dumitru
kind
of,
like
you
mentioned
earlier.
If
we
see
something
it's
nice
to
like
at
least
call
it
out
in
a
separate
issue
like
Scott
saying
before
before
we
lose
track
of
it,
but
losing
momentum
is
definitely
a
concern,
so
just
kind
of
reiterating
what
both
of
you
have
said
already
I
think,
depending
on
the
size
of
it.
B
Maybe
we
make
a
game-time
decision
and
say
if
it's
a
quick
thing
like
yeah:
let's
just
do
it.
If
it's
something
that
we
want
more
eyes
on,
and
we
want
to
call
out
a
little
bit
more,
we
just
pull
it
out
into
an
issue,
but
then
try
to
get
it
done
immediately
in
the
same
milestone.
Does
that
make
sense,
yeah.
A
A
We
can
give
to
an
issue
which
means,
if
we
have
a
lot
of
these
issues
with
those
really
small
things,
the
scope
of
combining
them
all
is
actually
bigger
than
the
actual
effort
that
needs
to
be
put
in
in
order
to
get
them
all
fixed
right
and
that
you
know
slows
down
organization
processes
and
those
kind
of
things.
That's.
A
D
Okay,
so
looking
at
the
design
and
I'm
looking
at
this,
there's
two
avatars
right,
there's
one
on
the
commit
message
underneath
master
right.
If
you
will
right
here
and
then
there's
one
to
the
right
to
the
left
of
the
whole
thing,
what
is
the
intended
difference
of
those
two,
so
the
different
actual
difference?
The.
C
Difference
is
that
commit
message:
avatar
is
the
author
of
the
commit
mm-hmm,
so
say:
Dimitri
committed
something
and
merged
it
to
master.
So
that's
there,
his
icons
next
to
it
because
he's
the
latest
person
sure
how
to
commit
on
master
the
icon
to
the
left
is
the
person
who
triggered
the
latest
pipeline.
So
it
not
necessarily
the
author,
it
could
be
the
author
of
the
commit
because
it's
like
automatic
pipeline
trigger
right,
but
I
could
manually
trigger
a
pipeline
which
her
master,
okay,
okay,
yeah.
A
Those
things
can
be
quite
quite
different,
say
that,
for
example,
Mara
and
uses
its
right
and
he
emerges
something's.
You
know
you
know
some
some
other
project
or
it's
some
other
branch
doesn't
mean
yes
they're,
not
in
the
last
midnight
and
those
are.
There
will
be
two
different
avatar
shown
there.
He
can
see
exactly.
You
did
wonder.
A
A
C
Think
in
the
spec
description
was
I.
Think
Dmitry
did
you
say
was
the
whole
time
that
that
pipeline
finished
finished.
Maybe
that's
what
I
understood
and
was
going
off
of
yeah.
So
the
reason
why
it's
not
there
as
if
the
pipeline
is
running
okay
or
some
reason
it
doesn't
have
the
the
last
time
finished
or
something.
E
A
A
This
is
when
it
was
scheduled
to
run
on
so
to
say,
and
the
time
that
we
are
shown
here
is
when
the
pipeline
finished.
So
in
this
page,
you
want
to
see
if
there's
something
wrong
with
your
projects
right
like
em,
how
long
ago
it
has
gone
wrong
like
how
long
ago
did
it
fail.
Something
like
that.
So
there
are
two
different
time
locations,
gotcha.
C
C
E
C
C
D
A
E
D
A
A
D
Yeah
yeah
yeah,
so
I
and
I
think
there's
two
to
empty
states
to
consider
maybe
I
think
there's
an
empty
state
of
no
commits
right,
which
is
probably
even
more
edge
but
then
also
the
pipeline.
Hasn't
no
pipelines
have
been
run
right
like
I,
don't
know
if
those
are
the
same
for
this
stat.
You
know
for
the
for
the
purposes
of
this
dashboard
right.
But
you
know
what
I'm
saying
to
meet.
You
like
I've
got
a
repository.
That
is
my
like
dot
files.
D
Right,
like
you
know,
send
it
to
the
group
just
because
we're
talking
about
it
right
now,
but
it's
such
Brendan
slash
next
Mac
right
now.
That's
all
that
all
the
dot
files
I
have
from
my
computer
and
so
there's
a
lots
and
lots
of
commits
for
that,
but
no
pipeline,
because
I,
don't
I,
don't
build
that
right.
So
I,
don't
know
if
that's
worth
considering
for
this
or
if
just
empty
means,
one
of
the
other.
You
know
empty
means,
no
pipeline
I,
don't
know,
might
might
be
worth
thinking
about.
Yeah.
A
Scott,
how
do
you
think
about
like
a
simple
understated,
hides
almost
everything
and
just
has
some
text
in
there
like
no
no
pipeline,
no
static
or
fear,
or
something
like
that
I'll
look
into
that.
It's
providing
you
any
mock-ups,
but
I
mean
like
if
there
is
no
committee
that
had
yet
or
if
there's
no
pipeline
or
CIA
to
pay
to
get
for
that
project.
I
mean
it's
not
gonna
show
chicken
chilling,
because
there
is
not
really
sure
yep.
C
A
C
D
A
Right
now,
all
right,
yeah
and
eventually-
and
this
is
taken
from
the
other
from
the
existing
operation-
that
46
dashboard
yep
but
I
mean
maybe
it's
not
ideal
yeah.
But
the
idea
was
there
to
also
like
hey
if
you
want
to
change
later
on,
if
lead
away
from
this.
No,
like
hey
my
changes
towards
a
certain
tag.
D
Seen
yep
and
then
and
then
my
last
question
is
there's
been
this
debate
ongoing
about
tearing
have
you
is
that
impacted?
Does
that
impact
front-end
or
back-end,
or
both
or
I'm,
not
sure
my
operations?
Dashboard
originally
was
only
an
ultimate,
but
the
plan
was
to
bring
the
functionality
of
the
pipeline's
into
premium,
but
then
the
alerting,
obviously,
and
any
other
monitoring
kind
of
things
that
come
in
that
here
eventually
would
be.
Ultimately
I.
Don't
know
if
that's
question.
C
A
C
C
Well,
I,
just
when
I
paint
Mattia
yesterday
on
the
issue,
I
asked
him
to
provide
me
with
like
lurked
metric
I
was
gonna.
Ask
you
some
of
the
the
spec
we
have
here
like
we
have
the
number
of
alerts,
some.
Sometimes
the
alert
isn't
there.
If
it's
not
configured
I
can't
I,
don't
know
how
to
tell
from
the
response
if
they
Lori's
configured
or
not.
Maybe
if
it's
null
or
something
instead
of
account
and
then
sometimes
we
have.
This
Ayres
is
greater
than
nine
percent.
C
D
E
A
Put
in
any
extra
discovery
feature
or
functionality
that,
if
don't
have
been
configured
that
it
you
know,
shows
anything
up
or
something
like
hey
this.
You
can
also
show
colors
or
something
like
that.
That
is
for
any
future
information,
any
new
functionality
to
this
page,
which
is
a
little
bit
more
apparent.
So
today,
yeah.
C
D
When
I
added
a
project
that
had
today
when
I
add
a
project
that
does
not
have
ultimate,
it
says
your
alerts,
none
and
then
doesn't
show
me
master
and
the
commit
and
the
timing,
but
on
a
project
that
does
have
ultimate
done
so
yeah
I'm
gonna
talk
to
Josh
and
try
and
sort
out
what
the
current
state
is
again.
I
don't
want
to
blow
the
scope
up
of
this
to
fix
or
change
any
of
it.
But
okay.
D
A
Right
sounds
good.
I
got
a
few
more
in
terms
of
like
how
this
relates
to
the
mock-ups.
The
things
that
provided
first
thing
was
I
want
to
touch
a
little
bit
on
the
badges.
The
middle
bags
that
represents
me
current
project
I
would
prefer
that
to
be
a
you
know,
a
full
batch
ID
with
text
in
there.
So
it's
a
little
bit
more
apparent
than
Dennis.
You
know
the
curve
pipelines
status
its
wondering
if
you
could
put
that
in
I
know
even
waiting
on
the
new
new
badges
requests
that
were
to
be
done.
Yeah.
C
A
C
A
Yes,
I,
don't
know
if
you,
if
you've
used
it
up
until
now,
but
I've
had
some
requests
where
they
used
to
review
apps
as
a
way
to
review
the
requests,
which
is
so
incredibly
awesome.
I'm
gonna
say
there
anything's
possible
for
this
one
but
and
I'm.
It
would
be
so
lovely
in
the
whole
front
end
and
back
end
team.
D
D
Hey
quick
question
before
as
Scott's
working
that
I
I
clicked
record
but
late
into
the
call.
Is
it
okay,
if
I
throw
this
meeting
on
to
our
unfiltered,
get
left
channel
cool
next
time?
We
do
this
we'll
live
stream
it
and
really
put
on
the
pressure
with
everybody.
Oh
I
just
could
be
good
for
the
community
to
see
like
how
we're
talking
do
this
stuff
in
great
discussions.
A
D
D
A
D
D
Actually,
I
think
it
actually
ends
up.
It's
gonna
end
up,
creating
I,
think
I.
Think
it's
taken
me.
You
know,
since
October
2017,
to
figure
this
out,
but
I
think
I
figured
it
out.
I
think
it
will
actually
create
a
folder
called
pipeline
dashboard
sneak
peek,
which
is
the
name
of
this
meeting
in
the
calendar,
and
that's
where
it'll
be.
A
D
D
A
C
A
A
D
There's
a
plan
yeah,
it
gets
complicated,
there's
a
plan
in
a
couple
of
releases
to
allow
the
inverse
relationship
right
like
today.
The
parent
needs
to
know
about
the
children.
If
you
will
right
that
the
parents
triggers
the
children
and
parent
child
is
not
the
right
word
here,
but
it
helps
the
upstream
pipeline
triggers
the
downstream
pipelines,
but
in,
but
that's
really
not
a
great
pattern
actually,
because
if
you
have
like
a
real
library
that
people
can
use
throughout
an
enterprise,
you
should
be
able
to
say
I
use,
library,
X
and
anytime.
D
X
completes
then
run
mine
right,
so
we're
adding
the
concept
of
triggered
by
like
I'm
triggered
by
this
upstream
thing.
I
depend
on,
but
that's
in
the
edge
case.
We
don't
need
to
worry
about
right
now,
but
I
think
it's
okay
to
say.
If
my
pipelines
running
I,
don't
know
what's
going
on
with
downstream
pipelines.
That's
that's
an
acceptable
to
say:
okay,.
C
C
A
D
Yeah
yeah
I,
just
so
the
question
here:
Scott
is
the
one
that's
in
the
middle
on
the
bottom
right.
What?
What
is
that
just
made
up
data
that
the
fact
that
yeah
yeah
it's
made
up
right
right?
That's
one!
You
probably
wouldn't
have
that
downstream
data
to
write,
like
I,
think
you
handle
in
that
case
makes
sense,
but,
like
today
in
get
lab
when
my
pipelines
running
there's,
it's
not
gonna
have
a
concept
of
oh
and
then
there's
gonna
be
a
pipeline
after
me
like
it,
won't
know
that
got
it
anyway.
D
C
A
A
That's
a
good
question:
I
wondered
about
this.
I
thought
like
may
not
be
like
mainly
main
case,
though
I
like
the
idea.
Windham,
the
no
stack
and
not
like
shown
next
to
each
other
is
similar
to
the
comments
in
request
beers
inside
the
sidelines
sort
of
a
race
for
a
second,
but
there
at
some
point.
You
have
an
extra
number
in
there,
so
I
hope
you
could
use
that
better.
A
C
A
A
C
D
C
A
C
D
D
A
Thought
it
I
thought
it
animated,
but
this
is
good
as
well.
This
is
actually
more
simple
yeah.
This
is
good.
This
will
be
nice,
and
then
you
know
if
it
says
two
more
down
strings.
If
you
click
that
okay,
you
then
go
towards
the
pipeline
detail
page
because
we
cannot
go
into
you
know
expanded
ever
more.
It
will
be
crazy.
Oh.
D
D
Exactly
so,
you
can
see
all
the
gas
streams
then
yeah
then
you'll
be,
and
that
eventually
not
this
release,
but
soon
is
gonna,
have
evidence
scroll
built
in
in
a
way
that's
much
more
maintainable
like
I.
Don't
want
infinite
scroll
on
this
little
tiny,
you,
okay,
awesome!
This
was
really
really
useful.
Thank
you.
Scott
for
for
volunteering,
yeah.