►
From YouTube: 2022 06 30 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
to
the
european
docs
office
hours
here
on
june
30th
2022.
We
have
a
little
bit
of
an
agenda
today
going
over
a
handful
of
different
things.
A
couple
of
item
updates
from
mark
regarding
the
docs
mailing
list
and
a
couple
blog
posts
that
will
eventually
be
given
shared
in
a
week
or
two.
A
We
have
the
jenkins
lts
changelog
and
upgrade
guide
that
will
be
coming
out
soon
with
the
next
lts
release,
which
is
going
to
be
in
a
couple
weeks
from
upstate
and
mark,
ideally
of
course,
and
then
we
have
vihan
here.
So
if
leon
can
give
us
an
update
about
the
google
summer
of
code,
that
would
be
great
and
then
some
other
items
about
the
java
level
requirement
and
things
that
are
happening
right
now.
A
That
folks,
like
basil,
crowe,
are
helping
us
out
with
and
making
sure
that
everything
is
ready
to
go
for
continuous
improvements.
And
then,
if
there's
some
time
and
we
have
the
chance
to,
we
can
go
over
some
further
localization
with
crowded.
If
alex
is
here,
we
can
pin
that
for
next
time
so
mark.
If
you
want
to
just
kicks
off
talk
about
the
first
couple
items
here
under
the
action
items,.
A
Good
yeah
and
then
the
jenkins,
2.346.2,
changelog
and
upgrade
guide
is
something
that
mark
and
I
are
working
on
and
will
be
working
on
as
we
go
through.
There
was
some
discussion
about
potentially
doing
that
today.
We
can
definitely
come
back
to
that.
If
that
would
be
best
mark,
I
did
want
to
make
sure
everyone
has
a
chance
to
share
their
updates
and
whatnot,
so,
okay,
yeah
that'll,
be
taken
care
of
and
we'll
be
sure
to
update
everyone
when
there's
further
news
about
that.
A
C
Yes
sure
so
in
the
last
meet
I
was
working
on
the
data
types
of
the
steps,
the
parameters
and
bringing
them
up
to
the
top.
So
that
pull
request
is
created
and
it
is
working
fine
for
now
we
are
reviewing
it
for
some
possible
refinements,
so
it
is
not
yet
merged,
but
I
am
sure
it
will
be
that
the
result
of
that
pr
is
pretty
good.
C
C
Also
because
earlier
the
user
had
to
expand
the
parameter
and
then
go
through
the
help
in
order
to
read
this
type,
but
now
it's
there
in
the
top
itself,
so
yeah
that
is
working
fine
now
and
today
I
also
created
a
draft
request
in
the
pipeline
metadata
utilized
repository,
that
is,
a
repository
will
use
to
maintain
the
remote
plugin
manager
that
has
to
be
shifted
from
the
pipeline
step,
docs
repository.
C
So
our
plan
is
to
release
it
as
an
artifact,
so
release
the
metadata
repository
as
an
artifact
on
maven,
which
can
then
be
imported
onto
the
pipeline
step
docs
for
the
tree
and
used
basically
as
a
dependency,
and
then
we
can
get
rid
of
the
classes
which
are
there
locally.
C
C
So
that
is
the
process
that
we
also
wanted
to
take
some
help
from
the
community,
because
neither
christian
or
high
have
the
permissions
in
order
to
push
for
the
gen
or
jenkins
group
or
maven.
So
that
is
something
that
will
require
some
help
from
the
community
in
the
upcoming
week
and
yeah.
I
guess
no,
that's
more
or
less
of
it.
So
yeah.
A
C
Sure
so
I
can
demonstrate
the
data
type
of
request
if
you'd
like
that
yeah.
Why
not?
Let
me
go
ahead
and
just
run
it
real
quick.
So
meanwhile,
we
also
reviewed
the
plugin
list
for
requests
and
asked
for
some
feedback
from
tim
and
mark.
I
think
it
is
best
suited
not
to
work
further
on
that
particular
feature.
We
can
leave
it
dangling
as
it
is
over
there
and
in
the
future.
C
A
And
what
kind
of
things
can
we
do
as
the
community
like
for
reviewing
the
pull
requests
and
anything
else
that
might
be
coming
up?
What
can
we
do
to
help
out
in
these
cases,.
C
I
think,
as
of
now,
I
have
three
pull
requests
that
are
being
like
left
to
merge
a
small
one.
So
one
is
that
plug-in
list
which
I
mentioned
so
nothing
to
be
done
on
that
side.
But
on
a
more
general
note,
I
think
whatever
ui
based
changes
are
there
I'll
share
on
the
docs
channel
the
screenshots
and
everything
like
I
did
for
the
the
data
I
think
and
for
the
more
back
end
kind
of
stuff
the
release
and
all,
I
think,
we'll
we'll.
C
Let
it
we'll
let
you
know
on
the
channel
itself.
So
if
you
require
any
help
as
such,
but
for
the
pull
request-
and
I
think
I
think
everything
is
going
as
smooth
as
it
can
probably
yeah.
So
I'll
just
share
my
screen
real
quick
now
I
guess
yeah
this
one's.
C
Okay,
so
can
you
see
the
screen
pipeline?
Groovy
library?
Is
this
one?
Yes,
all
right,
so
I'll
just
show
you
the
main,
the
larger
one
so
that
you
can
get
an
idea.
So
what
I
did
to
see
the
page
size
was
I
disabled,
the
javascript
altogether.
So
all
these
things
got
expanded,
but
we
can
see
from
the
flow
itself.
C
So
these
all
are
there
on
the
top
now,
so
you
can
see
the
data
type
right
beside
the
name
and
for
larger
things
such
as
this
one
when
you
expand
it
earlier,
the
string
was
coming
all
under
under
this
stuff,
so
we
have
to
go
through
this
stuff
and
until
the
time
you
reach
there,
you
actually
forget
what
that
type
was
really
about.
So
that
comes
out
of
nowhere,
so
that
space
gets
saved
as
well,
and
this
is
now
coming
everywhere.
C
So
I've
handled
every
particular
situation
because
there
are
a
couple
of
different
types
of
nestings
going
on
under
here,
so
all
of
them
are
taken
care
of
now
and
all
in
all,
I
think
this
feature
is
working
fine
with
the
pull
request
so
yeah.
This
was
a
little
demonstration
for
the
scene.
A
Yeah,
thank
you
so
much
that
looks
great.
That
navigation
looks
a
lot
cleaner
and
everything's
very,
very
nicely
placed
and
aligned.
So
that's
wonderful!
Thank
you.
So
much
for
all
this
work
and
everything
you're
doing
for
the
jenkins
project.
It's
really
appreciated.
A
Great
cool
so
now
that
we've
gone
through
the
google's
number
of
code,
just
a
couple
other
points
here,
so
with
our
weekly
release
last
week
or
or
was
it
this
week,
I
forget
now
mark
which
was
it
last
week
of
this
week's
weekly
release
that
pushed
the
java
level
requirement
this
week
right
this
week,
yep
yeah,
okay.
A
So
with
the
weekly
release
line,
the
java
11
java
11
is
required,
and
so,
alongside
the
job
11
requirement,
there
are
other
improvements
and
enhancements
and
upgrades
that
need
to
be
done
stuff,
like
jetty
and
being
upgraded
from
version
nine
to
ten.
There
are
some
other
api
upgrades
that
might
need
to
have
that
need
to
happen
as
well
stuff
like
the
servlet
api
specifically,
and
the
encoding
will
be
changing
to
utf-8
instead
of
code,
ascii
doc.
So
a
lot
more
uniform
and
consistent
across
organizations.
A
And
mark
is
there
anything
else
on
the
job
11
improvements
that
we
should
be
aware
of
or
note
here
or
does
that
cover
the
general
idea.
A
Yeah
no
worries,
of
course
great,
so
that
actually
takes
care
of
the
agenda
pretty
quickly
mark.
Did
you
was
there
anything
else
you
wanted
to
go
over
or
take
a
look
at
here.
B
So
vihan
vihan
had
made
mention
of
something
that
I
think
is
worth
a
question
to
him.
So
vihan
you
indicated
you
and
kristen
may
not
have
permissions.
I
think
we
gave
kristen
permissions
to
the
permissions
she
had
previously.
That
should
have
allowed
her
to
release
new
versions
at
least
of
pipeline
step
stock
generator
was
that
what
you
were
referring
to,
or
is
there
something
else.
C
I
was
referring
to
the
maven,
deploy
permissions
so
basically
under
the
groups
that
we
have
right
now.
So,
for
example,
what
I,
what
what
I
was
trying
to
do
was
we
can
define
a
jenkins
file
for
that
metadata
repository,
and
in
that
we
will.
We
will
push
to
the
neumann
repository
for
that
particular
artifact.
C
So
for
that
pushing
into
the
main
repository,
I
think
it
requires
some
different
permissions
and
I'm
not
sure
how
it
is
done
and
probably,
if
I'd
get
some
idea
of
a
similar
repository
and
to
see
how
things
are
happening,
so
maybe
some
other
artifact
to
see
how
it
is
working
out.
Then
I
can
maybe
just
take
take
some
stuff
from
the
jenkins
file
and
after
that
whole
thing
is
released
ready.
Then
we
can,
then
we
can
ask
about
the
permissions
and
all
required
to
do
the.
B
So
what
incrementals
are?
Is
they
provide
a
facility
for
jenkins
plugins
to
do
to
save
the
results
of
pull
request,
builds
so
bruno
submits
a
pull
request
to
improve
the
git
plug-in
and
when
he
does
that
his
pull
request
actually
becomes
the
the
binary
of
his
pull
request
becomes
visible
for
other
people
to
consume
through
repos.jenkins.ci.org,
and
they
then
can
refer
to
it
by
this,
this
incremental
syntax.
So
this
special
version
number
that
says
this
is
an
incremental,
and
this
page
talks
about
how
to
do
that.
B
You
may
want
to
explore
that
I'm
not
sure
if
it
will
work
with
with
non-plug-in
components,
but
I
would
expect
it
to
work
with
them,
so
you
may
want
to
look
at.
Could
we
enable
incrementals
on
pipeline
steps
doc
generator,
for
instance,
if
you
need
to
do
something
with
it?
Ultimately,
I
think
the
thing
you
want
incrementals
on
is
probably
the
the
library
you're
extracting
right,
rather
than
the
generator
itself,
but
but
it's
pipeline
step
stock
generator
gives
you
a
place
to
test
drive
that
if
you'd
like
sure.
C
So
we
also
saw
some
other
non-plug-in
repositories
that
had
a
release
type
of
feature.
So
the
first
thing
that
we
looked
at
was
the
plugin
installation
manager
tool
so
that
had
a
github
actions
and
everything
set
up
for
it,
so
it
had
releases
also,
but
the
one
thing
that
I
couldn't
find
for
it
was
a
maven
artifact,
so
I
don't
think
it
is
published
as
a
maven
artifact
on
the
repository.
So
basically
I
was
looking
at
the
maven
repository.com
for
all
the
repositories
associated
with
jenkins.
B
Well,
so
let's
your
question
is:
is
a
good
one?
Let's
take
a
look.
I
think
I
can
show
that
the
maven
that
the
plugin
installation
manager
is
in
fact
deploying
to
the
repository.
So
let's
are
you?
Okay,
if
we
explore
that
for
just
a
little
bit
sure
sure
I
would
love
that
okay,
so
kevin
I'm
going
to
put
another
hyperlink
into
the
document
and
let's,
let's
use
this
as
our
test
case,
so
plugin
installation
manager.
B
Pr
sample
and
let's
try
it
so
so
there's
the
kevin,
if
you
can
click
through
that
link,
what
that
takes
us
to?
Oh
nice,
dark
theme:
well
done,
okay,
so
what
that
takes
us
to
is
here
are
components,
including
jar
files
with
interesting
version
numbers
inside
their
the
name
of
the
file.
Now,
if
we
copy
that
one
of
those
file
names,
I'm
going
to
try
searching
repo.jenkinci.org
to
see
if
I
can
find
that
thing.
B
B
B
B
B
B
Okay,
so
what
you
should
see
on
screen
is
the
artifactory
location.
B
B
D
I
may
have
a
stupid
question:
sorry
for
interrupting,
but
okay,
we
have
seen
that
maybe
the
plugin
could
the
build
could
store
the
plug-in
artifacts
in
that
rt
factory
or
j4.
Whatever
the
repository.
B
B
So
the
artifacts
can
be
consumed
without
requiring
any
authentication,
and
so
so
as
an
example
as
an
example
that
that
I
specifically
use
when
I
need
to
make
a
change
to
the
git
client
plug-in
I'll,
make
the
change
in
the
git
client
plug-in
and
then
in
the
git
plug-in.
I
will
reference
that
changed.
Pull
that
the
pull
request,
incremental
bill
of
that
pull,
request
and
use
it
or
when
I
need
to
test
drive
a
an
incremental
plug-in.
B
B
B
B
Okay
and
it
does
not
have
a
dot
mvn
directory
okay,
so
what
that
tells
me
is
plugin.
Installation
manager
is
able
to
deploy
incremental
builds
and
the
reason
it
can
is
because
it's
been
incrementalified.
I
know
that's
not
a
word,
but
it's
been,
it's
been
given
incremental
capability
and
the
way
that's
been
done
is
through
this
page.
The
instructions
here
on
the
jenkins.io
page,
incrementals,
developing
components
in
parallel,
and
what
this
tells
us
is
to
do
this.
B
We
say
incrementalify
and
we
submit
a
pull
request
on
the
way
to
say:
is
this
the
right
one?
Oh,
no!
Let's
look
at
this
one,
no!
No!
That
should
be
it
that
that
was
okay
back
sorry,
reading
reading
more
carefully
here,
so
I
think
what
we
do
is
we
run
this
command
and
if
I
do
that
again,
everybody's
okay
with
me
doing
this
kind
of
live,
live
manipulation.
B
Okay,
no
plug-in
found
now.
I
think
this
may
be
vian's
question.
Why
doesn't
this
include
the
jenkins
parent
palm
vihan?
Didn't
you
ask
that
question
earlier?
Oh,
yes,
I
didn't.
I
think
you
did,
and
it
may
be
that
in
order
to
do
an
incremental
with
this
thing,
because
if
we
look
at
the
palm.xml
file
of
this-
and
we
compare.
D
B
With,
let's
see
what
was
it
core
plug-in
installation
manager
palm
here,
the
plug-in
installation
manager
has
the
jenkins
palm
as
a
parent.
This
one
has
no
parent,
so
okay
vihan,
I'm
going
to
just
be,
as
ignorant
as
I
can
and
try
this
anyway.
B
B
Okay,
so
there
this
does
not
this
message
is
not
unresolvable.
I
I
think
it
could
be
fixed,
because
it's
telling
me
something
that
it
sees
is
wrong,
and
if
I
look
at
scm
I
may
even
see
what's
wrong
yeah.
For
starters,
this
is
wrong.
B
B
B
C
This
helps
me
a
lot
actually
so
maybe
of
one
very
knife
type
of
question
so
earlier
I
was
actually
looking
into
the
mvnrepository.com
and
I
have
sent
the
link
on
the
chat
actually,
and
I
thought
that
was
the
artifact.
That
was
the
place
where
we
store
all
the
groups
and
the
artifacts,
and
I
was
able
to
find
most
of
them
over
there,
but
then
I
also
found
out
repo
dot.
C
C
B
C
B
D
Yes,
sorry,
that's
because
the
git
protocol
is
not
available
anymore
for
github.
That's
it
that's
correct!
Exactly.
B
C
And
I
guess
one
more
question
that
I
would
put
here
and
that
would
be:
is
there
a
need
to
set
up
github
actions
for
the
metadata
users
that
will
create
so
for
the
plug-in
installation
manager?
We
have.
We
have
the
release
system
on
github
itself.
So
do
you
think
it?
It
will
have
any
real
use
for
the
pipeline.
Measured
bills.
Also.
B
B
Okay,
we're
gonna
have
to
go,
find
it
the
hard
way.
The
search
engine
is
not
finding
it.
The
way
I
wanted
developer
guide
how
to
guides
release
setting
up
automated
plug-in
release.
So
this,
I
think
the
same
technique
for
automated
automated
releases.
That's
being
done
for
for
other
tools
could
be
done
for
for
the
pipeline
steps.
Documentation
generator.
Now
the
plug-in
installation
manager
tool
isn't
using
those
as
isn't
using
this
particular
form
of
delivery.
B
It's
still
released
and
still
released
manually,
but
but
the
idea
of
automating
release
is
a
good
one
and
your
question:
should
we
be
doing
other
things?
Let's
look
at
some
of
the
actions
that
are
on
that
repository
just
to
see
so
release
drafter?
Yes,
if
you
don't
have
release
draft
on
pipeline
step
stock
generator,
you
want
it.
It's
a
good
thing
to
have
and
publish
artifact
isn't
harmful.
B
It's
it's
a
nice
thing.
What
what
we
get
with
publish
artifact
is
when
I
look
at
the
list
of
releases
here,
this
list
of
assets
includes
the
jar
file
and
that
arrived
there
because
of
that
github
action,
so
that
github
action
is
smart
enough
to
go,
find
the
place
that
builds
this
thing
and
copy
it
into
github
for
convenience.
B
B
Yes,
it
is
okay,
good
there
we
go
okay,
so
right
now
this
doesn't
have
any
actions
defined,
but
I
don't
know
that,
for
instance,
it
also
defines
no
releases
and
so
the
release
drafter
thing
won't
help.
Much
now
you
may
you
and
kristen
may
together,
say
hey.
We
should
start
using
releases
so
that
we
have
known
points
where
we
can
declare.
This
was
what
we
delivered
in
this
release
and
if
so,
then,
release
drafters
a
good
help.
C
Sure
so,
if
I'm
not
wrong
in
saying
the
way
we
use
github
actions
for
jenkins
repositories
is
just
to
document
our
changes
as
releases
and
maybe
to
like.
We
saw
there
maybe
to
provide
links
of
those
jars
as
the
releases
come
so
that
that's
it
right.
So
the
repo
is
getting
pushed
to
the
repo
and
everything
that
is
happening
with
a
different
way.
So
with
the
jenkins
files
jenkins
file,
I
guess,
and
the
jenkins
files
file
for
that
uses
the
build
plugin
thing.
B
B
B
B
So
now
I
don't
know
if
any
of
those
this
one,
the
cd
one,
may
be
quite
helpful
to
you
and
that's
described
on
the
jenkins.io
page
here
this
one
talks
about
automated
plugin
release.
This
is
really
telling
people
how
to
do
continuous
delivery,
and
part
of
that
is
this.
This
github
action,
other
parts
require,
are
described
here
so
right.
So
it
talks
about
you
need
to
make
a
change
in
the
repository
permissions
update
or
you
need
to
configure
release
drafter.
B
You
need
to
configure
a
github
action
for
the
continuous
delivery
workflow
you
need
to
configure
dependable
those
kinds
of
things
right
did
did
vhan.
Does
that
help
you.
C
Yeah,
it
helps
a
lot
actually,
okay,
so
the
the
main
idea
is.
We
can
treat
a
non-plug-in
repository
as
a
plug-in
repository
and
use
these
steps
over
there.
So
is
there
anything
that
we
have
to
prepare
the
repository
before
applying
these
changes.
C
B
B
B
Thank
you
yes,
so
so
vihan
you're.
Okay,
then,
with
the
idea
that,
if,
if
you
want
to
do
an
automated
release
of,
if
you
want
to
do
releases
of
pipeline
step
stock
generator
and
that's
something
to
negotiate
with
kristin,
I
think
it
makes
sense
if
you
want
to
do
releases
of
pipeline
steps
doc
generator,
then
these
these
steps,
the
enable
release
drafter
enable
incrementals,
enable
continuous
delivery
are
all
good
choices.
I
think
right
now
the
way
pipeline
step
stock
generator
is
used.
Is
it's
taking?
I
assume
it's
taking
the
most.
C
So
this
is
something
that
we
can
definitely
look
after
our
artifact,
the
artifact
release
thing
is
set
up,
so
this
is
the
next
big
step
for
us.
D
C
Super,
yes,
perhaps
you
can
link
yeah.
It
was
a
schedule
build
plugin,
for
which
we
saw
the
different
github
actions
right
the
cd
and
everything
it
was.
C
A
Great,
yes,
that
looks
like
we're
all
set
for
today.
We
are
up
against
time,
so
I
want
to
be
conscious
and
give
everyone
another
time
back.
So,
if
mark,
if
you
could
stop
the
screen,
recording.