►
Description
Jenkins Pipeline-Authoring SIG Weekly Meeting for 20200508
A
B
Awesome
hi
everyone.
Thank
you
for
joining
this
week's
pipeline
authoring
sig
meeting
during
the
course.
The
meeting
we're
going
to
adhere
to
Jenkins
communities,
code
of
conduct,
which,
more
or
less
just
means
to
be
excellent
to
each
other
and
be
nice.
We
are
recording.
So
if
that's
an
issue
for
you
feel
free
to
to
either
not
have
your
webcam
on
or
drop
off,
this
will
be
uploaded
at
a
future
date.
B
B
One
second,
all
right,
I
think
I
can
I'm
not
sure
if
I
can
share
and
message
at
the
same
time
chat
there.
We
go
everyone
all
right.
So
the
the
link
to
the
meeting
notes
is
in
the
zoom
chat
window,
feel
free
to
join
and
add
yourself
to
the
attendees
I
think
we're
gonna
start
today's
meeting
with
Mark,
who
has
something
to
talk
to
us
about
about
the
user
experience
a
quest
coming
up
at
the
end
of
May,
so
mark
I'm
gonna
hand
it
off
to
you
super.
C
Yeah
so
May
25
through
29
we're
going
to
do
a
user
experience,
act
fest
an
online
event
to
encourage
people
to
help
with
improving
the
experience
for
users
of
Jenkins,
and
the
experience
includes
not
just
user
interface
look
and
feel,
which
is
certainly
a
compelling
part
of
it,
but
also
their
experience
with
documentation
and
I.
Think
it's.
The
pipeline
authenticity
is
a
good
fit
for
hey.
There
are
ways
to
improve
user
experience
in
offering
pipelines.
C
Do
in
the
github
repository
for
those
top
40
pages
will
now
work
through
those,
and
it
might
be
a
place
where
the
authoring
sig
might
want
to
look
at
some
of
those
issues,
help
me
process
them
and
think
about
hey
which
of
these
are
pipeline
specific,
and
where
should
that
information
be
placed
so
that
we
can
get
some
good,
first-time
contributor
issues
ready
to
go
for
this
hackfest
on
the
20
from
the
begins?
The
25th
of
May
now
Oleg's
joined
us
and
coleg?
Maybe
there's
more
that
you
want
to
highlight
on
the
hackfest?
Yes,.
D
E
E
A
E
D
The
unofficial
day,
Gary
yep,
so
this
hackathon
will
have
three
matrix
user
interface
is
a
documentation
and
also
spreading
the
work
share.
Your
stories
now
and
basically
the
pipeline
no
drink,
have
some
cases
in
all
three
domains.
So
use
of
the
communication
is
what
Mark
was
played
in
the
world.
Yeah
many
people
create
pipelines,
they
experience
development
tools
so
how
it
pipelines
to
Jenkins,
not
cool,
let's
say
and
user
interface.
There
are
also
some
relevant
tasks.
D
So,
for
example,
one
task
which
we
have
attentively
put
on
there
gently
is
improvement
pipeline
and
rousing
writing
in
the
Jenkins
web
interface,
so
not
in
the
ocean,
but
in
class
in
Jenkins
it's
under
the
discussion,
but
it
could
be
done
and
potentially
pipeline
authoring.
She
has
other
use
cases,
for
example,
the
totals
not
old
map
like
any
integration,
etc.
If
the
seeker
wants
to
focus
together
on
whatever
single
story,
I
think
we
could
easily
edit
to
the
hectare,
scope
and
maybe
to
facilitate
conditions
there.
D
So
scroll
down
there
are
some
project
tricks,
project,
IDs
yeah.
You
can
see
that
there
is
a
lot
of
things
in
TBD
and
because
we
start
s
I'm
going
to
basically
this
week,
but
we
try
to
get
some
stories
on
the
table
already.
If
you
have
any
suggestions,
special
interest
group
would
like
to
work
on
something
together.
D
B
Think
that's
a
good
idea
mark.
Do
you
know
which
repository
did
you
create
those
40
issues
on?
Maybe
we
can
go
through
those
pages
and
see
if
there's
something
that's
particularly
well
suited
to
this
sig
and
see
if
we
can
add
labels
for
the
pipeline
authoring
sig,
so
we
can
track
which
which
issues
are
most
applicable
and
we
can
maybe
coalesce
around
those
yeah.
C
Good
ideas
so
github
calm,
slice,
Jenkins,
CI
or
no
slash,
Jenkins
infra,
Junkins,
IO
yep,
that's
the
one,
and
if
you
look
at
the
issues
there,
there
are
now
66
issues,
whereas
before
they
were
in
the
20s
each
of
these
pages
that
are
right
now
visible.
There
say,
convert
some
wiki
page
to
Jenkins
at
I/o
and
so
what
you
might
actually
use
the
the
github
search
facility.
C
D
C
Well
and
I've
got
lots
of
feedback
from
the
docs
feedback
form
that
is
submitted
with
Jenkins
IO.
So
there's
a
Doc's
feedback
spreadsheet
that
we
collect
feedback
from
the
Jenkins
I/o
pages,
and
many
many
of
them
are
asking
for
hey.
Give
me
better
pipeline
examples.
Give
me
better
this
or
better
that
relative
to
pipeline
yeah.
D
So
probably
we
need
to
move
some
of
these
stories
to
github
issues
and
last
week
we
already
had
a
discussion
about
replacing
a
Google
Form
for
providing
feedback,
but
just
github
wishes
to
keep
things
simple,
but
here
we
haven't
implemented
theater
and
for
me
it's
one
of
the
topics.
I
would
like
to
address
and
use
of
the
documentation.
B
A
Yeah
I
was
surprised,
I
just
yeah
mark
I
mentioned
this.
One
I
went
and
looked
just
commented
on
it.
This
page
is
still
relevant.
I.
Think
I
would
really
like
to
expand
this
into
more
comprehensive
documentation,
but
it's
kind
of
the
best
that
I
know
of
on
low-level
details
of
pipeline.
For
now,
right.
C
Well,
and
that's
that
Devon,
you
and
Stephen
just
just
inspired
exactly
what
we
hope
for
here,
which
is
help
us
identify
which
of
these
things
are
our
value,
which
are
less
value,
and
that
way
we
can,
we
can
make
progress.
I,
put
a
link
into
the
pipeline,
offering
signals
to
the
the
big
spreadsheet
that
collects
all
the
data,
no
need
to
show
it
right
now,
Stephen
just
for
everybody
else's
reference.
C
B
D
D
If
you
see
and
for
example,
Liam
Devon,
you
Steve
and
you
like-
have
a
lot
of
experience
with
drinks,
but
when
documentation,
so
you
could
just
start
creating
get
capricious
for
that,
because
you,
even
if
we
don't
handle
them
during
the
head
cast,
it
would
be
useful
in
the
future.
For
example,
we
are
starting
google,
seasonal
dogs.
Hopefully,
on
one
day
we
will
get
the
positive
response
about
whether
we
accept
it
or
not,
and
if
you
accept
that
the
influent
pipeline,
the
communication
could
be
also
a
potential
project
there.
C
B
Yeah
I
think
it's
twofold
I
think
you
know
the
pipeline,
syntax
generator
I,
don't
want
to
call
it
a
hidden
gem,
but
it's
like
a
trick
that
a
lot
of
people
haven't
heard
of
that
I
interact
with
so
like
exposing
that
in
more
places
and
then
also
in
the
plug-in
development
Docs,
maybe
having
a
best
practices
session
where
we
talked
about
be
great.
If
he
could
provide
snippets
in
your
in
your
Java
doc
that
this
is
exposed
in
our
documentation.
C
Because,
oh,
like
forgive
my
ignorance
but
I,
wasn't
aware
that
Java
doc
was
used
so
that
I
knew
about
the
dot
HTML
files
that
I
can
embed
and
those
those
I've
done
with
the
get
plug-in,
for
instance.
But
it
was
a
lot
of
work.
You're
saying
that
it's
some
of
it
is
extracted
actually
from
Java
doc
for
the
classes
for
the
classes
and
the
attributes.
I.
A
B
A
Java
doc
I
can
you're
a
Java
doc
extensions
that
like
wrap,
HTML,
CSS
classes
to
do
code
snippets
or
something
but
I,
refuse
to
accept
the
world
as
it
is
like.
Maybe
there
is
a
way
that
you
could
write
plug-ins
for
Java
doc
to
do
some
syntax,
highlighting
and
stuff
like
that
right
through
your
Java
doc,
I'm.
A
B
A
D
Could
play
more
magic?
We
have
a
repository
called
pipeline
examples.
We
could
somehow
to
meet
extraction
of
data
from
this
repository,
because
our
jinks
a
website
also
has
a
lot
of
auto
generation.
So
we
could
apply
some
magic
to
take
examples
right
from
Python
examples
repository
but
yeah.
This
magic
would
need
to
be
designed
and
implemented.
It's
definitely
something
we
could
do
during
the
hacker
test,
so
I'm
just
to
document
this
potential
project.
B
B
B
And
then
from
there
once
we
identify
those
we
can
then
see
if
anybody
has
the
capacity
to
to
help
improve
those
or
as
part
of
the
access
to
do
some
improvement
there
there
any
anything
else.
We
want
to
consider
for
the
the
hackfest
any
of
our
features
on
on
the
roadmap
that
we
talked
about
from
like
code
analysis,
you
know,
testing
called
add
user
experience
type
stuff.
Is
there
anything
that
we
think
would
be
a
good
fit
for
a
hackfest?
B
D
Basically,
everything
would
be
a
good
fit
if
you
have
in
the
newbie
friendly
tickets
we
could
also
just
or
if
you
have
a
team
which
would
be
interested
to
work
on
it.
So
yeah.
We
have
a
lot
of
ideas.
We
try
to
do
but
yeah.
Basically,
six
could
just
discuss
what
they
would
like
to
do
together
with
the
kind
of
team
bonding
covalent
or
whatever.
E
B
That's
coming
up
on
the
coming
up
on
the
25th,
so
maybe
one
of
the
accidents
for
those
ones
called
it.
That
has
the
opportunity
is
to
review
the
hackfest
page
so
that
next
Friday
we
can
see
if
there's
anything
that
is
already
on
there.
Potentially
that's
a
good
fit
for
the
goals
of
this
this
SIG
and
see
if
we
can
try
to
break
that
down
into
like
newbie,
friendly
tasking
and
and
all
those
great
things
does
that
sound
like
a
plan.
B
B
All
right
is
there
any
were
there
any
leftover
items
from
from
last
week's
meeting.
I
know
that
we
s
I,
remember
correctly,
we
talked
about
the
pipeline
is
yeah
Mille.
We
talked
about
the
the
new
job
factory
idea
that
Stephen
Foster
had
proposed.
Was
there
anything
from
that
that
we
we
tabled
for
this
time.
E
Not
specifically,
I
still
have
to
write
those
juror
queries.
I'm
not
I
have
not
had
time
to
do
that
so,
but
other
than
that,
the
other
two
things
are
basically
take
a
take,
a
look
at
the
mo
plugin
and
just
give
it
a
try
and
then
Stephen.
You
had
some
sort
of
questions
that
we
had
on
the
in
the
notes.
I.