►
From YouTube: Verify:Pipeline Authoring 15.4 kickoff
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,
my
name
is-
and
this
is
15.4
pipeline-
authoring,
kickoff
video.
As
always,
we
do
have
a
planning
issue
underneath
our
pipeline
authority
group
issue
number
68,
where
you
all
of
you,
can
add
your
comments,
thoughts,
feedback
and
see
how
we
as
a
team,
collaborate
and
decide
what
are
the
priorities
for
the
upcoming
iteration,
the.
A
Milestone
is
heavily
driven
from
the
carrier
was
from
the
previous
milestone,
and
this
is
why
I
link
the
previous
milestone
planning
issue
and
we
had
a
lot
of
back-end
work
that
did
not
complete
yes,
so
we
had
to
move
some
of
those
goals
from
the
previous
iteration
to
the
existing
one.
Primarily,
they
work
for
secret
management.
A
Integration
with
the
move
of
the
jwt
open
id
connect
token
from
alpha
to
ga
is
still
something
that
the
team
is
focusing
on,
and
I've
linked,
my
previous
recording
from
the
previous
milestone,
where
I
elaborate
about
what
is
the
work
that
is,
needs
to
be
done
in
order
to
move
it
from
a
alpha
to
ga.
So
if
you
want
more
information
about
this
work,
I
highly
recommend
you
watch
this
recording.
A
I
don't
expect
all
of
those
issues
to
land
into
15.4.
We
might
need
to
carry
over
some
of
this,
but
the
work
that
we
are
doing
today
will
allow
us
to
unblock
those
issues
and
movements.
As
you
can
see,
it
is
reflected
on
the
planning
issue
where
you
can
see
that
most
of
the
issues
are
front-end
issues
only.
B
Hey
everyone:
this
is
nadia
the
product
designer
at
verify
pipeline
authoring,
and
this
is
my
plan
for
15.4.
So
in
15.4
I
will
be
spending
half
of
my
capacity
on
the
beautifying
ui
effort,
which
is
a
like
a
new
program
that
we
have
at
gitlab,
where
we
pair
an
engineer
and
a
product
designer
every
milestone
to
resolve
different
ui
bugs
polish,
our
ui
in
different
ways
use
a
small,
solve
small
usability
problems
and
just
do
some
ui
polish,
like
ui
unboxing,
and
things
like
that.
B
B
Next,
I
will
be
working
on
some
pipeline
authoring
specific
issues,
so
I
will
work
on
an
issue
to
show
information
about
runner
setup
during
csd
csd
onboarding.
So
we
already
have
explore
some
mockups
here,
but
it
requires
some
more
refinement.
B
We
want
to
show
the
runner
setup
information
in
a
way
that
doesn't
block
you
from
seeing
what's
next,
like
what's
the
next
step
for
the
icd
setup,
so
I
will
be
exploring
combining
this
view
with
our
templates
empty
state
for
ci
cd.
B
Next
is
an
issue
to
show
this
to
show
job
variables
in
the
ui.
So
currently
it's
very
difficult
to
understand
which
variables
are
used
by
a
job
in
a
pipeline.
It
makes
it
difficult
to
debug
pipelines,
so
we
want
to
show
a
list
of
all
variables
used
by
the
job
somewhere
in
the
job
detail.
B
This
is
around
improving
the
user
experience
for
secrets
workflows
in
gitlab,
and
here
we
will
need
to
figure
out
a
better
way
to
serve
as
a
helpful
error
in
case
defined
secrets
do
not
exist
involved
because,
currently,
when
such
problem
occurs,
we
don't
communicate
it
to
the
user
in
any
way,
so
it
becomes
again
very
difficult
to
troubleshoot
the
problem.
So
yeah
I'm
very
excited
to
work
on
the
accessibility
issues,
and
this
will
be
it
for
me.