►
From YouTube: GitLab 14.1 Kickoff - Verify:Pipeline Execution
Description
https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/67
Welcome to Verify Pipeline Execution14.1 Kick-Off! This group is responsible for GitLab CI, such as pipelines, pipeline processing, and variables. As well as the category of Merge Trains. In 14.1 we deliver some incredible features that will help our users see is to see a return on investment with GitLab via an investment in the foundations of CI Minutes.
A
Welcome
to
the
verify
pipeline
execution,
14.1
kickoff,
my
name
is
jackie,
porter
interim
product
manager
for
the
pipeline
execution
group
here
at
get
lab.
As
a
reminder,
this
group
is
responsible
for
get
lab.
Ci
such
as
pipelines,
pipeline
processing
and
other
great
features
to
deal
with
the
pipelines.
Experience
as
well
as
the
category
of
merge
trains.
A
I'm
joined
here
by
the
pe
product,
designer
vitica
and
in
14.1
we'll
be
delivering
some
incredible
features
that
will
help
our
users
begin
to
see
a
return
on
investment
with
git
lab,
which
is
seen
in
the
foundation
of
ci
minutes.
Vitica
will
dive
into
some
of
the
ux
priorities
that
she
has
on
her
docket.
That
will
shape
our
user
experience
as
we
begin
to
combat
things
like
pipeline
abuse,
as
well
as
update
us
on
some
of
the
work
that
she
has
related
to
variables.
Vitica.
B
Sure,
thanks
jackie,
so
in
the
previous
kickoff
video
we
touched
upon
how
we
were
going
to
conduct
a
ux
scorecard
exercise
on
variables
and
the
jobs
to
be
done
that
we
had
selected
was
controlling
the
scope
for
ci
cd
variables.
So
I
just
wanted
to
let
you
all
know
that
we
are
through
with
the
exercise,
and
we
spoke
to
about
five
users,
and
we
have
some
really
good
findings
at
hand
and
using
those
findings.
We
would
now
work
on
putting
together
a
proposal
for
redesigning
the
experience
with
variables.
A
A
A
For
our
users,
we
aren't
experiencing
to
be
a
disruption
in
the
current
user
experience
as
we're
reusing
the
same
patterns,
although
we
are
expecting
to
fix
some
of
the
inconsistencies
in
the
old
system
such
as
this
bug
that
we'll
be
also
investing
in,
which
is
a
a
correct
edition
of
the
ci
minutes,
so
that
the
notification
thresholds
that
are
enable
inside
of
ci
minutes
are
correct.
This
focus
on
ci
minutes
will
empower
our
users
to
effectively
see
how
their
consumption
is
progressing
and
manage
their
accounts
correctly.
B
Thanks,
jackie
yeah,
this
is
the
first
issue
that
I
would
be
talking
about,
and
so
recently
there
has
been
a
requirement
from
our
users
that
they
want
to
identify
the
projects
that
have
been
consuming
like
the
most
ci
minutes.
So
in
this
issue
we
would
be
providing
sort
of
an
mvc
solution
to
this
problem.
A
As
mentioned
earlier
in
the
introduction,
a
big
piece
of
pipeline
abuse
prevention
is
being
able
to
granularly
control
our
user
access,
different
components
of
ci.
This
is
a
great
entry
point
for
our
users
in
prevention
abuse,
but
also
controlling
legitimate
user
access,
so
really
excited
to
see
how
you
design
this
experience.
Fujika.
B
So
now,
what
one
thing
that
we
missed
was
the
banner
was
not
dismissible
until
now,
so
this
is
for
something
that
we
would
be
like
through.
This
issue
would
make
sure
that
the
banners
are
dismissible
and
users
could
just
close
it
and
continue
with
the
their
workflow,
which
is
not
related
to
gitlab
ci.
A
Thank
you
so
much
for
that
overview.
Fujika.
I'm
really
excited
for
some
of
your
design
priorities
in
14.1.
I
think
you're
working
on
some
high
priority
initiatives
related
to
pipeline
abuse,
and
I'm
excited
to
see
about
some
of
the
design
proposal
around
variables.
I
think
that
that
will
be
a
really
rich
experience
that
pipeline
authoring
will
get
to
work
on.
14.1
is
going
to
definitely
be
the
best
release.
Effort
for
us.