►
From YouTube: GitLab 14.00Kickoff - Pipeline authoring:Verify
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone-
this
is
dave
kovitz
from
the
pipeline
authoring
team,
and
this
is
14.0
kickoff
video.
As
always,
we
do
have
a
planning
issue
underneath
pipeline
authoring
group
issue,
number
15,
where
you
can
see
a
list
of
all
the
deliverable
items
and
the
fillers
that
we
expect
the
engineers
to
focus
on
to
begin
with
the
goals
of
the
milestones,
since
this
is
a
major
release
and
the
goals
of
this
milestone
is
breaking
changes
and
with
that
we
are
adding
some
bugs
and
technical
depth,
and
this
will
be
the
focus
of
most
of
the
release.
A
There
is
one
issue
that
I
want
us
to
the
most
wanted
to
focus
on,
which
is
to
add
three-stage,
temp
template
to
the
drawer
in
13.,
12,
we've
added
the
pipeline
door,
maybe
you've
seen
it.
The
pipeline,
though,
is
the
component
that
you
see
here
on
the
right
hand,
side,
and
it
appears
when
you
click
on
the
pipeline,
editor
and
start
adding
your
epic.
A
Another
thing
that
may
be
worth
mentioning
is
the
branch
elector.
The
branch
selector
is
the
feature
that
will
allow
users
to
to
work
on
the
pipeline.
Editor
that
I
just
show
from
different.
In
different
branches,
we
wanted
to
release
it
in.
In
the
last
iteration,
however,
we
were
able
to
detect
a
couple
of
showstopper
which
we
plan
to
address
in
this
iteration
and
hopefully,
once
those
will
get
resolved,
we'll
be
able
to
release
the
branch
selector.
B
B
So
in
this
milestone,
I
will
be
focusing
on
creating
visionary
mock-ups
for
the
cic
templates
experience.
B
So
in
our
research
we
learned
that
the
experience
for
cic
templates
or
maintaining
a
library
of
cic
templates
is
incredibly
important
for
large
enterprise
organizations.
So
we
want
to
define
the
vision
for
what
it
could
look
like
for
you
to
create
a
library
of
a
cc
templates.
Maintain
that
library
enforce
certain
templates
across
the
organization,
notify
your
projects
and
developers
in
your
teams
about
updates
to
templates,
and
things
like
that,
so
feel
free
to
check
out
this
issue
to
learn
more
about
the
problems
that
we'll
be
looking
into.
B
We
want
to
collaborate
with
the
compliance
management
team
to
make
sure
that
we
are
aligned
on
the
things
that
they
are
doing
to
enforce
pipelines
across
projects.
So
we
have
some
overlap
there,
so
we'll
be
collaborating
together
and
we
want
to
create
visionary
mock-ups.
So
it's
not
going
to
be
like
a
final
proposal.
The
idea
here
is
just
to
create
some
mock-ups
some
assets
to
kick
off
discussions
around
this
vision
within
the
team
and
across
gitlab
across
different
stages,
so
related
to
this
work
I
will
be
collaborating.
B
Actually,
I've
already
started
collaborating
collaborating
with
the
compliance
management
team
to
surface
information
in
the
pipeline,
editor
about
existing
compliance
pipelines.
So
currently,
if
a
compliance
pipeline
is
enforced
for
that
project,
it
will
run
before
your
main
ci
cd
configuration,
but
we
don't
communicate
it
in
any
way
and
it's
important
that
we
communicate
it
to
anyone
who's
authoring,
a
pipeline
for
their
project,
because
the
pipeline
that
they're
creating
might
be
overridden
by
the
compliance
pipeline.
B
Another
issue
that
is
again
related
to
csa
templates
and
making
them
more
usable
is
improving
the
grouping
of
cic
templates
in
github
ui.
So
last
milestone.
I
ran
ux
research
learning
more
about
how
our
how
gitlab
users
group
css
templates.
B
When
does
it
run,
it's
allowed
to
fail
or
not,
and
things
like
that,
all
of
the
different
parameters,
and
then
you
can
go
to
edit
that
specific
job
in
the
yaml,
which
makes
it
easier
for
you
to
learn
ci
cd,
yaml
syntax,
because
now
you
can
make
the
connection
between
okay.
This
job
is
allowed
to
fail,
and
this
is
what
it
looks
like
in
yaml.
So
it's
easier
for
you
to
go
and
actually
edit
the
code
yeah
and
another
issue
that
I
will
attempt
to
complete
this
milestone,
we'll
see
how
it
goes.
B
It's
a
filler
issue
is
documenting
the
pipeline
graph
in
pajamas,
so
the
python
graph
is
a
pretty
complex
object,
with
lots
of
different
moving
parts
interactions
and
lots
of
different
teams
and
designers
worked
on
it
in
the
past.
B
So
this
is
an
attempt
to
kind
of
do
an
audit
of
the
pipeline
graph
and
document
how
it
is
and
what
it
looks
like
and
how
it
works
right
now
and
we
will
create
a
figma
file
that
will
contain
all
of
the
different
components
that
can
be
used
by
designers
across
gitlab,
and
we
will
also
document
in
pajamas,
so
others
can
also
access
this
information
about
the
different
statuses
and
states
and
interactions
in
the
pipeline
graph.