►
Description
Jenkins Pipeline-Authoring SIG Weekly Meeting for 20200515
A
Hi
Ron
thanks
for
joining
this
week's
pipeline
authoring
sig,
like
all
SIG's,
we
adhere
to
the
Jenkins
community
code
of
conduct,
which
basically
means
the
excellent
to
each
other,
looks
like
we
have
a
pretty
small
attendee
list.
Some
people
had
some
conflicts
today,
but
we
can
recap
last
week's
action
items
and
see
if
there's
any
new
topics
we
want
to
talk
about.
The
link
to
the
Google
Doc
is
is
in
the
zoom
chat
and
share
my
screen
to
show
it.
A
So
last
week
we
talked
about
the
40
pages
that
Mark
had
highlighted
for
opportunities
to
improve
documentation.
We
considered
going
through
each
of
those
issues
and
labeling,
which
ones
are
best
aligned
to
this
sig
I.
Guess
all
one
one
question
about
that:
how
would
we
go
about
adding
labels
to
these
PRS?
Who
has
the
authority
to
add
labels.
B
So
for
labels
right
now,
so
we
have
two
teams.
One
team
is
copy
editors,
so
basically
the
team.
We
should
have
use
pull
requests
and
we
have
recently
introduced
the
3h
team,
which
is
basically
responsible
for
initial
processing
of
issues
and
pull
requests,
and
they
also
have
permissions
to
label
items.
A
A
A
B
A
The
others
yeah,
so
we
also
talked
about
the
access.
That's
going
on
see.
We
added
a
discussion
topic
for
today:
Jenkins
UI,
UX,
access
and
pipeline
authoring,
so
that
I'm
trying
to
think
you
know,
is
there
an
opportunity
for
the
access
is
blue
ocean
and
device
great
there
is.
There
may
be
something
around
improving
the
pipeline
visualization
in
the
Jenkins
UI
in
a
way,
that's
not
as
Extreme
as
blue
ocean.
That
would
be
within
scope
for
that
yeah.
B
And,
moreover,
that
is
already
a
project
idea
for
this
I'm,
not
sure
whether
we
published
it
on
the
website.
But
it's
definitely
on
the
student
document,
so
we
have
a
Google
Doc,
which
is
linked
from
the
mailing
list.
Just
second
I'll
put
a
link
to
the
meeting
notes
and
in
this
document
we
will
accept
any
project
ideas
but
yeah
as
long
as
that
they
related
to
user
experience
and
as
long
as
there
is
somebody
behind
them,
who's
interested
to
work
on
them
or
could
coordinate
the
effort.
So
just
a
second
I'll
paste.
B
B
Well,
it's
easy
to
say
that
the
problem
that
I'm
not
really
ready
to
commit
enough
time
to
do
that.
But
if
there
is
strong
interest
from
pipeline
of
drinksy
home
I
were
to
work
on
that
during
the
hackathon.
It
would
be
nice,
maybe
something
closer
to
the
current
state.
So,
for
example,
we
have
templating
engine
which
would
be
somehow
somehow
contribute
to
user
experience
same,
for
example,
for
remote
file,
plug-in
for
multi
branch
or
maybe
even
for
Python.
In
zmo.
B
A
B
Mostly
Luke
and
fuel,
so
just
we
have
three
tricks
there.
A
one
track
is
user
interface,
which
includes
you,
look
and
feel
problem
negation
and
all
of
the
improvements
are
also
accessibility
and
other
topics.
There
is
user
documentation
topic
which
again
may
include
some
pata
any
related
stuff
example
documenting
features
and
the
including
features
into
the
main
documentation.
Because
right
now
we
have
a
pretty
good
documentation,
for
course
pipeline
on
Jenkins
I/o.
B
A
I
think
that's
a
common
challenge.
I
see
people
run
into
you
right.
It's
like
they'll,
see
a
pipeline
step
and
they'll
sort
of
look
in
the
pipeline
documentation,
but
that
steps
coming
from
a
particular
plugin,
so
I've
seen
that
people
have
like
a
hard
time
figuring
out.
Where
is
this
particular
method
being
contributed
from
and
where
the
documentation?
For
that.
A
B
A
Yeah
I
think
anything
we
put
on.
There
should
be
something
accomplishable
within
the
five
days
or
you
know,
maybe
a
prototype
of
something
that
could
be
accomplished
in
five
days
and
then
maybe
the
folks
that
participate
can
drive
it
after
the
access
to
finish
it
off
or
something.
But
abstract
ideas
are
going
to
be
hard
to
actually
make
tangible
progress
on
unless
there's
already
like
wireframes
or
something
like
that.
B
B
B
B
D
B
Me
it's
just
use
cases
so,
for
example,
by
plan
we
can
have
area
like
tools
and
then
we
put
plugins
like
pipeline
million
plug-in
or
whatever.
Then
we
have
every
multi
branch
pipeline
and
then
we
put
remote
remote
files.
Again
we
have
a
core
area
and
they
we
put
all
court
against
like
pipeline
job,
etc.
D
C
C
B
C
B
So
do
you
see
new
top
right
now?
Yeah,
okay,
so
here's
a
plug
inside
again
yeah.
There
is
a
lot
of
things
under
development
there,
but
they
significant
improvements.
So
here
you
can
massage
I'm
just
by
planner
for
whatever
different
sort,
things
relevance
most
installed,
trending,
it's
the
recent
installations,
title
etc,
and
the
Daniel
Beck
has
recently
introduced
a
metadata
for
12
for
plug-in
rating.
B
Daniel
started
doing
advanced,
or
for
that
you
can
also
search
for
particular
cases.
So,
for
example,
here
you
can
see
that
there
are
labels
right
now.
We
do
not
have
label
for
multi
branch
pipeline,
for
example.
It's
something
we
could
fix,
but
yeah.
These
labels
are
basically
managed
right
now
through
github
topics.
So
us
plugin
being
here,
can
just
put
a
number
of
labels
and
they
able
automatically
they
all
the
appear
on
the
plugin
side
in
a
few
hours.
So
I'm.
B
A
B
A
B
Yeah,
oh
she's,
not
exactly
so
it
it's
not
tolerant
mistakes!
Yeah!
Here
you
can
see
that
the
plug-in
has
no
labels
at
all.
So
right
now
it
won't
appear
and
the
labels
are
useful
because
labels
also
appearing
in
plugin
manager
now,
so
it's
not
only
plug-in
side
in
Jackie's
plugin
manager,
all
labels
appear
and
thanks
to
Daniel.
He
keeps
improving
that
part
as
well.
B
B
Okay,
so
it's
here
it
has
a
pipeline
label,
for
example,
for
this
plug-in
and
guess
we
really
need
a
multi
branch
with
label,
because
with
the
current
team,
you
need
to
it
description
to
understand
what
it
is
exactly
about.
Oh
maybe
it's
actually
better
to
be
name
of
the
plug-in
at
least
display
name,
I,
don't
know
yeah.
C
And
I
going
for
that
dragon.
Yes,
maybe
just
for
the
others,
I
mean
even
even
like
a
person
who
is
experienced
hard
years
in
drinking's
each
community,
sometime
tough,
to
find
what
you
are
searching
for.
Maybe
indexing
the
documents
from
with
from
the
gift
bleating
files,
maybe
can
help
people
what
they
need:
yeah
techniques,
so.
C
B
C
B
Yeah,
so
what
do
we
started
doing
in
Jenkins
to
digital?
You
created
setup
wizard.
It
offers
something
against
by
default.
It
also
offers
some
additional
plugins,
but
yeah.
This
functionality
could
be
much
better.
For
example,
if
you
use
star
changes,
you
can
also
it
asks
you
whether
you
would
like
to
get
plugins,
for
example,
for
the
night
off
iOS
development.
So
right
now,
I
want
to
show
anything
or
no
shows.
So
there
is
some
button
query
on
the
website,
but
yeah
generally,
when
you
use
these
filters
and
stuff
wizard,
you
get
the
same
advice,
but.
C
Edd
the
chart
that
you
showed
I
think
it's
really
useful,
because
I
get
busy
keeps
on
like
overall
picture
about
what
we
have
also,
maybe
we
can
just
define
or
the
right
this
chart
for
some
groups
also
maybe
like
for
pipeline
a
child
that
which
plugins
are
the
next
to
pipeline,
as
you
suggested
well,
maybe
like
we
can
just
change
this
graph
to
like
maybe
dotnet
Moodle
pinky.
All
the
government
related
charts
plugins.
That
style
maybe
can
help
there.
B
C
B
Had
a
blog,
not
even
a
blog
post,
I
sent
a
couple
of
messages
to
the
development
increased
about
that
idea
of
Mark
has
also
created,
for
example,
a
blank
recommendations
yeah.
Maybe
we
could
have
a
session
about
how
basic
how
to
properly
label
your
plugins
aside
to
help
users
discover
them.
Yeah
feels
like
a
user
experience.
C
D
B
D
A
All
right,
I
found
that
it's,
it's
really
helpful
for,
like
helping
people
find
the
logs
in
the
in
the
jenkins
la
guerre,
something
actually
went
wrong
right,
I,
usually
administer
pipelines
for
development
teams
and
I'll.
Just
get
links
to
broken
builds,
let's
say
like
I,
don't
know
what
happened
because
they
pull
up
the
build
bog
and
it's
it's
really
long
and
I
can't
find
the
exception.
So
blue
oceans
made
it
really
nice
to
be
like
look
at
the
red
bubble.
The
red
bubble
is
the
thing
that
failed.
You
should
go
read
the
logs
thing,
yeah.
B
That's
right
so
yep
person
there
would
be
really
interested
to
somehow
detach
the
browsing
engine
from
lotion.
So
one
of
the
big
ocean,
architectural
problems
is
that
it
was
created
in
opinionated
way.
So
we
provide
some
advantages
because
it
provides
put
out
a
good
user
experience
out
of
the
box,
but
it
has
significant
disadvantages
because
you
can
actually
extend
that
and
also
it
declares
a
lot
of
dependencies.
B
B
Possible
to
make
the
plug-in
I
mean
it
would
be
a
plugin,
but
it
would
be
still
a
part
of
the
Jenkins
web
interface
so
without
creating
new
pages,
whether
it's
possible,
to
put
it
right
in
the
Jing
escort
likely,
not
because
the
ocean
requires
a
lot
of
pipeline
specific
stuff,
so
I
would
rather
expect
it
to
become
a
part
of
pipeline
playing
inside.
Not
a
part
of
the
jinkies
called
I
might
be
wrong
because
well
in
principle,
you
can
provide
road
interfaces
in
jackets
code
and
then
somehow
the
pipeline
is
dead,
but
yeah.
A
B
Would
be
so,
somebody
is
interested
to
work
on
that
at
some
point.
I
was
really
thinking
about
doing.
Could
it
on
my
own,
but
for
me
the
problem
this
time
so
I
haven't
even
started.
I
also
know
for
sure
that
Felix
discovered
on
the
topic
he
was
presenting
it
at
you
excessive
meeting,
but
it
also
the
conclusion
that
would
require
a
lot
of
time
to
make
it
happen.
A
B
B
A
A
B
Be
quick
update
for
me,
so
I
returned
back
to
the
development
of
edging
his
forerunner
one
thing:
I
did
just
basically
stopped
all
the
functionality.
So
now
you
can
really
build
and
test
the
project.
I
plan
to
revive
my
being
a
project
for
using
Bojangles,
followed
another
four
pipeline
testing.
So
basically,
integration,
testing
framework
based
on
that
and
separate
topic,
which
I
am
planning
to
do
quite
soon,
is
to
include
Payton
cómo,
lo
plug-in
right
inside
Jenkins.
For
long
because
is
incorporated
project
itself,
so
I'm
pretty
happy
to
do
such
change
so
actually.
C
B
B
C
I
implemented
these
special
steps
with
their
own
code
blocks
like
with
my
month.
We
count
all
the
credentials
and
also
directly
step
so
I.
Do
this
the
zero
point,
three
erosion.
So
my
next
step
is
to
the
implement
this
UI
converter,
so
I
find
a
way
to
add
my
link
to
my
syntax
page
and
also
I
would
like
to
maybe
in
the
future
enable
Python
is,
you
know
in
pipeline
type
itself,
so
it
is
only
now
available
via
pipelines,
but
maybe
in
future.
C
C
B
A
B
A
The
last
time
since
the
last
time
we
spoke,
we've
got
inside
IO
project
roadmap.
So
we
have
a
new
road
map
item
for
the
to
do
release
with
a
scope
document
that
outlines
all
of
all
of
the
things
that
I'm
working
on
as
part
of
the
the
to
dot
our
release.
A
lot
of
it
is
like
internal
code
clean
up
so
that
it's
a
little
easier.
B
A
Jenkins
pipelines
work
so
I'm
going
to
be
working
on
fixing
that
and
improving
the
integration
between
the
templating
engine
and
workflows.
Cps
itself,
I
made
a
very,
very
pretty
picture
that
visualizes
the
jte
source
code
because,
at
least
from
my
perspective,
the
hardest
part
for
jumping
into
a
codebase
and
helping
out
is
knowing
like
where
to
get
started.
A
A
A
A
B
The
first
step
is
to
have
new
comer
friendly
issues,
so
in
github
you
can
create
an
issue
labeled
with
a
good
frustation
and
if
it's
well
described
as
such
users
tend
to
pick
them
up
because
github
right
now
yeah
they
do
some
turrican
to
length
around
this
label.
So,
for
example,
when
a
newcomer
contributor
who
looks
at
the
repository,
they
get
an
offer
that
hey.
Do
you
like
this
project?
Would
you
like
to
contribute?
B
B
B
D
It's
an
intentional
and
intentional
choice
there,
because
we
don't
have
the
complications
that
we
have
with
plugins,
where
we
have
to
be
able
to
do
security
releases
and
keep
security,
bug
reports
hidden
the
we
just
don't
get
security
bug
reports
to
Jenkins
do
so.
For
me,
it's
a
great
excuse
to
learn
how
to
try
to
fit
github
issues
into
the
Jenkins
project,
workflow
to
see
where
they
fit
and
where
they
don't
well.
B
So
yeah
Marcus
totally
right.
If
we
talk
about
Jenkins
I
know,
but
even
in
researching
to
tell
you
it
actually
works
pretty
well
these
days
so,
for
example,
give
completely
attention
so
hey
if
I
want
to
create
an
issue
here:
good,
oh
I,
don't
okay,
but
I
just
get
to
pop
up
here
at
the
port,
a
security,
vulnerability,
yeah
check
out
the
project
security
policy.
So
what
happens
we
inject
metadata
on
the
top
level.
This
metadata
basically.
B
Injects
Falmer
to
all
our
repositories,
which
recommends
that
the
security
reporting
flow.
It
looks
even
better
if
you
have
issued
templates.
So,
for
example,
in
this
repository
we
have
issued
templates
configured
and
here
you
what
report
feature,
requests,
etc,
and
they
participated
to
the
liability.
It's
here
because
I
mean
github,
has
automatic
processing
of
metadata
and
the
basically
it
shows
you
the
same
page
here
again:
it
pulls
it
from
veronyka's
organization
wide
metadata.
B
A
B
B
So
with
something
I
had
in
mind
when
I
started
both
get
half
of
the
mission,
but
then
I
switched
to
other
tasks
and
basically
I
haven't
really
touched
that,
but
you
could
try
anyway
right
now.
You
can
just
basically
take
these
files
and
copy
the
repositories.
So
it's
not
something
like
the
rocket
science.
C
A
B
B
Some
advantages,
so
the
real
disadvantage
of
github
is
that
you
have
difficulties
with
linking
multi
repository
issues
and
projects,
for
example,
now
on
the
jenkees
project.
We
have
some
multi
organizational
projects
like
this
ones,
but
it's
not
that
convenient
as
it
is
in
Judah.
But
if
your
project
is,
is
the
latest
or
not,
then
the
top,
which
issues
is
quite
convenient
to.
A
B
B
I
just
want
to
say
that
we
did
a
lot
of
research
about
how
to
improve
contributions
before
Oktoberfest
last
year,
and
we
also
worked
a
lot
of
data
that
basically,
it
happens.
Just
is
much
more
effective
for
Promotion
Committee,
promoting
contributions
when
jenkins
data,
which
is
slightly
not
surprising,.