►
From YouTube: GitLab 16.1 Kickoff - Verify:Pipeline Security
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
All
right,
hi,
I'm,
Jocelyn
I,
am
the
product
manager
for
the
pipeline
security
team
here
at
gitlab,
just
a
quick
refresher
for
those
of
you
who
are
new
to
us.
We
are
the
team
responsible
for
the
secrets,
manager,
Secrets
management
category,
which
includes
secret
manager,
integration,
CI
variables
and
CI
job
token,
as
well
as
the
build
artifacts
category
I'm
here
today
with
our
wonderful
designer
of
youthika
to
kick
off
our
16.1
Milestone
plan.
A
So
a
few
things
just
this
Milestone,
our
capacity
is
going
to
be
a
little
bit
smaller
than
it
has
been
in
the
past
due
to
a
one-week
hackathon,
an
internal
hackathon,
but
we've
got
a
ton
of
great
features
that
were
that
were
still
focused
on
implementing.
A
A
We
are
going
to
continue
to
focus
on
build
artifacts,
and
it's
been
for
those
of
you
who
have
been
with
us
on
the
sturdy.
It
has
been
quite
the
road
trip
working
on
getting
artifacts
unlocked
properly
and
really
helping
out
with
the
storage
means,
so
that
will
continue
to
be
something
that
we
will
be
working
on
as
a
team.
A
However,
we
are
really
excited
to
be
making
new
feature
changes
to
improve
the
variables
experience,
as
I
mentioned
on
the
front
end,
we
will
be
spending
a
lot
of
time,
also
improving
that
experience
for
the
variables
one
of
our
I
think
big
big
areas
is
actually
starting
work
on
the
variable
table
layout,
and
so
this
is
our
first
iteration
of
a
larger
request
to
really
help
be
able
to
represent
a
visual
hierarchy,
and
so
this
will
enable
our
users
to
better
understand
what
very,
what
variables
are
affecting
their
their
outputs
as
well
as
where
overrides
might
be
happening
as
well.
A
B
Thank
you
so
much
Jocelyn,
it's
good
that
this
is
open.
So
I
could
like
talk
about
this.
First
I
won't
be
doing
a
lot
of
design
for
this
Milestone,
because
a
lot
happened
in
this
Milestone.
B
We
took
up
work
that
was
not
scheduled,
but
we
made
a
lot
of
progress
in
making
some
very
meaningful
UI
changes,
but
there
are
still
some
changes
that
we
are
not
like,
100,
confident
confident
about,
and
we
want
to
just
like
check
with
our
users
validate
with
our
users,
so
that
can
be
sure
that
we
are
delivering
what
needs
to
be
delivered.
B
So
here
you
would
see
this
issue
that
I
have
different
versions
of
designs
up
on
like
what
would
solve
the
problem
of
not
of
this
lack
of
communication
of
hierarchy
in
the
wearables
table.
B
So
many
teams
they
rely
heavily
on
the
hierarchical
structure
of
the
of
how
the
variables
are
inherited
from
group
to
subgroup
to
project
and
not
getting
any
visibility
into
that
actually
creates
a
lot
of
problem,
because
then
they
end
up
creating
a
variable
with
the
same
name
as
one
already
exists
at
some
level
and
that
ends
up
getting
overridden.
So
nobody
wants
that.
B
This
is
like
our
first
step
towards
making
that
change
towards
bringing
this
to
users
that
these
are
all
the
variables
that
are
being
used
by
the
project,
and
we
don't
need
to
separate
them
out
like
groups
and
projects,
because
if
we
just
present
them
all
together
in
alphabetical
order,
it
would
be
easier
to
like
show
visually
that
maybe
two
variables
Exist
by
this
name
at
different
levels,
and
this
is
how
the
overriding
is
happening.
B
Yeah
and
we'll
take
this
to
a
bunch
of
users
for
testing.
That's
one.
We
have
a
lot
of
questions
that
we
would
want
answers
to.
So
let's
keep
our
fingers
crossed
that
we
get
some
conclusive
answers
and
we
can
make
a
progress
on
this
foreign
to
the
next
one.
I
mean
apart
from
this
I,
don't
have
really
any
Stage
Group
related
work.
It's
just
that
I'm
taking
part
in
a
beautifying
UI
effort
which
is
going
to
impact
the
entire
verify
section.
B
We
are
making
some
like
quick,
UI,
purifications
I
would
say
like
improvements,
so
that
the
experience
in
those
areas
are
smoother
yeah
and
that's
going
to
be
exciting
as
well
and
and
I'll
see
what
comes
up
that
I
would
be
working
on
in
this
Milestone
I'm
like
pretty
excited
about
this,
because
I
think
end
of
16.1
we'll
see
some
tangible
changes
on
the
UI.
That's
going
to
really
improve
our
experience.
A
Yeah
we
are
I'm,
really
excited
as
well,
just
looking
at
our
backlog
and
looking
at
the
issues.
I
think
this
is
going
to
have
a
really
great
impact
for
for
our
users,
so
so
that
is
pipeline
security.
16.1
thanks
for
sharing
with
me.