►
From YouTube: CI category direction update - Mar 2021
Description
Referenced in the video:
- https://about.gitlab.com/direction/verify/continuous_integration/
- https://about.gitlab.com/blog/2021/02/22/continuously-improving-ci-lovability/
A
Hi
everyone,
my
name,
is
tali
yaeger,
get
lab
product
manager
for
continuous
integration.
Today,
I'd
like
to
walk
you
through
some
updates
on
the
ci
category
direction
page
as
well
as
talk
through
why
we
have
made
a
change
on
our
category
maturity,
so
I'll
link
to
this
direction
page
at
the
bottom
of
this
video.
A
If
you
take
a
look
at
what's
the
section
for
what's
next
and
why
you'll
see
that
in
the
first
paragraph
we
talk
about
the
investment
that
we're
making
now,
it
is
actually
our
primary
focus
to
strengthen
the
availability,
reliability
of
gitlab.com,
and
that
involves
optimizing.
The
performance
of
the
database
queries
in
ci
pipelines.
A
A
In
addition,
we're
also
working
to
enhance
our
pipeline
validation
service
to
ensure
that
performance
on
gitlab.com
is
not
impacted
by
improperly
configured
pipelines
and
jobs.
So
what
that
means
is
both
of
these
efforts
are
our
top
priority
currently,
and
we
in
fact
have
prioritized
this
over
plans
to
improve
usability
with
and
even
promise
features,
which
are
the
two
things
that
we
had
originally
planned
for
the
first
couple
quarters
of
this
fiscal
year.
A
Setting
now
being
able-
that's
not
to
say,
we
want
to
hinder
the
ability
to
to
merge
whenever,
whenever
possible.
In
fact,
there
are
times
where
you
have
pipeline
must
succeed,
enabled,
but
the
configurations
resolve
to
an
empty
pipeline,
because
no
jobs
need
to
be
run,
and
we
have
a
feature.
We've
identified,
that
we
want
to
also
work
on
in
this
first
half
of
the
fiscal
year,
which
is
allowing
you
to
still
merge
your
mr,
even
if
no
jobs
need
to
run
for
that
pipeline
and
an
example
of
that
would
be.
A
That
condition
would
prevent
you
from
merging
that
mr
and
we're
trying
we're
working
to
solve
for
that
in
this
issue
to
allow
you
to
still
merge
okay,
so
that's
what's
next
and
why
the
other
thing
I
wanted
to
highlight
is
our
maturity
plan.
So
recently
we
changed
our
maturity
from
lovable
to
complete.
For
a
couple
reasons,
we
did
a
research
project
for
category
maturity
scorecard
for
ci
and
in
this
research
project
we
interviewed
both
software
developer
persona,
as
well
as
the
devops
engineer
persona,
and
we
had
them
evaluate.
A
We
gave
them
a
project
and
said
now
make
some
change
to
the
project.
How
would
you
how
easy
and
observe
how
easier
it
was
for
them
to
trigger
a
pipeline,
and
then
in
the
second
one
we
had
a
project
that
had
a
problematic
job
that
failed
and
we
observed
how
easy
it
was
for
our
research
participants
to
find
the
the
delay
in
their
pipeline
the
issue
with
the
job
and
how
easy
it
was
to
troubleshoot.
A
A
Scale
is
for
a
content,
a
category
maturity
card
of
of
at
least
3.95.
It
would
fall
into
the
maturity
rating
of
lovable.
Now
that
is
consistent
with
another
research
project
that
happened
about
the
same
time
that
is
summarized
in
an
unfiltered
blog
that
jackie
porter,
published
at
the
end
of
february
and
I'll
link
to
this
blog
at
the
bottom
of
this
video
and
what
she
found
in
this
research,
which
was
conducted
over
a
six
week
period
interviewing
our
customers
to
learn
about
their
adoption
journey
with
gitlab.
A
There
were
three
key
findings
summarized
in
this
blog
one
is
that
gitlab
is
leveled
by
developers
and
that's
consistent
with
what
we
found
in
the
jobs
to
be
done,
that
we
researched
and
how
high
it
scored.
Above
four,
however,
we
decided
to
move
our
ci
category
maturity
down
to
complete,
because
two
of
the
other
findings
in
this
research
revealed
areas
in
which
we
can
mature,
improve
and
they're
listed
here.
A
I
won't
read
through
them,
but
you
can
dive
into
this
in
this
blog,
but
so
our
path
back
to
maturity
is
listed
here,
as
well
as
in
our
category
direction.
Page
as
far
as
the
things
we
want
to
do
to
progress
from
to
the
next
maturity
target
of
lovable,
which
is
working
on
our
variables
and
artifact
bugs
and
resolving
tech,
debt
related
to
a
merge,
request,
widget
and
then
one
of
the
findings
that,
from
that
research
project
about
the
adoption
journey,
mentions
that
it's
hard
to
have
visibility
into
jobs
at
scale.
A
We
know
that
there
are
features
that
we
can
deliver.
That
is
already
a
part
of
our
vision
items
for
the
fiscal
year,
which
is
plans
to
help
users
better,
monitor
and
understand
their
pipelines.
It
could
be
details
about
a
pipeline
activity
such
as
job
duration
or
metrics,
about
historical
pipelines,
so
that
better
decisions
can
be
made
based
on
the
trends
of
pipelines.