►
From YouTube: GitLab 14.2 Kickoff - Verify:Pipeline Execution
Description
https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/68
Welcome to Verify Pipeline Execution14.2 Kick Off! This group is responsible for GitLab CI, such as pipelines, pipeline processing, and variables. As well the category of Merge Trains. In14.2 we are exclusively focused on helping our users understand CI minutes better than ever before. Design will be focused on the usability of merge trains and pipelines.
A
Welcome
to
the
pipeline
execution
14.2
kickoff,
my
name
is
jackie
porter
acting
product
manager
for
the
pe
group
here
at
git
lab.
As
a
reminder,
this
group
is
responsible
for
all
of
get
lab
ci,
which
is
pipeline,
processing
and
pipeline
experience,
as
well
as
the
category
of
merge
trains.
I'm
joined
here
by
the
pe
product
designer
vitica
and
in
14.2
we're
exclusively
focused
on
helping
our
users
understand
ci,
minutes
user,
as
well
as
removing
some
of
the
pain
points.
Around
pipelines,
merge
trains
and
com
availability.
A
B
Sure,
jackie
and
first
of
all,
thank
you
so
much
for
highlighting
the
theme
for
the
milestone.
Some
of
the
issues
that
I'm
I'll
be
focusing
on
this
milestone
are
the
following.
This
is
the
first
one
which
says
show
pipeline
iii
in
pipeline
in
pipelines
page.
So
users
want
to
embed
the
build
number
in
windows,
resource
files,
specifically
the
file
version
field,
and
this
can
take
only
16
bit
integers
and
in
many
cases
the
id
for
the
pipelines.
B
It
has
already
exceeded
16
bit
and
thus
it
kind
of
breaks
the
window
versioning
schema.
So
we
don't
expose
the
iid
anywhere
in
the
ui
today
and
to
kind
of
deal
with
this
problem.
One
of
the
proposed
solution
is
that
we
would
be
doing
that,
especially
on
the
pipeline
index
page
and
we'll
be
exploring
solutions
in
this
issue.
Yeah.
A
B
All
right
thanks,
jackie,
the
next
one.
The
next
issue
says
use
danger
for
merge
button
if
pipeline
has
been
skipped
so
when
using
ci
skip,
users
are
not
made
aware
of
the
status
of
the
most
recent
pipeline
run.
That
was
not
skipped,
and
this
could
lead
to
a
merge
conflict
very
easily.
So
a
solution,
we're
exploring,
is
to
check
the
status
of
the
last
non-skip
pipeline
and
change
the
button
state
to
communicate
it.
B
Just
to
give
an
example:
let's
say
the
last
landscape
pipeline
failed,
then
probably
the
treatment
or
the
variant
that
we'd
be
looking
at
for
the
merge
button
could
be
danger
or
warning
yeah
and
the
third
one,
which
is
the
last
one
it
says,
triggered
pipeline
display
incorrectly.
So
today
we
just
put
the
triggered
badge
for
a
job
based
on
trigger
request,
and
this
is
irrespective
of
whether
the
trigger
is
an
api
or
something
else.
B
A
A
A
As
mentioned,
14.2
is
really
about
building
an
experience
around
managing
ci
minutes
and
helping
them
understand
their
consumption
and
in
14.2
we
have
a
couple
of
back
end
issues
and
front-end
issues
to
help
build
these
two
charts.
One
of
them
is
the
ci
minutes
usage
by
months
and
ci
minus
issues
by
product,
so
I'm
really
excited
to
help
our
users
understand
their
consumption,
because
current
state
is
just
this
kind
of
burn
down
of
this
bar
of
how
their
minutes
are
today.
So
really
excited
about
this
view
that
we're
enabling
users.
B
A
A
The
team
will
kind
of
determine
what
what
view
this
will
will
take
presence
when
they
start
creating
it.
The
architecture
blueprint
process
is
an
internal
process
where
there's
gris
assigned
from
all
parts
of
the
organization
and
they
document
the
technical
and
product
underpinnings
of
that
functionality.
A
A
A
One
of
them
is
this
time
decay
blueprint
that
we're
thinking
about
delivering,
also
in
14.2,
so
something
to
to
consider
whenever
you
look
at
our
issue
and
then
also
informative
issues
are
another
top
theme
that
we're
always
trying
to
bring
down
in
pipeline
execution.
So
if
you
take
a
look
at
our
our
pipeline
execution
planning
issue-
and
you
see
other
top
priority
issues,
these
are
things
that
we're
always
trying
to
deliver
in
our
in
our
group
as
well.
Well,
we're
super
excited
for
14.2.