►
Description
Jenkins Pipeline-Authoring SIG Weekly Meeting for 20200403
A
Hello,
everybody
and
welcome
to
the
Jenkins
pipeline
authoring.
Sig
today
is
Friday
April
3rd.
This
is
our
weekly
meeting.
Welcome
to
everybody.
I
do
see.
We
have
a
few
new
people
on
the
call.
If
you
would
like
to
introduce
yourself
you're
more
than
welcome.
If
not
that
is
okay.
I'll
give
you
a
moment
and
if
you'd
like
to
introduce
yourself.
B
A
A
Let's
see
we'll
go
ahead
and
get
started
on
the
open
items
so
last
week
we
did
not
meet
because
there
was
all
kinds
of
things
happening
with
myself
and
other
people
were
busy,
so
we
did
not
cover
the
roadmap
that
was
drafted
up.
I
would
like
to
start
off
with
covering
the
roadmap
and
I
have
sharing
it
on
my
screen.
This
is
kind
of
what
I
came
up
with
and
I
started
doing
some
of
the
initial
initiatives.
These
are
not
hard
initiatives.
These
dates
are
not
hard
dates.
A
I
just
wanted
to
get
something
started
and
really
open
it
up
to
the
rest
of
the
community
to
start
to
help
set
the
sort
of
the
roadmap
for
this
particular
sig.
I
would
also
like
to
mention
that
the
idea
for
creating
this
roadmap
is
to
roll
up
into
the
Jeff
roadmaps
that
was
approved
by
Oleg
and
PR
game.
I.
Don't
have
a
link
to
that
PR
right
off
the
top
of
my
handy-dandy.
The
interweb
but
I
think
everybody
may
have
a
chance
to
you
have
seen
it.
A
Just
wanted
to
get
the
format
sort
of
up
there,
put
sort
of
what
the
ideas
would
be.
I
put
the
G
DSL
on,
because
I
really
do
want
to
see
that
come
to
fruition
from
a
sort
of
upkeep
and
maintain
maintenance
standpoint.
But
again
these
are
nothings
that
are
hard.
I
know:
we've
worked
on
the
personas,
the
roadmaps
and
their
documentation.
A
So
again
this
is
just
to
get
us
started
and
feedback
is
welcome.
What
I
do
believe
this
document
is
open
to
everybody
to
comment.
It
is
open
edit
ability
to
you
Liam.
The
reason
for
that
is
just
general
JP.
We
we
don't
want
to
have
people
come
and
start
messing
around
with
things
and
yeah,
not
to
not
to
be
the
gatekeepers.
It's
certainly
not
that.
So.
With
that
this
is
the
roadmap.
We
can
change
it,
we
can
add
to
it.
We
can
take
away
I
just
wanted
to
get
something
started
there.
C
I'll,
miss
Liam
I
preferred
that
we
actually
sort
of
follow
the
lead
from
the
overall
roadmap,
I
think
which
illness,
which
doesn't
have
target
dates,
and
the
reason
for
that
is
I
don't
want
to
for
people
to
feel
like
this
is
that
we
are
not
succeeding
if
some
specific
date
isn't
hit.
This
is
a
volunteer
organization.
Things
happen
and
like
that
means
that
it
sets
an
expectation
that
that
you
may
not
be
met
and
then
also
sort
of
it
just
might
make
make
anyone
doing
the
work
feel
less
good
about
it.
A
C
A
That
would
be
great,
you
know
what
I
think
I
can
I
can
take
that
action
item
to
sort
of
plagiarize
it
and
you
can
tailor
it
the
way
we
need
for
for
our
sig.
That
probably
will
be
a
good
good
thing
to
do.
I
will
take
that
action
item.
Okay,
thank
you.
So
there'll
be
another
document
coming
before
next
meeting.
Okay,
so.
D
Jenkins
roadmap
is
live
on
Jenkins
that
I,
oh,
it's,
admittedly
still
in
draft,
but
the
pull
request
was
accepted.
It's
visible
and
being
refined
I.
Like
the
conversation
we
had
in
discussing
the
road
map
that
maps
of
roads
do
not
in
general,
have
dates
on
them.
So
my
full
support
that
massive
roads
do
not
have
dates.
They
don't
need
them
right.
Lack.
B
D
A
D
I
just
sent
to
the
docs
mailing
lists
and
invitations
for
people
to
suggest
Doc's
roadmap
items
as
well
and
my
intent
there
I
proposed
to
use
a
actually
conducive
style
voting
technique,
gather
the
ideas
and
then
ask
people
to
vote.
So
this
is
this
feels
like
a
great
a
great
effort
as
well,
and,
let's,
let's
encourage
P.
The
crucial
thing
for
me
is
contributors
are
deeply
profoundly
highly
valued
I.
A
Next,
on
the
list
we
had,
there
was
I
have
added
these
items
in
I,
do
not
see-
and
they
may
be
here
and
no
I-
don't
think
so.
I'm
Craig
here,
so
it
no
SIL
for
Craig.
If
you
are
watching
the
video
we
are
talking
about
the
items
that
you
wanted
to
be
on
the
agenda.
I
would
like
to
add
something
which
is
an
echo
to
what
Oleg
has
stated
that
these,
these
type
of
bugs
don't
really
fall
under
this
sig
I.
C
C
I
will
try
and
advocate
for
active
that
I'm,
not
sure
that
the
percent
that
I
don't
agree
with,
which
is
these
are
pipeline
bugs
and
so
I
can
see
how
it's
how
it's
reasonable
to
want,
want
them.
It
worked
on
and
to
want
to
gain
and
greater
visibility,
and
they
say
well
the
this
would
be
one
place
to
get
that
kind
of
traction
right,
but
I,
don't,
as
you
said,
I,
don't
I.
Don't
think
that
this
is
the
venue
since
we're.
C
This
is
more
would
say
that
this
this
group
is
more
aspirational
about
where
we're
going
and
how
we
can
help
a
larger
community,
not
work
on
individual,
specific
technical
bugs.
There
are
already
people
doing
that
and
the
the
fact
that
their
time
is
limited
and
that
some
bugs
are
not
getting
as
much
traction
as
anyone
would
like.
Really
there's.
No
there's
always
more
to
be
done
than
there's
resources.
A
That
being
said,
if
a
if
a
particular
issue
or
person
concerned
about
an
issue
feels
that
they're
not
getting
the
needed
exposure
to
the
to
the
issue,
then
maybe
this
could
be
a
place
that
they
bring
that
up
to
voice
that
concern
I,
don't
necessarily
think
we
are
structured
currently
in
such
a
way
that
we
could
help
be
a
sounding
board
for
that
or
get
the
help.
I
think
for
a
particular
issue.
I
think
like
I'm,
rambling
and
I
apologize,
robot.
C
C
C
So
yeah
I
commented
a
little
while
ago
on
it's
five
to
nine
three
nine,
it's
sort
of
a
squash
together
issue
that
has
like
we
also
they
think
I
was
filed
by
Craig,
actually,
and
so
he's
said.
I
want
this,
and
I
also
want
to
do
a
reload
for
Hanley's.
Other
larger
technical
issue,
which
is
been
around
for
a
long
time,
is
harder
to
do
so.
A
Hey
this
is
not.
This
meeting
is
not
the
venue
to
address
certain
things
like
that
yeah
to
get
those
things
addressed.
We
can
maybe
say
you
know,
use
the
getter
channel
and
I
think
I.
Also
just
add
to
that
I
put
in
a
PR
yesterday
that
PR
was
merged
to
update
sort
of
the
structure
of
our
Jenkins
dial
for
IO.
For
the
the
pipeline
authoring
to
kind
of
state.
Hey,
you
gotta
use
the
getter
channel
for
these
things
and
make
sure
you've
done
your.
You
know
due
diligence
and
research
before
coming.
A
A
C
Me
just
let
me
just
guess:
I'll,
just
okay,
if
you're
watching
this
later
or
if
you're
on
the
Gator
channel,
we're
happy
to
you
know,
discuss
this
again,
just
come
back
around
just
like
it's
one
of
those
things
where
right.
This
is
one
star
it's
like!
Well,
you
wanted
to
bring
it
up.
We've
grown
it
up.
We'd,
look
we'd
love
to
have
your
your
view
on
it,
rather
than
talk
about
it
amongst
ourselves.
So
anyways
thanks!
Thank
you
very
much.
A
I
have
some
suggestions
so
I
think
for
anybody
else
that
may
not
have
been
here
when
we
were
discussing
that
we're
talking
about
wood.
Overall,
all
there
was
a
larger
organizational
roadmap
put
forward,
and
now
each
cig
is
trying
to
do
their
roadmap
to
sort
of
roll
up
into
that
large
organizational
role
on
the
job.
The
doxy
is
also
doing
the
same
thing
and
the
hobbs
they're
open
for
suggestions
and
contributions
and
items
like
that
now
I
know.
A
We
have
talked
a
lot
about
previous
meetings
about
the
Dobson
and
how
we'd
like
to
see
pipeline
stuff
sort
of
structured
for
that.
So
this
is
a
great
opportunity
to
be
able
to
for
anybody
watching
or
anybody
here.
This
is
a
great
opportunity
to
be
able
to
influence
or
have
the
ability
to
speak
and
add
your
value
to
other
SIG's
as
well.
There
is
a
link
to
the
docks,
Zig
meeting
notes
in
our
meeting
notes
mark.
Would
you
like
to
add
anything
about
that?
Just.
D
Encourage
people
to
freely
be
involved,
I'm,
trying
an
experiment
with
this
particular
request.
I'm
gonna
gather
suggestions
for
about
a
week,
and
after
about
a
week,
I'm
gonna
put
up
a
Condorcet
poll
that
will
ask
people
to
prioritize
which
things
they
want
and
then
will
my
proposals
we'll
take
the
top
two
or
three
and
put
those
on
the
roadmap.
We've
had
suggestions
for
Jenkins
and
kubernetes
for
hey,
give
me
dramatic
improvements
to
how
Java
eight
is
described
or
the
tuning
of
this
or
that
all
sorts
of
interesting
topics
and
areas.
D
B
A
D
D
D
A
Okay,
that
is
I
I
will
as
soon
as
we're
done
with
this
meeting
I'm
going
to
go
right
to
this
thing,
and
you
had
some
stuff
great
thanks:
okay,
so
that
takes
care
of
new
items.
We
do
have
my
action
item
that
I
will
migrate
and
adapt
the
Jenkins
I/o
road
map
for
our
cig.
I
will
have
that
ready
by
the
next
meeting.
Is
there
an
so
now
we
can
go
into
open,
Q&A
or
open
mic?
Do
you
want
to
call
it?
Does
anybody
have
anything
they
wanted
to
discuss?
A
C
A
I'd
like
to
say
one
thing
in
regards
to
the
new
people
joining
that
really
warms
the
the
deepest
parts
of
my
heart.
So
thank
you
for
joining
California
front.
I.
Think
it's
awesome.
The
community
we're
very
inviting-
and
this
is
the
opportunity
to
not
only
get
to
learn
but
also
to
be
able
to
help
affect
some
of
the
organizational
changes
that
are
happening.
So
thank
you
so
so
much
for
joining
please
tell
a
friend
and
bring
one
I
was
going
to
make
some
hot
feet
statement,
but
I'm
not.