►
From YouTube: Jenkins Pipeline-Authoring SIG US Meeting for 20200313
Description
Jenkins Pipeline-Authoring SIG US Meeting for 20200313
A
Hello,
everybody
and
welcome
to
the
Jenkins
pipeline
authoring,
sig
United
States
meeting
it
is
Friday
March
13th
welcome.
I
will
start
with
saying
that
the
Jenkins
does
have
a
code
of
conduct
which
essentially
amounts
to
don't
be
a
jerk
to
one
another.
Just
be
kind.
I
am
going
to
share
my
screen
to
bring
up
the
meeting.
Oh
no,
don't
tell
me
I
can't
share
my
screen.
A
A
Beautiful,
thank
you
so
very,
very
much
I
appreciate
that
make
it
readable,
sighs,
okay
and
if
you
could
just
drop
your
name
in
the
attendees
list
for
March
13
I
will
go
ahead
and
start
off
with
open
items.
The
personas
questions,
if
everybody
has
entered
their
questions,
which
I
believe
they
have
that's
great.
A
If
you
have
it,
please
do
I,
will
link
the
doc
the
link
to
the
doc
in
here,
but
I
think
most
everybody
has
answered
their
personas
questions
and
those
are
going
to
be
what
we
decide
how
our
roadmap
is
going
to
look
and
the
features
that
we
want
to
work
on.
Do
you
anybody
have
anything
to
add
to
that
anybody
mark
it's
Jesus.
I
won't
refer
to
you
as
there's
more
people
here,
nothing.
A
I
will
move
over
into
the
discussion
G
DSL
support.
There
has
been
some
chatter
in
the
Gitter
chat
in
regards
to
doing
getting
that
back
up
to
speed
and
well
I.
The
the
the
chatter
I
agree
with
is
extremely
relevant,
and
it
is
something
that
Liam
and
I
have
talked
about,
adding
this
to
our
roadmap.
So
we
definitely
will
be
thinking
about
that
and
how
we
want
to
get
that
done.
A
Is
we
want
to
set
out
a
roadmap
for
what
we
will
be
wanting
to
accomplish
as
a
you
know,
from
a
high
level
and
then
what
we're
going
to
accomplish
this
year,
maybe
quarter
by
quarter.
This
also
sort
of
rolls
up
into
for
those
that
have
seen
Oleg's
email
in
regards
to
the
overall
Jenkins
roadmap.
We
want
to
start
rolling
sig
roadmaps
into
that.
I
will
add
a
link
to
what
we
have
for
the
initial
road
map,
as
well
as
to
O'lakes
a
mailing
list
item
for
hit
the
overall
Jenkins
project
roadmap.
B
Just
one
point:
just
like
real
maps
of
real
roads
don't
have
dates
on
them.
It
is
perfectly
okay
that
the
real
map,
but
the
map
of
this
road
does
not
have
dates
on
it.
So
you
you
referenced
quarters
and
for
me
it
I
think
it
was
Oh.
Legs
phrasing
was
something
like
now
near
and
the
long
ways
out
or
something
like
that.
There
he
had
three
three
buckets
in
his
proposal
and
and
none
of
them
are
particularly
time
constrained,
agreed.
A
A
B
Okay,
so
I've
been
I've
been
funded
to
replace
the
d-zone
Jenkins
pipeline
rift
card.
It's
a
PDF,
formatted
ref
card,
eight
or
ten
pages
based
coming
from
2015,
that's
heavily
on
scripted
pipeline
and
I
think
we
can,
given
that
it's
a
funded
effort,
we
can
shift
its
content
to
use
it
to
do
some
things
with
declarative.
There
is
already
a
declarative
pipeline
ref
card
from
d-zone,
but
none
of
them
that
none
of
those
have
anything
about
matrix
for
milestones
or
retry.
For
me,
I
think
we
should
deprecated
scripted
from.
B
A
B
That,
okay,
cool,
so
matrix,
milestone
and
retry
are
three
that
look
to
me.
Oh
I,
guess
there's
one
more
lock
right
that
are,
if
I
remember
I'd
not
mentioned
in
the
existing
declarative
pipeline
ref
card,
any
other
recommendations
of
oh
here's,
a
cool
feature
that
we
ought
to
highlight.
It
already
does
have,
for
instance,
post
when,
except
are
already
covered.
Okay,.
A
B
It's
this
is
just
me
I'll.
Do
it
myself,
I'm,
not
no
kind
of
for
help
from
the
community.
I
do
think
that
I
would
lie.
I
hope
that
I
can,
as
part
of
this
use
it
to
generate
a
declarative
pipeline
tutorial
on
Jenkins
IO.
That
was
the
the
reason
for
coming
to
the
pipeline
authoring.
Sig
was
I
think
this
could
also
be
used
to
generate.
We
have
today
on
Jenkins
DeMayo
tutorials
on
how
to
do
a
maven
based
java
application,
how
to
do
a
Python
application,
how
to
do
a
nodejs
application.
B
This
would
be
somewhat
orthogonal
to
those
two,
those
three
things
which
are
application
centered.
This
one
would
be
feature
highlight:
centered,
show
the
pieces
and
let
let
a
reader
choose
which
piece
they
wanted
to
look
at
instead
of
a
linear
flow
through
the
tutorial,
it
would
be
choose
your
adventure,
oh
I,
want
to
know
about
postconditions
I
want
to
know
about
when
I
want
to
know
about
matrix
or
milestone
and
put
tutorials
segments.
Their
question
was:
does
that
seem
reasonable
for
a
tutorial
or
should
I
look
at
another?
Another
delivery
form
no.
A
B
And
I,
like
that,
that's
a
good
point
which
persona
or
personas
will
this?
Will
this
updated
document
address
because
we've
got
a
good
point?
I
I
should
be
very
clear
with
the
people
I'm
working
that
they're,
helping
with
it
which
personas
were
trying
to
address
and
which
ones
we
are
not
trying
to
address
with
this
agreed.
A
And
I
think
when
we
have
the
overall
document
that
gets
put
out
there
in
terms
of
personas-
and
somebody
says
oh
I'm
David,
and
then
they
see
that
they
could
say:
oh
okay,
well,
that
that
doesn't
apply
to
me
or
then
they
look
at
it
in
their
like
that,
does
apply
to
me.
I'm,
not
David,
I'm,
Linda,
so
I
do
think.
That
would
be
good
if
we
could
sort
of
somehow
incorporate
that
good.
B
A
That
is
that'll,
be
great
I'd
love
to
see
that
in.
If
you
need
any
help,
please
by
all
means,
let
me
know
and
I
can
help,
but
I
think
you've
got
it
well
under
control,
but
please
don't
hesitate
to
reach
out
if
you
do
great.
Thank
you.
That
is
all
that
I
had
I,
don't
think,
there's
anything
else.
Do
you
have
anything
else
you
wanted
to
add
mark
I,
don't.
A
Talk
through
that
risk
card
question.
Well
that
is
beautiful,
then
I
will
give
you
back
the
rest
of
your
hour.
I
will
thank
anybody
that
is
watching
this
for
watching
it,
and
if
you
do
have
any
questions,
please
don't
hesitate
to
reach
out
to
us
via
the
pipeline
authoring
mailing
list
or
directly
in
the
Gator
channel.
With
that
I
will
thank
everybody
and
have
a
great
weekend
thanks,
bye,
bye.