►
From YouTube: GitLab 13.12 Kickoff - Verify:Continuous Integration
Description
Links to GitLab pages and issues discussed:
- https://about.gitlab.com/direction/verify/continuous_integration/
- https://gitlab.com/gitlab-org/gitlab/-/issues/320981
- https://gitlab.com/gitlab-org/gitlab/-/issues/290961
- https://gitlab.com/gitlab-org/gitlab/-/issues/277393
Usability issues delivered recently:
- https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=all&label_name[]=group%3A%3Acontinuous%20integration&label_name[]=SUS%3A%3AFY22%20Q1%20-%20Done
A
A
And
we're
here
to
talk
about
the
the
work
we
have
planned
for
the
upcoming
milestone.
13.12..
Can
you
see
my
screen
vitica
yeah,
okay
and
I
the
13.12
planning
issues
open?
Yes,
okay.
So
before
I
dive
into
some
of
the
issues
that
we're
going
to
be
focused
on,
I
want
to
go
back
and
talk
about
what
we
have
identified
on
our
category
direction.
A
Now,
one
of
the
things
I'm
going
to
talk
you
through
in
a
moment
is
in
addition
to
stabilizing
on
the
usability
of
our
features,
and
actually,
as
part
of
that
are,
is
work
that
we're
doing
to
improve
focus
on
ui,
polish
and
and
usability
that
would
is
relevant
to
our
systems.
Usability
scales
such
what
we
call
suscor
I'll,
come
back
to
that.
A
So
there's
a
couple
issues
that
I
wanted
to
mention,
and
then
we
want
to.
I
want
to
spend
the
remainder
of
the
time
talking
about
ui
improvements
that
we're
making
one
of
the
issues
we're
targeting
for
13.12
is
mentioned
here,
which
is
issue
number
the
issue
related
to
allowing
you
to
disable
the
default
behavior
of
merge
immediately.
A
Merge
immediately
is
there
to
allow
emergency
patches
to
bypass
if
safeguards
such
as
merge,
request
pipelines
or
merge
strains,
but
for
some
organization
you
do
want
to
have
the
flexibility
to
turn
that
off,
and
we
have
that
in
this
issue
to
what
the
setting
does
it.
It
mimics
the
current
behavior
that
is
not
a
project
setting
and
this
issue
will
make
that
into
a
project
setting
so
that
you
could
disable.
A
Okay,
okay
and
it
is
an
option-
that's
going
to
be
enable
the
default.
If
you
don't
make
any
changes
it,
it
mirrors
the
behavior
that
happens.
Now,
it's
just
right
now,
you
don't
have
the
option
to
disable
the
other
issue
that
we're
going
to
be
working
on.
That
in
13.12
is
notifying
users
when
their
ci
usage
falls
behold
below
a
threshold.
A
B
All
right,
so
here's
the
list
of
the
issues
that
we
tackled
in
the
previous
milestone
I
mean
in
in
the
ongoing
one
which
is
about
to
end,
and
I
have
them
open,
but
not
in
sequence.
So
please
bear
with
me
all
right.
So,
first
one
is.
It
was
an
issue
which
was
opened
very
recently,
like
you
can
see
here.
It
says
one
week
ago,
so
they
said
the
tooltip
positions
in
python
job
page.
B
There
was
some
problem
with
that
like
when
you
are
hovering
over
a
job,
so
the
tooltip
appears
and
what
it
did
was.
It
was
including
the
job
name
which
was
right
above
it
so
to
tackle
this
very
quickly.
A
merge
request
was
opened
by
sam
and,
as
you
can
see,
this
is
how
it
used
to
appear
like
it
used
to
cover
the
job
beneath
or
above
it.
Now
it
appears
on
the
side.
So,
okay,
yeah.
A
And
we
did
that
one
really
quickly
right
yeah,
and
so
we
never
got
a
chance
that
some
of
these
you'll
notice,
folks
you
we
never
had
a
chance
to
talk
about
them
in
the
last
kickoff
video,
and
we
do
want
to
showcase
these
because
we
we,
we
are
giving
a
lot
of
focus
on
usability
and
we're
doing
these
some
of
in
this
case
as
they
come
in
okay,
vitica.
Let's
look
at
the
next
one.
B
And
the
next
one
was
again
something
very
recent
which
I
noticed
that
there
are
different
terminologies
which
were
used
for
time
on
the
job
on
the
pipeline
index
page
on
the
job
index
page
like
here
it
says,
duration.
Here
you
say
it's
timing
and
on
the
job
detail
page,
we
said
duration
and
timeout,
so
again,
very
quickly,
marcel
opened
an
mr,
and
now
we
are
trying
to
make
like
both
the
index
page.
B
Where
triangle
we
have
changed
it
from
timing
to
duration,
and
that's,
I
think
this
solves
about
the
major
part
of
the
issue
then
moving
to
the
next
one.
This
one
here
says
improve
ux
on
off
toggle
for
ci
cd
left
now,
so
we
have.
We
have
this
option
to
switch
on
and
off
the
option
of
ci
cd.
That
appears
on
the
on
the
left
side,
navigation,
the
main
navigation,
but
the
way
this
trigger
was
placed
in
the
settings.
B
It
was
not
very
easy
to
figure
out
like
what
is
it
there
for
and
now
it
is
kind
of
fixed.
So
it
says
what
it
should
like.
It
says
the
name
of
the
section
that
it
enables
on
the
navigation
which
is
cicd,
and
this
has
been
taken
away
from
this
repository
section
it
it
has
now
been
placed
outside
of
it,
so
that
users
don't
get
this
misconception,
that
they
would
be
enabling
something
within
the
repository
option
here
in
the
left
navigation.
But
they
would
be
enabling
something
like
a
very
different
menu
option.
A
B
The
next
one
is
tool
tip,
should
point
towards
the
active
menu
item
in
the
drop-down.
So
this
is
the
problem
that
we
are
facing,
like
the
tooltips
were
appearing
at
strange
places
sometimes,
and
it
was
difficult
to
understand
like
what
they
were
pointing
at
and
then
there
is
here's
the
fix
for
that.
So
this
has
also
been
taken
care
of
now
it
behaves
as
it
should
another
one
is.
Let
me
move
this.
B
It
was
just
communicated
like
a
normal
certified
set
of
list
of
jobs
to
the
user,
but
now
we
have
this
small
text
that
comes
here,
which
I
could
show
more
clearly
in
the
mr.
So
now
for
non-draft,
mrs,
you
would
be
able
to
see
this
text
that
says
merchant
pipeline
jobs
cannot
be
retried
so
that
they
don't.
They
are
not
left
guessing
like.
Why
is
it?
The
behavior
is
different
for
the
particular
set
of
jobs.
B
B
Yeah
sure
in
the
coming
milestone,
we'll
be
working
on
this
problem,
so
I
would
talk
a
little
about
how
this
came
into
our
attention
and
I
mean
how
this
whole
problem
statement.
It
kind
of
emerged.
So,
first
of
all,
there
was
an
issue
that
talked
about
introducing
a
new
action
for
in
the
pipeline
index
page,
so
I
mean
those
who
are
those
of
you
who
work
with
gitlab
cio
would
be
aware
with
the
pipeline
xp.
This
is
how
it
looks,
and
then
you
see
all
these
options
on
the
side.
B
I'm
not
exactly
the
way
you
see
here,
because
it's
a
proposal,
but
it's
similar
in
placement
and
looks
now.
The
problem
was
that
if
we
ever
plan
to
add
additional
action
to
this,
the
this
block
is
just
going
to
get
longer
horizontally
and
that's
not
what
we
really
wanted,
because
it
was
kind
of
eating
up
the
space
on
the
table.
So
we
wanted
a
solution
that
was
more
scalable
and
also
something
that
kind
of
very
clearly
speaks
as
to
what
is
the
primary
and
the
secondary
actions
there.
B
B
One
more
thing
that
this
design
would
be
doing
is
improving
the
performance
for
this
page,
because
what
it
does
is
it
kind
of
isolates
the
load
of
loading,
all
the
artifacts
for
the
page,
from
loading
of
the
page.
So
until
user
comes
here
and
clicks
on
this
kebab
menu,
the
artifact,
the
list
of
artifacts
would
not
be
loaded,
and
that
would
make
loading
of
the
page
faster.