►
From YouTube: Discussion around CI features - Veethika and Michael
Description
catch a glimpse of the new merge train index page.
A
To
give
an
intro
for
the
recording,
so
we
are
like
syncing
for
the
cicd
pipeline
and
other
ideas
between
me,
michael
from
developer,
eventualism
and
vtca
as
a
ux
designer
and
we're
gonna
think
what's
what's
coming,
what
ideas
are
in
there
and
yep?
I
kind
of
I
had
a.
I
had
a
coffee
chat
on
monday
with
christian,
a
community
member
who
was
working
at
dm
tech.
A
A
A
So
basically
that
you
know
that
when
this
job
finishes
in
the
first
stage
it
will
jumpstart
or
kickstart
a
job
which
is
in
the
fifth
or
sixth
stage.
In
the
end-
and
I
was
wondering-
or
we
were
wondering,
one
point
is
improving
the
documentation
and
chris
christian
said
he.
He
will
be
working
on
that
like
having
the
the
plain
pipeline
view
and
maybe
the
the
duck
view
or
deck
view,
and
just
saying
hey.
A
This
is
how
it
works,
because,
right
now
we
have
a
huge
colored
image
of
of
the
directed
exactly
graph,
but
it's
really
hard
to
understand
why
I
want
to
use
that.
So
this
is
one
part
of
the
story,
and
the
other
thing
is
that
the
the
needs
arrows
from
the
ci
pipeline
editor
are
probably
a
good
idea
for
the
main
pipeline
for
you
at
runtime,
and
I
was
wondering
if,
if
I
think
there
is
something
already,
but
I
was
wondering
if
you
have
more
insights.
B
Sure
so
I
mean
what
goes
on
on
the
pipeline
visualization,
which
is
present
today,
it's
mostly
in
the
area
of
pipeline
authoring,
so
I
know
that
they
are
trying
to.
I
mean
they're,
taking
small
steps
towards
achieving
their
goal,
and
I
think
recently
the
lines
were
removed
if
I'm
not
wrong,
because
they're
they're
working
in
the
background
enabling
a
few
things
and
that's
the
first
step
that
they
have
taken.
B
A
B
B
Okay,
so
these
are
the
six
actionable
ones
that
we
have
shortlisted
from
the
solution.
Validation,
exercise-
and
let
me
let
me
quickly
scan
through,
like
which
ones
are
relevant
for
the
graph,
so,
for
example,
for
the
identification
of
pipelines
and
jobs,
some
users
shared
like
what
they
feel
about
how
they,
how
they
usually
identify
them,
then
highlighting
the
critical
path
with
graph.
This
is
something
that
we
are
planning
to
opening
these
yeah.
A
Their
job
took
15
seconds
for
some
reason,
but
the
average
turns
turns
around
to
10
seconds
and
if
there's
like
a
huge
offset,
which
is
two
times
at
the
time,
this
could
be
visualized
in
a
different
way
and
saying
hey.
This
is
red
and
this
happened.
Maybe
maybe
we
can
also
count
this
and
say
it
happened
not
only
once
or
twice,
but
in
the
past
week
it
happened
20
times,
and
this
is
an
indicator
to
say:
hey
dear
user,
or
do
you
like
visitor
to
this
this
page?
A
A
A
Typically,
a
weather
map
has
been
used
for
network
traffic
at
a
huge
isp
or
provider.
Saying
hey
this
respect,
this
link
is
using
so
much
traffic,
it's
red,
but
luckily
the
the
backup
link
is
taking
the
rest
of
the
traffic.
So
it's
it
allows
to
to
immediately
see
when
you're,
using
more
than
95
of
your
95
percent
of
your
given
bandwidth,
because
normally
you
pay
more
than
that.
If
you
stay
up
on
using
that,
but
different
story
yeah.
B
A
A
I
have
some
screenshots,
but
I
cannot
share
them
and
typically
it's
really
hard
to
draw
a
line
from
the
from
the
top
to
the
bottom
and
then
going
back.
It
doesn't
help
much
and
if
you
draw
it
just
like
an
air
wire,
it
also
looks
a
little
strange
on
the
other
side.
I
want
to
see
that
I
don't
want
to
click
a
drop
down
and
say
I
want
to
enable
this
view.
A
B
Right
so
my
next
task
is
to
translate
all
these
insights
that
I've
received
and
I've
shared
a
link
with
you,
which
is
to
the
dovetail
project.
So
I
cannot
share
those
information
here
in
the
video
because
it
has
some
personal
information,
but
you
could
go
and
dig
deeper
and
read
the
more
detailed
insights
in
there.
The
highlights
so
I
have
to
translate
those
into
some
improvements
to
my
previous
design,
and
my
task
is
to
again
propose
like
how
we
are
breaking
that
into
iterations
and
in
that
process.
B
A
B
There
it
is
yes,
there
is
so
I
I
have
taken
up
this,
so
I
finally
taken
up
this
exercise
of
visualizing
merge
strain
and
I
put
the
issue
and
sigma
file
here,
but
I
would
also
share
my
screen
just
to
show
like
where
I've
reached
it's
it's
in
a
very
nascent
stage.
So
brutal
feedbacks
are
more
than
welcome
at
this
stage
because
of
course
it's
very
unpolished
all
right.
There
you
go
so
I
started
off
thinking
that
it's
just
going
to
be
a
visualization
of
the
train.
B
It
goes
and
gets
stuck.
It
gets
cute.
So
I
what
I
did
was
I
added
this
tab
here
that
shows
cute
merge
requests
but
individually
for
one
merge
request,
which
is
kind
of
a
part
of
like
for
which
a
merchant
pipeline
is
running.
What
are
the
informations
that
they
are
keen
to
look
at
so,
of
course,
which
merge
request
like
what's
the
how
they
just
want
to
identify
like?
B
What's
the
merge
request,
please
ignore
how
different
this
information
is,
because
it's
still
in
the
process,
then,
who
created
the
merge
request
and
what's
up
with
the
pipeline,
the
moisture
in
pipeline?
That's
running
for
this,
mr
and
a
way
to
get
into
the
pipeline
from
here
itself
and
investigate
more
and
how
much
time
to
merge.
So
I've
put
it
very
crudely
right
now
and
I
would
involve
the
technical
writers
but
like
what's
the
eta
like
when
should
I
expect
this
to
be
merged,
and
this
is
a
very
approximate
figure.
A
A
View
but
maybe
combine
started
at
or
it
should
be
a
relative
time
because
I
don't
want
to
translate
in
my
head,
started:
4
hours
and
10
minutes
ago
estimated
time
to
merge,
35
minutes
or
something
like
that,
so
you
have
both
numbers
in
the
same
line
or
in
the
same
visual
view
when
you're
looking
at
it.
So
I'm
reading
line
by
line
I'm
saying
okay,
this
is
the
the
much
request
id
yeah.
I
want
to
click
on
that.
I
personally
don't
remember
the
numbers.
I
want
to
read
the
title,
which
is
rough.
A
A
B
Perfect,
thank
you
so
much
for
that
yeah.
I
I
would
look
at
improving
that
and
the
next
thing
that
I've
explored
is
like
how
the
cued
merge
request.
Tab
would
look
like
so
right
now.
I
have
very
less
information,
I'm
not
even
sure.
If
this
position
column
is
like
important
at
all,
because
it
would
be
kind
of
implied.
B
But
let's
say
if
I
have
about
100
and
I'm
scrolling,
then
would
I
be
interested
in
the
position
there,
so
I'm
giving
this
option
to
remove
while
users
are
looking
at
the
the
cued,
mrs
here
in
the
list,
because
they
might
think
otherwise
they
want
to
do
much
immediately,
maybe
because
they
are
not
up
for
waiting
for
such
a
long
time.
So
they
could
do
that
from
here,
and
this
is
something
very
experimental.
I'm
not
even
sure
it's
a
requirement
and
it's
going
to
add
some
value.
It's
just
I.
A
Option
too,
because
sometimes
sometimes
the
request
is,
can
you
speed
up
the
mergers?
I
have
no
idea
how
to
do
that.
I
could
probably
skip
the
merge
train.
Remove
the
protection
from
the
master
main
branch,
merge
it
and
then
protect
it
again,
but
if
I
could
just
like
simply
change
the
priorities
or
maybe-
and
this
is
a
different
feature
request-
when
I'm
merging
some
when
I'm
adding
something
to
merge
train,
I
usually
get
the
feedback
edited
position
whatever
and
I'm
like.
I
have
no
idea
what
this
means.
A
A
I
don't
know
how
this
works
in
the
back
end,
but
it
should
probably
fire
an
update
and
prevent
some
race
conditions,
but
I
really
would
love
to
have
just
saying:
okay,
this
one
is
now
the
first
one
because
the
blog
post
needs
to
be
published
and
the
handbook
updates
need
to
wait.
For
example,
right,
probably
if
you
need
to
break
it
down
in
an
in
mvcs
or
like
in
smaller
iterations,
this
is
something
which
comes
at
last.
I
think
it's
it
takes
lots
of
resources
to
implement.
B
Yeah
we
have,
we
have
an
effort
going
on
like
right
now,
which
is
around
re-architecturing.
This
whole
merge
train
architecture
and
I
think
yeah
you're
right
that
this
has
to
be
taken
up
at
the
end.
But
at
least
maybe
I
should
start
this
discussion
so
that
while
they're
taking
a
look
at
so
many
things,
they
might
even
accommodate
something
that
could
be
useful
later.
A
I'm
just
saying
when
you're
proposing
it
and
saying
I
want
this
to
happen,
but
in
the
second
sentence
say
it
should
be
in
the
design
and
it
could
be
static.
So
I
I
wouldn't
expect
to
to
move
it
around
in
the
current
state.
Even
if
you
don't
provide
me
a
tooltip
or
give
me
the
hint
that
it's
possible.
A
So
if
we
have
a
static
interface
and
listing
this
seeing
this
in
line,
because
if
I
only
see
like
three
items,
I
know
oh,
it's
totally.
Fine.
If
I
see
oh,
it's
got,
got
20
20
trains
inside
the
merch
train.
It's
like!
Oh,
something
is
wrong,
and
one
thing
I
would
also
add,
is
cute.
Merch
request
is
34.
Currently,
if
this
exceeds
a
a
certain
number,
maybe
maybe
mark
the
number
or
the
background
in
in
in
a
warning
or
critical
state.
So
like
cubed,
merge
request
is
greater
than
30.
A
This
is
more
monitoring
related,
so
when
the
queue
grows
and
doesn't
get
doesn't
get
back
to
zero,
something
is
off
or
it's
expected,
but
it
it
could
be
a
good
way
to
indicate
that
as
a
warning
or
as
an
info
or
just
to
just
to
say,
hey
next
to
the
things
above,
there
is
still
something
in
the
queue.
I'm
not
I'm
not
100
sure
what
I'm
proposing
now,
but
it's
I
need
that,
and
I've
been
building
systems
where
the
queue
was
running
full
all
the
time
and
the
users
said
well.
A
A
Or
it's
expected
could
also
be
the
case,
but
at
some
point
you
probably
want
to
know
something
is
blocking
my
deployment
or
my
my
ci
cd
pipeline,
and
this
could
be,
could
be
a
good
indicator
to
to
see
that
this
metric
could
be
also
being
used
for
the
director
level
cicd
dashboard,
which
we
had
discussed
a
while
ago.
I
think
in
release
management
with
jackie
and
and
ryana.
A
A
A
Yeah
right
also
point
which
probably
comes
later,
but
it's
it
would
be.
It
would
be
super
useful
to
have
this
as
a
as
an
orchestrator
as
an
action
interface,
I'm
personally
not
a
fan
of
navigating
into
much
request.
Only
if
I
want
to
see
the
details,
if
I
want
to
take
action
with
a
merge
it
or
remove
it
or
do
something
it
should
be
in
there.
B
A
A
A
B
B
Not
that
doing
that
at
all
so,
okay,
so
this
is
what
it
is
right
now
and
since
you
have
to
move
to
another
meeting,
I
think
I
I
would
still
be
receiving
feedback.
If
you
have
anything,
you
can
just
put
a
comment
on
this
figma
and
I'll
read
them,
but
this
was
a
really
good
session
and
thank
you
so
much
for
so
many
feedback
on
this
one.
B
Sure
I
would
love
to
so.
Let's
talk
about
this
section.
This
is
the
page
which
I
have
kind
of
organized
a
little,
so
it's
cleaner
to
put
comments
on
that.
Could
there
be
anything
else
that
could
be
a
variable
when
looking
at
the
train
visualization?
So,
for
example,
here
I
have
put
up
something
to
select
the
target
branch,
but
is
there
something
else
that
I'm
missing
out
on
probably.
A
I
don't
know
where
I
would
move
it,
but
I
would
be
moving
moving.
The
currently
running
merge
requests
at
the
bot
at
the
top,
because
this
is
this
is
what
I'm
interested
in
okay,
I
like
that.
I
can
select
the
target
branch,
so
this
this
is
something
I
probably
would
have
asked
at.
The
later
point
saying:
hey,
maybe
I
want
to
see
which
which
branches
is?
A
A
If
the
train
history,
I'm,
I
was
I'm
not
sure
if,
if
I
want
to
see
the
history
or
the
cute
merch
requests
by
default,
this
is
this
is
something
to
find
out
right,
because
sometimes
the
history
is
important
to
me
to
see
how
often
or
something
failed.
But
when
I'm
coming
there
and
saying
hey.
Where
is
my
job?
Oh
it's
not
there!
It's
in
the
cute
list,
then
I
don't
want
to
switch
the
top.
B
A
Yeah
this
this
could
be
a
this
would
be
interesting
because
I
probably
would
always
navigate
into
the
cute
list,
because
I
want
to
see
the
whole.
It's
not
a
pipeline.
It's
it's.
It's
merge
trend
view,
but
I'm
kind
of
like
connecting
the
running
queue
with
the
pending
queue
in
my
head
and
then
like
have
my
own
list.
B
One
thing
that
I'm
planning
to
do
now
is
how
I
would
put
some
sort
of
an
indicator
which
is
closely
related
to
the
same
visualization,
but
on
the
mr
widget,
so
pedro
and
his
team
they're
working
on
redesigning
the
mr
widget
and
I'm
using
the
new
design
to
see
where
we
can
place
some
sort
of
an
indicator
about.
What's
the
situation
with
the
merge
train
to
which
you're
adding
or
once
you
add
that
like
at
what
position
is
that
and
how
many?
B
How
much
time
do
you
have
to
wait
on
your
merge
request
to
get
merged
and
what
else
yeah?
And
I
also
have
to
think
about
what
message
which
you
mentioned
here
like
depending
on?
What's
the
number
of
queued,
merge
requests?
We
should
be
able
to
give
some
sort
of
notification
on
the
merge
request.
Right
like
there
would
be
situations
when
it
would
be
a
hard
stop
like
we.
We
cannot
take
any
more
merge
requests
to
queue
for
this
much
train
or
I
know,
there's
no
heart.
B
Stop
that
exists,
as
of
today
like
there's
no
limit,
but
maybe
that
should
something
should
be
in
place
just
for
a
precaution,
and
we
can
also
set
a
bar
for
ourselves
like
at
these
much
at
this
number.
Maybe
we
should
just
give
a
soft
warning
to
users
that
it
wouldn't
be
very
ideal
if
they
add
to
the
train.
At
this
point.
A
Yeah
they
can
so
you
when
I,
when
I'm
like,
taking
the
action
of
adding
something
to
the
merge
train,
I'm
expecting
it
to
work,
but
I
would
would
love
to
have
an
indicator
and
saying
hey.
There
are
like
20
much,
mrs
in
the
merge
string
currently
running
and
mine
is
cued
now
and
if
the
queued
position
and
for
me
the
position
is
not
it's
not
really
relevant.
A
Which
is
not
possible
for
me
and
I'm
expecting
it
to
merge
sooner,
because
the
deployment
needs
also
be
triggered.
Deployment
means
copy
copying
the
the
thing
to
gcp
cloud
and
restarting
something
and
whatever,
and
it
takes
five
minutes
again,
and
I
could
imagine
that
we
provide
an
action
in
the
metric
quest
which
allows
you
to
move
it
at
the
first
position,
so
you
can
influence
the
behavior
from
the
merchandise
widget
or
in
the
first
iteration,
just
linking
there
to
the
to
the
overview
and
saying
hey,
we
queued
it
at
position.
15..
A
A
Because,
right
now,
when
I'm,
when
I'm
using
quick
actions
now
because
roman
told
me
everything
around
about
that,
so
I
slash
merge
and-
and
it
says
here-
added
to
merge,
train
at
position
seven
and
I'm
like
yeah,
okay.
I
have
no
idea
what
happens
next.
This
may
sound
a
little
blunt,
but
it's
like
the
raw
impressionist
thing.
I
don't.
I
don't
really
know
what
a
merge
trend
does.
In
the
background.
I
have
no
idea
and
if
I
have
a
visualization
of
saying
hey,
there
are
like
position.
A
A
35
minutes
works
for
me
that
works
in
my
maintenance
window,
for
example,
because
I've
told
customers
there
will
be
a
downtime
between
five
and
six,
so
no
monitoring
alerts
and
nothing
else,
because
we
need
to
deploy
a
new
software
release
because
bug
fixes
or
whatever,
but
still
my
other
deployments
are
my
other
merge.
Trains
are
still
running,
but
I
want
to
have
this
speed
up,
and
this
brings
me
back
to
my
priority.
A
A
B
Very
good
suggestion,
so
I
have
some
interpretation
of
what
you
just
said.
So
how
about
like,
when
we're
presenting
with
some
option
to
users,
which
is
add
to
merge
train
starter,
merge
train
as
opposed
to
emerge
immediately,
maybe
depending
on
how
much
time
it
would
take
for
it
to
merge.
If
you
add
it
to
the
train,
if
that's
substantial,
then
that
button
could
appear
in
red,
I
mean
red
is
going
to
be
very
it's
for
danger,
but
maybe
some
warning
color.
A
A
A
We
need
to,
we
need
to
to
use
a
color
set,
which
is
which
works
for
everyone.
So
if
you're
color
blind,
you
cannot
use
orange
or
yellow,
but
this
this
needs
to
be
built
for
accessibility
with
maybe
icon
shapes
and
different
color
sets,
which
we
have
been
using
for
the
the
incidents
and
the
alert
management
for
the
monitor
group
and
also
security
dashboards,
use
these
markers
already,
and
I
think
I
don't
know
if
we
use
the
small
icons
or
how
did
the
buttons
look
like.
A
But
yes,
if
there
is
like
an
expected
delay
of
whatever
more
than
30
minutes
could
be,
it
could
be
a
hardcoded
default
or
configurable
default.
Saying
hey.
This
is
now
orange
because
you
there
is
an
expected
wait
time
of
45
minutes,
and
everyone
in
slack
is,
is
asking
you.
When
is
the
release
live
because
customers
are
asking
where
in
read-only
mode
currently
and
the
backend
is
not
functional
and
we
want
to
sell
something
or
we
want
to
build
something.
A
And
just
as
an
example,
when
gitlab.com
does
maintenance
or
the
deployment
needs
to
happen
or
we're
all
waiting
for
a
security
fix
because
we
know
it
gets
gets
exploited
already.
I
think
it's
critical
to
have
the
option
of
saying:
hey
get
an
estimation
and
if
it
doesn't
match
our
expectations,
we
need
to
have
a
different
emergency
workflow
applied.
A
For
example,
this
could
be
documented
and
saying:
okay,
the
typical
workflow
is
click
deploy
or
click
merge
and
it
the
merge
train
does
something
and
35
minutes
later
it
happened,
but
if
there
is
nothing
happening
after
45
minutes,
it's
bad
so
having
the
the
exp.
Having
the
the
estimation
of
when
it's
supposed
to
merge,
it
would
be
really
helpful.
B
A
This
this
looks
also
interesting.
I
know
that
the
the
pipeline
table
is
has
gotten
huge
and
like
having
having
pipeline
priorities
and
and
other
things,
yeah
yeah.
I
think
I
think
it's
it
not
only
adds
too
much
trains.
What
we're
discussing
now.
It
could
also
like
influence
the
normal,
merge,
probably
or
merge
when
the
pipeline
succeeds.
B
A
How
long
a
deployment
would
take
when
is
when?
Can
I
expect
this
to
be
in
production,
because
the
last
deployment
took
pipeline
took
five
minutes?
Deployment
took
two
minutes.
Seven
minutes
can
I?
How
can
I
estimate
that
like?
When
is
the
website
live
or
when
is
the
bug
fix
for
the
website?
Live?
It's
it's
not
directly.
In
the
cicd
pipeline
view.
A
Now
we
are
basically
on
the
cd
side
at
the
end,
but
yeah
I
totally
loved
the
numbers
and
just
fetching
the
metrics
and
storing
them
and
comparing
them,
but
I
think
it
would
be
helpful
to
to
know
that,
and
if
I
see
seven
minutes
I
say
yeah,
I
can
do
it
in
five
minutes.
I
need
to
optimize
away
two
minutes
because
pipeline
is
not
good
or
I
think
there
was
a
recent
incident
with
nothing
it
an
incident.
We
had
a
problem
with
our
pipelines.
A
B
B
A
A
So
I
can
like
go,
go
back
in
there
and
share
my
thoughts
around
as
if
a
specific
proposal,
in
fact,
if,
if
it
helps,
if
not,
we
can
do
it
async
still,
I'm
I'm
open
to
to
discussing
things
also
in
a
wider
group,
but
not
like
for
two
hours
but
more
like
sometimes
it's
hard
to
to
write
things
down
which
you
visualize
for
me
now,
and
I
just
keep
thinking
about
it.
For
me,
this
is
super
helpful.
B
Great,
so
I
what
I
would
do
after
making
these
improvements,
I
would
record
a
video
like
I
always
do
and
yeah.
So
at
least
I
would
put
a
slack
post
tagging
you
of
course,
and
would
record,
would
put
the
video
on
the
on
unfiltered
as
well,
and
let's
see
where
we
would
want
to
discuss
the
ideas
from
there
and
if
you
would
want
to
have
a
discussion
with
the
community
members
as
well.