►
Description
Jenkins Pipeline-Authoring SIG Weekly US Meeting for 20200320
A
Hello,
everybody,
my
name
is
Marky
Jackson
I
am
a
software
engineer.
This
is
the
Jenkins
pipeline
authoring
SiC
meeting
for
the
u.s.
time
zone.
It
is
March
20th
2020.
Thank
you.
Everybody
for
joining
liam
welcome
back
yeah,
hey
I'm
alive
alive,
vastly
different
world,
as
we
were
then
chatting
about
earlier.
Yeah
I
will
like
to
start
before.
I
start.
This
meeting
I
would
like
to
say
that
the
Jenkins
does
Jenkins
community
does
have
a
code
of
conduct
which
essentially
amounts
to
do
not
be
a
jerk,
be
good
to
one
another.
A
With
that
we
will
get
this
meeting
underway.
Liam
is
taking
notes
I.
Thank
you
for
doing
that.
I
am
going
to
say
that
if
you
have
not
added
the
your
name
into
the
attendees
list,
which
I
believe
everybody
has
that's
awesome,
we
will
move
into
open
items.
The
first
open
item
is
closing
out
the
personas
I
know
they're.
The
last
before
you
had
went
on
vacation
Liam.
A
The
last
item
we
talked
about
was
adding
in
the
questions
for
the
various
personas
I
feel
that
most
people
have
done
that
there
may
just
be
one
or
two
more.
That
need
to
be
added
out,
but
what
I
would
like
to
do
is
start
to
close
that
out
this
week
and
have
before
next
week
can't
that
be
done
and
I've.
B
Looks
like
someone
was
nice
enough
to
ask
to
do
some
of
the
characteristics
for
URI
right
signed
up
for
so
that's.
Thank
you.
Very
much.
I
should
add
a
few
more
on
that,
but
anyway,
so
do
me
let's
see
here,
do
we
want
to
go
over
these
to
close
them
out
or
I
mean?
How
should
we
go
about
that
I?
Think.
A
B
B
A
B
B
A
D
A
D
B
These
one
questions
it's
more
like
these
are
the
kinds
of
things
that
they're
gonna
be
asking,
where
I
most
often
write
to
start
with
so
anyways
uh-uh
all
right.
What
else
so?
Moving
on
to
Erica
the
person
who's
been
dropped
into
doing
the
Jenkins
maintenance,
but
it's
trying
to
do
it
right
and
improve
on
things
in
Dijkstra.
They
understand
things.
Where
can
I
find
documentation
to
help
me
keep
Hankins
running
how
do
I,
D
bug,
failures
and
pipelines
after
upgrading?
B
How
can
I
create
easy
to
manage
pipelines?
Is
there
a
list
of
best
practices
documents
to
guide
me?
This
is
similar
to
the
similar,
the
ones
that
you're
asked,
but
a
little
a
little
more
on
the
holistic.
I'm
gonna,
try
and
understand
that
this
this
new
world
I'm
living
in
kind
of
thing,
where
can
I
get
a
list
of
steps
provided
by
plugin,
so
I
don't
try
to
recreate
them
in
groovy
when
I
should
not
and
when
should
I,
not
trust
steps
from
random
plugins.
D
A
Think
one
I
don't
know
what
persona,
what
I'm
about
to
say
would
fall
under
I
feel
like
it's
Erica
and
maybe
Olivia,
but,
for
example,
I
have
had
the
passionate
debate
with
individuals
about
the
use
of
plugins
versus
natively
writing
the
code.
A
good
example
is
docker,
so
most
people
will
trust
the
underlying
jenkins
to
handle
docker.
You
know
certain
native
docker
calls
as
opposed
to
writing.
Those
native
doctor
calls
out
themselves.
What
happens
is
is
for
in
my
particular
example,
for
my
argument
is
durable
tasks
plug-in
that
somehow
gets
broken.
A
For
example,
1.32
was
broken
for
a
bid
that
broke
all
underlying
docker
and
people
had
to
write
things
out
natively.
While
we
waited
for
a
fix
in
1.33
I'm
wondering
if
the
cool
I
don't
know.
If
it's
a
question
to
say,
when
do
you
install
a
plug-in
versus?
Actually
writing
your
own?
You
know
code
to
do
something
such
as
docker.
E
F
G
G
D
G
A
A
I
was
able
to
mitigate
it
well
for
those
people
that
don't
know
that
and
they're
just
like
you
know,
they're,
not
ops
and
then
all
of
a
sudden
they're
like
hey
I'm
using
a
you,
know,
agent,
dockerfile
and
it's
just
not
working
or
you
know
or
doc
image,
and
it's
not
working,
they
may
not
know
have
the
advantage
of
knowing
that
there's
regression
taking
place
on
that
and
that's
sort
of
where
my
question
comes
in.
If
that's
a
valid
question,
oh.
B
A
B
B
D
B
D
B
B
All
right
cool,
let's
I'll,
move
on
so
we
have
Olivia
outside
I,
see
developer
I'm,
not
ops.
I
can't
tell
what
plugins
provide
which
pipeline
steps.
This
is
similar
to
a
bit
different
I,
see
that
how
do
I
know
when
I
should
convert
something
into
a
shared
library
or
not
I've
read
about
declarative
versus
scripted.
How
do
I
know
which
one
to
use?
What's
all
this
about
CPS
sandbox,
do
I
need
to
worry
about
that
stuff
yeah
getting
into
the
more
into
the
into
the
the
guts
of
the
system.
B
D
B
B
B
B
B
What's
the
best
workflow
patterns
for
teams,
what
are
the
ways
to
best
use
share
code?
What
are
some
common
best
practices?
What
are
common
use
cases
I
can
follow.
Are
there
common
use
cases
I
can
follow?
Is
there
a
link
to
videos
from
the
Jenkins
community?
Is
there
documentation
of
basic
usage
of
pipelines.
A
Sorry
I
did
my
inline
questions
there,
it's
fine
and
when
I
approach
these
questions
a
lot
of
the
way
I
approached
him
was
somebody
that
is
now
either
taking
over
Jenkins
or
they
they
are
go
moving
from
a
one
platform.
You
know
to
two
Jenkins,
and
these
are
things
that
I
would
having
been
through,
that
the
questions
I
start
to
think
of
okay.
B
E
B
So,
moving
on
to
I'll
come
back
and
clean
this
up
in
just
a
second
moving
on
to
Lisa.
How
can
I
make
pipeline
support
my
plugin
easier
for
users?
Well,
symbols
help
what
documentation
should
I
write.
This
sounds
like
Mark
writing
this.
Where
will
I
well
with
that
documentation
be
displayed?
How
do
I
write
Java
unit
tests
for
pipeline
code
in
my
plugin
work?
Homeland
Security?
Are
there
common
security
threats?
I
should
understand,
while
writing
my
plugin.
Where
should
I
ask
questions
about
development
pipeline
support
in
my
plugin
a
lot
of
plug-in
detail
stuff
here?
B
B
G
B
B
G
B
B
A
B
C
For
me,
it's
a
level
of
experience,
because
student
intern,
on
the
account
with
limited
knowledge
of
the
industry,
definitely
of
program
in
cat
level
of
pipeline
DSL
and
but
similar.
They
may
get
cases
like
his.
You
know,
Jenkins,
please
automate
product,
I,
wouldn't
say:
I
agree
with
such
approach,
but
yeah
I
see
that
quite
often
so,
basically
it's
just
persona
for
the
label
all
experienced
against
a
user
and
who
is
tasked
to
do
some
development
and
basically
needs
a
kind
of
ramp
up.
Okay,.
B
B
No
I
mean
I,
see
what
you're
saying
like
it's
somewhere
between
it's
somewhere
between
Erika
and
Olivia.
Is
the
thing
and
I
see
what
you're
saying
that
that
it's
not
quite
either
one
of
those
because
the
there's
less
industry
experience
and
less
Jenkins
experience,
but
they're
being
asked
to
do
things
at
the
level
that
things
that
you
might
ask
of
the
Olivia
persona.
C
B
B
D
Do
we
want
to
have
a
persona
asking
the
question
should
why
should
I
continue
using
Jenkins
versus
something
else
and
I
asked,
because
something
I'm
fighting
with
a
lot
yeah
and
I
I
think
it's
kind
of
stupid,
because
I
don't
think
engineers
should
be
focusing
on
CAC
need.
But
since
people
are
asking
a
question,
I
mean
it's:
it's
just
a
waste
of
time.
In
my
opinion,
they
like
switch
stuff,
but
is
that
something
that
we
might
address.
B
Or
is
upturn?
No
no
I'm
at.
Let
me
see
so
Yuri
wouldn't
ask
that
cuz
he's
too
busy
doing
it.
Erica
wouldn't
ask
that
because
she's
taking
things
as
they
are
and
working
with
them
right,
probably
the
devs
the
eyes
either
that
and
I
think
the
dev
ops
team
member
would
might
might
ask
that
question
but
they're,
but
at
that
point
they're
very
often
they're,
like
hey
we're
doing
this
thing,
we've
already
got
a
big
investment
in
this
go
ahead
and
continue
like
it's
I.
B
B
D
B
B
B
A
B
C
Yeah
I'm
not
sure
whether
it's
a
good
discussion
to
dive
too
much,
because
there
is
no
students
at
the
call.
What
if
we
detail
over
past
week,
we
agreed
that
we
would
use
500
meetings
to
discuss.
The
project
sounds
great
yeah,
but
so
far
he
didn't
work
well,
maybe
because
of
time
income
in
Shaw.
So
maybe
we'll
try
another
approach
but
yeah.
What
I
wanted
to
say
that
there
is
a
project
idea
which
is
specifically
related
to
pipeline
authoring,
basically
providing
ability
to
write
pipelines
in
fully
declarative
way
early
without
groovy,
DSL,
okay
and.
B
A
A
C
You
have
my
keys
right
now:
okay
ji-sook,
so
here
you
can
see
that
there
is
a
number
of
proposals
which
actually
related
to
pipeline,
for
example,
that
our
pipeline
documentation,
generation
improvements,
and
today,
we've
spent
a
lot
of
time
discussing
checks
api,
how
checks
api
steps
could
be
also
integrated
in
the
pipeline.
So
all
proposals
will
go
so
far,
including
integration
with
pipeline,
but
specifically
the
respite
and
as
a
llamo
think
and
pipeline
is
llamo.
Sink
is
a
continuation
of
the
project
we
had
in
2018.
C
But
that's
what
we
had
at
that
point
and
right
now
the
propose
will
behave
on
the
table
after
multiple
discussions
that
have
an
experimental
plugin,
which
would
be
doing
basically
the
same
supporting
PMO
definitions,
but
it
could
be
the
definition
course
Jenkins,
X
pipelines
or
definition
close
to
one
of
existing
pipeline
libraries,
because
we
have
a
bunch
of
Python
libraries
which
support
llamo
right
now,
like
I,
would
say
word
or
impaired,
or
a
xxx
proposal,
which
was
discussed
recently.
It's
actually
having
support
of
syntax,
which
would
be
close
to
Tecton.
C
C
C
C
It
depends
because,
right
now
there
is
a
better
mode,
always
how
it
could
be
implemented,
how
JSOC
works.
You
expect
students
to
come
up
with
their
proposals
based
on
project
ideas
and
then
his
help
of
mentors
is
inputs
to
implement
them,
so
the
final
implementation
would
be
really
dependent
on
what
occasions
we
get
and
there
were
concerns
about
how
to
map
into
existence
on
the
caste
system.
So
we
run.
This
proposal
is
explicit.
The
experimental.
C
B
B
C
C
Everyone
else:
okay
and
yeah,
the
government
personas
and
CDF
in
CDF.
That
is
a
special
interest
group
about
interoperability
and
what
they
are
doing.
Nowadays
they
are
trying
to
define
common
terminology.
They
are
trying
to
define
personas
forty
ICD
tools
and
basically
it's
it.
Maps
personas
for
pipeline,
though
yeah
Jenkins
personas
are
different,
but
still
there
may
be
some
opportunities
for
collaboration.
Okay,.
E
C
So
once
you
have
something
for
Jenkins,
maybe
make
sense
to
at
least
bring
it
up
and
bury
intervene
sisig.
So
to
see
whether
there
is
some
overlap
with
other
tools,
because
I
believe
that
spinner
ket
has
problems
quite
close
to
Jenkins
for
Tecton
for
Jenkins
X.
Yes,
this
face
is
a
bit
different,
but
at
the
same
time
it's
something
where
Jenkins
might
be
looking
at
several
years.
Who
knows
so?
Some
combination
might
make
sense.
Okay,.
A
Awesome
road
man,
yep
I,
was
oh,
like
put
out
a
sort
of
overall
arching
roadmap
for
the
Jenkins
project
as
a
whole
and
I
I
think
it
would
be
advantageous
for
every
sink
but
for
at
least
for
the
pipeline
authoring
sig
to
start
coming
up
with
the
roadmap
that
can
roll
up
into
that
roadmap.
I
know
I've
talked
to
you
about
that
lammed
of
getting
that
starting
to
dictate
what
we
want
to
get
done,
but
I'd
like
to
start.
A
First
get
everybody
from
the
communities
by
him
on
that
and
then
start
to
get
something
drafted
out
about
things
that
we
want
to
work
on.
So
people
have
a
good
idea.
I
will
say
a
lot
of
my
urgency
on
the
matter
came
from
an
interaction
with
another
community
member
who
was
very
frustrated
about
the
lack
of
progress
in
just
overall
stuff
that
was
prior
to
Oleg,
releasing
the
road
map,
but
mainly
towards
just
like
you
know,
the
G
DSL
and
things
like
that
and
just
you
know,
things
just
don't
seem
to
be
moving.
A
B
G
B
A
A
B
So
the
thing
that
I,
the
one
thing
I
would
I
would
want
to
clarify
here
is
is
the
as
you're
saying
we
want
to
try
and
get
this
in
and
I.
Think
part
of
the
point
of
this
sig
is
to
do
is
to
raise
awareness
so
that
we
aren't
the
ones
necessarily
doing
it.
This
is
very
much
like
where
volunteers
would
we're,
obviously
we're
contributing
we're
gonna
do
something
with
it,
but
I
want
to
be
I'll.
B
Make
sure
that
when
we
message
this,
it's
hey,
this
is
a
project
being
worked
on
and
you
can
join
agree
I'd
end
and
we
say
to
whoever
is
out
there,
because
otherwise
it
becomes
a
people
will
look
at
it.
Much
like
what
your
this
community
member
that
you're
talking
about
will
say.
Well,
when
is
it
happening?
Well
and
I?
You
know
we
all
we
all
have
aside
from
Jenkins.
We
probably
have
other
other
projects
that
we
also
work
on
like
when
it's
happening.
B
A
G
A
Like
to
add
I'd
like
to
add
that
I
100
percent
100
50
percent
agree
with
you,
I
do
think
that
we
have
to
as
leaders
of
a
given
sig
how
to
set
some
sort
of
work
precedence
and
when,
as
we
set,
you
know
those
precedents,
then
we
can
say:
hey
here's.
What
we're
working
on
and
we'd
love
your
help
or
if
somebody's
complaining
about
a
specific
or
and
I
don't
want
to
say
complaining.
A
If
somebody's
voicing
a
concern
about
a
specific
issue,
then
we
could
say:
hey,
that's
actually
on
our
roadmap,
it's
a
little
bit
further
down,
but
I'll
tell
you
what
the
reason
it's
further
down
on
us,
because
we
don't
have
a
lot
of
help.
But
if
you'd
love
to
help,
we
can
pull
that
up.
Yep
and
Oleg.
Do
you
have
a
question
not.
C
B
C
So
the
implementation
is
basically
aligned
with
what
you
were
saying
cream,
so
we
don't
do
any
kind
of
commitment.
We
deploy
roadmap
to
raise
visibility
of
the
projects,
visibility
for
contributors,
visibility
for
vendors,
because
it's
also
important
you
want
vendors
to
be
involved
time
to
see
where
Jenkins
was
going
and
at
the
same
time,
our
if
we
facility
convey
things
because
you
have
a
really
positive
experience.
C
For
example,
Jake
asked
space
and
documentation
space
recently
where
community
contributors,
who
do
a
lot
of
things,
might
help
of
Sikhs
like
entities
which
just
do
some
assistance
make
things
happen.
Some
like
is
do
sponsorship
site
for
delivering
changes,
and
this
approach
can
really
work
later.
We
could
also
align.
It
was
coming
in
to
bridge
projects.
So
so
there
is
google
Summer
of
Code,
but
we
also
did
a
successful
experiment
for
community
bridge
this
year.
We
have
slidin
on
the
call,
by
the
way
was
working
on
magic,
has
developer
tools
and
other.
C
B
C
It's
just
the
beginning,
so
if
you're
familiar
with
lotion
roadmap,
I
just
took
it
and
adjust
that
to
my
proposal
in
terms
of
process,
etcetera
right
but
yeah.
The
final
lookin
few
may
be
different
because
it
depends
on
the
number
of
items
only
we
are
going
up
to
something
like
50
items,
maybe
more,
and
the
current
listing
won't
be
really
good
for
that.
But
in
principle
it
would
be
like
that.
Okay,.
B
A
B
B
A
What
I
was
going
to
do
is
I
was
gonna,
start
doing
the
draft,
and
then
you
and
I
could
sort
of
work
together
on
that
I'll
start
the
basic
part
of
it
and
this
will
be
open
to
the
community.
So
everybody
is
welcome
to
to
jump
in
and
do
that.
But
I
I
was
gonna
say:
let's
get
the
first,
you
know
start
iterating
on
it
and
then
that's
where
we'll
start
to
see
where
items
that
we
want
to
start
working
on
can
actually
be.
A
You
know
we
can
start
to
prioritize
those
items
as
to
seek
to
say
what
we
want
to
start
working
on
sounds
good,
so
I
will
take
the
initial
draft
response
or
schema.
Then
I
will
create
the
initial
draft
and
then
I'll
get
it
out
there.
So
everybody
can
start
iterating
on
it.
I'll
have
that
ready
before
next
meeting.
Okay.
A
C
B
C
The
same
time
it's
4:00
p.m.
so
it's
better
than
6:00
p.m.
I'll.
Try
this
that's
for
sure!
Well
now
it's
5
p.m.
but
still
it's
quite
late,
for
example
in
Asian
and
Pacific
region.
So
for
me,
for
example,
it
would
be
more
preferable
to
do
it,
let's
see
in
European
zone,
so
let's
say
quietly
in
United
States,
but
a
good
for
Asian
and
Pacific
region,
human
that
there
are
people
interested,
but
it
fester
starts
from
people.
So.
C
B
The
the
one
that
seems
to
be
most
most
happy
making
for
your
your
time
frame
is
like
midnight
us
at
midnight
on
the
East,
Coast
kind
of
timeframes
so
and
I'm
not
I'm,
not
opposed
I'm.
Just
saying
like
that's
the,
as
opposed
to
being
them
being
pretty
close
together
on
two
different
days,
and
we
really
having
them
be
really
a
disparate
time
would
be
better.
A
B
C
B
A
A
C
A
B
A
B
A
B
The
it's
the
science
of
when
you
give
someone
a
choice.
They
will
be
less
happy
with
that
choice,
exactly
yeah,
so
you
know
I'm
I'm,
open,
oh,
look
it!
This
is
I
I.
Maybe
you
should
decide
and
like
you,
you,
you
have
a
particular
perspective
on
this
so
and
I
trust
that
perspective.
So
my
point
is:
maybe
you
pick
a
time
and
then
we'll
figure
out
how
to
make
it
work.
Okay,
all
right!
Well,
I
mean
okay,
like
you
have
you
ever
you've
you've
expressed
a
specific
like
okay.
B
B
C
A
That
I'll
need
to
do
on
my
end
is
one
is
we'll
need
to
adjust
the
cig
landing
page,
Huntington
bio.
Whatever
the
time
is
we
choose,
so
that's
corrected
and
number
two
are
the
zoom
that
I'm
using
is
not
the
CDF
zoom
and
the
reason
that
I'm
not
using.
That
is
because
it's
just
been
too
many
problems
with
that
hi
can
I,
have
the
ability,
I
think
I've
got
like
ten
post
keys
that
I
can
give
out.
A
C
Just
assign
all
that
some
items
to
me
because
I'm
probably
the
most
interest
third
person
starting
from
the
next
week,
I,
wouldn't
be
able
to
participate
again,
though
right
now,
it's
hard
to
predict
when
you
can
participate,
but
yeah.
You
can
just
assume
that
everything,
because
on
need
to
implement
until
that,
we
can
put
a
European
meetings
on
hold
just
save
everybody's
time.
Okay,.