►
From YouTube: 2022 07 12 Jenkins Infra Meeting
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
B
A
B
Sorry
asked
the
question
again:
I
was
working
on
the
jenkins
weekly
release.
Oh
good
you're,
asking
about
that.
I
was
multitasking,
that's
very
dangerous!
So
yes,
the
weekly
release
has
been
published
to
artifactory
so
to
the
repository
the
changelog
is
not
published.
I
just
completed
an
edit
on
it,
we'll
push
it
and
there's
more
to
do
on
the
checklist,
so
so
checklist
is
not
yet
complete,
but
the
coming
soon.
No
no
issues
detected.
B
B
That's
that's
good.
We
like
that
there
may
be
some
instability
or
some
surprises
there,
as
those
javascript
libraries
are
updated.
Previously,
our
dependable
configuration
was
incorrect.
It
was
not
detecting
javascript
updates
that
were
needed.
That
alex
brandis
corrected
that
mistake
and
we
suddenly
got
a
flurry
of
you
need
to
update
this
javascript
and
this
and
this
and
those
are
all
good
things.
B
Likewise,
if
not
two
three
four
fifty
nine,
then
the
next
one
will
upgrade
from
jetty
nine
to
jetty
ten
and
the
jetty
nine
to
jetty
ten
upgrade
is
is
a
key
component
of
jenkins.
Jetty
is
the
the
thing
that
provides
http
services
for
us
it
it
handles
http
and
https,
and
and
that's
a
good
thing,
because
the
jetty
project
has
declared
the
end
of
community
support
for
jetty.
B
A
Brazilian
community
told
there
is
no
known
issue.
I
thought
that
we
would
have
some
issues.
So
if
it's
ready,
let's
get
started
as
soon
as
possible,
that
will
provide
insights.
B
Well,
I
I
would
love
to
see
weekly.ci.jenkins.io
switch
to
java
17..
I've
got
an
unreported
issue
that
I
need
to
investigate
further
when
I
switch
my
production
instance
from
jdk
11
to
jdk
17.
I
got
surprising
messages
in
my
agent
logs,
but
I
can't
duplicate
it
and
I've
tried
with
a
brand
new
creation.
I
still
can't
duplicate
it.
So
nothing
for
you
to
note
here,
because
I
don't
know
of
a
repeatable
issue.
B
A
Okay,
the
challenge
for
us
will
still
be.
We
will
have
to
add
gdeca
17
next
to
gdk
11
on
our
agents
for
the
virtual
machines.
It's
not
an
issue,
because
we
are
it's
already
the
case,
so
we
only
should
update
the
ec2
templates
to
start
the
agent
with
opt
jdk
17
instead
of
tdk
11.,
so
for
virtual
machines.
That
will
be
really
easy,
however,
that
might
require
us
to
add
more
content
to
update
our
docker
container
images,
but
that
effort
will
be
required,
no
matter
when
we
do
it.
A
B
I
like
it,
and
I
think
we
take
it
relatively
low
priority,
but
yeah
I
like
for
me
that
we
we
eventually
we
we
certainly
want
java
17.
and
we
it
was
very
good
for
us
when
we
switched
ci.jenkins.io
from
8
to
11
a
few
years
ago.
It
gave
us
lots
of
experience
and
even
better
that
we
switch
lower
impact
ones
first,
learn
from
those
and
then
eventually
get
to
the
big
one.
A
Yep
agent,
with
both
stika
11
and
jdk
17..
A
Yep,
sorry,
sorry,
I
that's
okay,
I'm
taking
back
so
let's
get
started
on
what
we
did
a
lot
of
issues,
great
jobs
this
week.
A
So
let's
start
one
by
one,
so
we
add
a
request,
I'm
taking
them
on
the
order
of
the
nodes,
so
update
analysis
model
and
warning
ng,
plugins
and
ci
jenkins,
so
that
request
has
been
requested
by
alex.
Not
my
fault,
that's
something!
I'm
the
origin
of
the
reason
is
that
ci
jenkins
io
right
now
is
not
a
manager's
code
for
the
plugin
port.
A
I
was
sure
I
started
writing
something,
but
I
wasn't
able
to
find
so.
There
is
an
issue
to
be
written
to
get
started
on
putting
ci.jenkins.io
docker
image
with
its
plugins,
so
that
would
mean
building
an
image
for
the
ci
jenkins
io.
The
same
way
we
do
for
infra
ci
release,
ci,
that's
a
probability
made
with
an
exhaustive
list
of
the
plugin
with
the
exhaustive
and
spinned
versions,
and
then
we
have
a
process
to
update
them.
A
How
could
we
improve
the
the
security
process,
so
they
can
pre-stage
and
test
the
image
prior
to
delivery,
and
how
do
we
fix
the
drifts
that
inevitably
happen
when
a
security
board
is
applied
to
ci
jenkins
io,
because
if
we
upgrade
to
a
version,
an
updated
version
of
the
core
or
a
plugin,
we
need
to
build
an
image
before
these
plugins
or
core
is
available
publicly.
That's
the
concept
of
staging.
A
A
So
time
is
the
essence
there
and
then
once
we
have
an
image
that
has
been
installed
on
a
private
registry
and
tested
outside
our
usual
public
configuration
system.
We
need
a
way
to
correct
that
drift.
To
say,
oh,
I
see
that
that
image
is
not
what
you
you
would
expect
by
looking
at
the
infras
code,
which
is
public,
so
we
need,
let's
say
an
update,
clear,
whatever
automatic
process
that
say.
A
Oh,
we
see
that
there
has
been
an
security
process
automatically
open
a
pull
request
for
us,
so
we
have
put
disabled
during
that
amount
of
time
and
of
the
security
process.
I
don't
want
to
burden
the
security
team
with
the
drift
configuration
and
then
the
time
between
they
finish.
They
say:
okay,
ci
is
updated
with
the
image,
then
we
need
a
way
to
correct
the
drift
and
go
back
to
usual
process.
A
That's
the
main
challenge
on
that
issue.
The
advantage
of
doing
so
is
that
we
could
stage
the
image
test,
the
image
prior
to
deploying
to
ci
junk
in
cio,
and
we
could
be.
We
could
then
automate
plugin,
updates
and
audits,
plugin
updates
on
ci
jenkins
io
and,
moreover,
we
can
provide
easier
rollback
if
needed.
B
So,
just
to
be
sure,
I've
understood,
so
the
concept
then
is
switch
from
the
current
current
way
of
managing
ci.jenkins.io
as
a
as
an
operating
system
installed
package
and
switch
to
use
a
docker
image.
But
then
we
have
some
way
to
stage
those
docker
image
updates
privately
before
we're
ready
to
publish
them
publicly
and
on
public
public
publishing.
A
Exactly
okay,
except
the
only
it's
already
a
docker
image.
Oh.
B
A
So
right
now
I've
asked
alex
to
open
issues,
so
we
can
at
least
trace
the
changes
they
want.
They
want
to
do
because
he
wanted
us
to
update
some
plugin
on
specific
version,
so
they
took
care
of
that.
The
goal
is
to
have
issues
like
this
one
until
we
are
able
to
fully
use
a
configured
code
with
automated
or
auditable
content.
A
A
So
usual
we
had
to
prove
the
that
the
person
saying
hey.
I
want
that
account
to
be
removed.
We
have
to
to
be
sure
that
it
was
the
right
person,
so
we
have
to
prove
that
they
were
able
to
control
both
the
github
account
and
the
jenkins
account
before
removing
it,
but
they
went
fine
remote
access
api
on
a
very
non-cigio
instance
harvey.
Do
you
want
to
explain
it
or
do
you
want
me
to
to
summarize.
C
C
We
discovered-
and
we
I
discovered,
the
remote
accessory
path-
are
disabled
on
ci
dot
jenkins
at
io,
but
also
on
other
vehicle
stores
managed
by
puppet.
So
we
when
danielle
noticed
it.
He
asked
us
to
unblock
his
remote
accessory
on
the
previous
instance.
Like
that,
let's
say
I
touch
jenkins.
I
am
interested
so
I
made
those
first
configurable.
C
A
Thanks
for
the
explanation,
so
great
job,
that
was
a
lot
of
puppets
and
you
delivered
until
production,
with
no
outage
on
ci
jenkins.
I
also
congrats
releases
as
informative
notes,
so
here
it's
it's
an
automated
way
to
generate
the
notes
for
this
meeting
that
create
releases
really
useful
that
avoid
running
a
script
locally.
So
thanks
for
that,
that
helps
us
to
prepare
the
meetings
docker
compose
in
jenkins
ciao.
A
A
So
it
was
only
a
matter
of
using
the
correct
label,
but
also
the
thing
is
we
had
issues
because
it
accidentally
was
using
irm
machines,
so
we
had
to
fix
the
labels
of
the
rm
templates
because
a
docker
iran
container,
when
you
specify
an
intel,
an
intel
image
and
you
are
an
iran
docker
engine.
It
doesn't
work
as
expected,
so
the
label
has
been
fixed
and
seared
in
quincy
and
the
user
confirm
it
was
working
correctly
on
their
own.
B
C
B
A
The
the
thing
is
that
the
constraint
is
on
the
pipeline
library,
so
the
pipeline
library
drives
what
are
the
labels
used?
So
we
have
to
update
both
the
label
collection
and
the
documentation
and
the
pipeline
library
at
the
same
time.
So
there
is
some
clearly
some
improvements,
because
yes,
linux
for
me,
should
not
specify
an
architecture,
so
it
behaved
as
I
talked
it
would
behave.
However,
I
didn't
know
that
the
build
plug-in
library
was
using
linux
while
it
should
use
linux
and
imd64
by
default.
B
B
A
Thanks
for
the
question
we
added
kevin
to
the
jenkins
I
tried
team,
like
we
did
for
john
mark
and
christine
weston
recently
for
other
repositories,
but
in
that
case
that
will
help
kevin
to
contribute
and
continue
working
on
the
documentation
sig.
A
So
thanks
for
the
people
who
did
that
one,
we
had
a
failure
on
the
weekly
last
week,
which
was
a
consequence
of
the
kubernetes
upgrade.
So
thanks
for
the
tour
with
a
help
of
stefan
and
rv,
we
were
able
to
fix
that.
That
was
the
same
issue
as
we
had,
but
we
totally
forgot
that
there
is
a
persistent
volume
based
on
azure
file,
which
is
mounted
on
the
pod
used
to
package
and
deploy
the
weekly
release
under
core
releases.
A
A
Removing
groovy
tool
configuration
from
cert
ci
that
was
a
request
from
the
security
team.
They
want
to
remove
the
plugin,
so
we
had
to
remove
the
configure
the
tool
configuration
from
the
gcask
so
done.
Plugin
removed
and
removed
from
puppets
so
sounds
good.
C
A
A
Okay,
that's
the
word:
decommissioning
things.
Okay,
so
tim
and
danielle
took
care
of
that
contributor.
The
goal
was
to
decommission
a
plugin
502
proxier
when
accessing
polyquest
view
for
jenkins
ci,
so
that
one
is
solved
so
that
was
a
tricky
one.
The
root
cause
was
a
plugin
about
the
code
coverage
that
was
taking
that
was
either
looking
or
taking.
Sometimes
it
has
been
fixed
thanks
to
uli's
work.
So
many
thanks
for
everyone
involved
on
that.
A
I
have
no
idea
how
to
troubleshoot
such
error.
I
know
that
we
can
take
a
fret
dump
like
daniel
did.
There
is
a
page
on
somewhere
on
jenkins,
where
you
can
see
the
thread
dump
when
doing
such
elements.
A
But,
honestly,
when
I
read
the
thread
dump
I
mean
that's
yeah,
okay,
I
have
a
fret
dump,
I'm
happy
with
that,
so
that
one
is
that's
why
I
say
it's
tricky
us
jenkins
admin.
I
don't
think
we
have
the
knowledge
required
to
understand
this.
One,
so
what
that
means
is
that
when
there
is
a
word,
behavior
don't
stay
to
ask
the
others,
because,
as
soon
as
we
can
raise
such
issue
to
people
who
knows
like
daniel
and
uli,
then
they
could
start
acting.
A
That's
what
lee
expressed
saying
if
someone
will
report
such
problems,
so
I
think
there
is
a
room
for
improvement
there,
but
I
need
to
know
that
I
personally
I'm
a
long
time
around
jenkins
user,
but
knowing
that
it's
like
magica
for
me
like
how
could
I
know
so,
I
don't
know
how
we
could
improve
any
ideas.
Welcome
there,
because
I
feel
the
julius
frustration.
A
I
mean
having
an
issue
telling
him
hey.
There
is
an
issue
with
the
plugin
help
him
as
a
plugin
developer,
but
the
road
until
being
saying:
oh
yeah,
it's
a
problem
with
that
plugin.
For
me,
it's
like
magic.
So
thanks
for
daniel
help,
but
yeah
that
means
don't
hesitate
to
ask
for
help.
When
you
see
word
behavior
on
jenkins,
that's
take
away
from
me.
I
don't
know
if
you
share
it.
B
Is
this
one
where,
in
a
in
a
future
day,
we
might
be
able
to
use
historical
traces
to
something
that's
doing,
observability,
to
associate
a
plug-in
upgrade
with
a
slowdown
in
in
some
operations?
I
mean
right
now.
We
certainly
cannot,
but
I'm
I'm
wondering
if,
if
this
is
a
place,
where
think
about
the
the
trace
trace
facility
that
the
open
telemetry
plug-in
provides,
could
could
it
be
somehow
correlated
to
a
plug-in,
upgrade
and
tell
us?
Oh,
we
upgraded
this
plug-in
at
that
point
and
that's
where
the
traces
got
slower.
C
A
A
So
every
you
close
the
issue
about
powershell
and
pwsh.
So
as
you
express
as
you
expressed,
it
has
been
done
for
the
virtual
machine
built
on
packer,
which
is
our
final
goal.
So
it's
done
it's
hard
to
do
it
inside
the
windows
container
and
it's
really
time
consuming.
So
we
didn't
implemented
the
windows
part
because
we
don't
have
the
issue
now
we
under
the
issue
with
the
the
developers
that
had
the
the
problem
and
that
led
to
an
update
on
the
pipeline
powershell
documentation.
A
So
thanks
survey
for
that
that
will
help
a
lot
of
users,
because
I'm
sure
we
are
not
the
only
one
being
beaten
by
the
fact
that
jenkins
pipeline
engine
has
two
different
instructions
for
powershell,
depending
on
the
powershell
core
version,
so
by
adding
something
on
the
documentation.
That's
the
real
outcome
of
that
issue,
because
on
the
infrared
we
don't
have
the
issue
anymore,
I
mean
we
can
change
the
pipeline
library.
We
know
it,
but
letting
the
rest
of
the
users
know
that
outside
our
bubble
is
really
really
valuable.
A
A
So
sometimes
it's
okay
for
a
plugin
that
doesn't
have
frequent
merges,
but
on
the
jenkins
core
or
ath
or
bomb.
As
soon
as
you
update
something
on
the
bomb
branch,
each
pull
request
is
rebuilt
immediately
because
the
goal
of
auto
pull
request
is
to
build
the
virtual
result
of
what
will
it
be
if
it
was
merged,
meaning
the
git
commit
merge
of
the
head
of
the
destination
branch
was
the
source,
that's
the
default
behavior
of
all
ci
of
the
world
and
in
jenkins.
There
is
by
default
that
behavior.
A
That
say
if
either
the
source,
so
if
you
push
code
on
your
branch
is
change,
it
trigger
a
new
build,
make
sense.
If
the
destination
change.
You
have
to
be
sure
that
but
merging
your
change
is
still
valid
and
striking
that.
But
the
thing
is
that
for
the
bomb
or
eth
it
doesn't
make
a
lot
of
sense
and
it
cost
us
a
lot
of
wasted
cycles.
A
So
it
has
been
disabled
on
one
of
our
jobs
that
has
that
was
done
by
team.
I
think
manually
inside
the
ci
jenkins
io,
so
another
room
for
improvement
being
able
to
put
all
ci
gen
inside
your
job
config
under
job
dsl
management
will
clearly
help
in
these
situations,
because
we
could
audit
what
has
happened
and
we
could
remove
the
plug-in
job
configure
story
and
that
one
would
be
a
great
win.
A
A
First,
one
download
latest
latest
directory
out
of
date.
We
have
to
work
on
the
update
center
scripts
that
are
run
regularly.
There
is
a
script
on
the
pkg
update
center
machine,
which
every
hour
send
the
latest
plug-in
car
packages,
json
changes
and
send
them
to
the
mirror
reference
in
kubernetes,
which
is
the
mirror
system,
and
then
all
the
mirrors
can
start
delivering
these
appliances.
A
The
thing
is
that
the
tool
we
are
using
is
not
airsync
and
it's
not
a
linux
system.
It's
a
azure
file
bucket,
which
doesn't
support
natively
symbolic
links,
and
the
thing
is
that
we
construct
the
latest
path
on
update
jenkins
center
or
core
stable
latest.
It's
a
sim
link
to
the
latest
version,
but
when
you
send
that
in
a
system
that
doesn't
support,
the
sim
link
is
undirected
and
it's
a
directory.
A
So
since
we
do
not
override
the
changes,
we
just
add
the
new
changes
once
the
folder
latest
has
been
created
at
the
moment
of
time,
it's
never
overridden.
So
we
need
to
update
that
logic.
To
say,
we
need
a
specific
things
that
will
take
the
latest
of
each
change,
plugin
and
core
and
update
the
directory
and
update
the
new
directory
on
the
remote
system.
A
A
I'm
not
sure
I
will
need
help
from
team
olivier
or
daniel
on
that
area,
because
I
need
them
to
to
tell
me
why
I
didn't
avoid
that
because
it
explicitly
avoided
and
I
might
need
help
from
them
that
might
be
postponed
to
after
stefan
finish
update
center,
because
we
might
be
beaten
by
this,
but
right
after
c.I
jenkins,
io
agent
are
very
flaky.
A
We
had
issues
with
a
container
or
instances
on
kubernetes
all
the
spot.
Instances
on
the
region
were
consumed
on
aws,
leading
to
whatever
uses
a
spot
instance
kubernetes,
not
an
aks
or
virtual
machine
spawned
by
jenkins.
This
machine
were
reclaimed
or
not
started,
leading
to
a
high
rate
of
build
failures.
A
A
A
A
For
me
that
instant
is
closable.
I
will
take
care
of
that
after
removable,
lambda
bells
build
status
plugin,
so
almost
there
rv
that
trigger
a
new
issue
discussion.
What
should
we
use
to
replace
so
the
status
right
now
is.
We
are
experimenting
quickly
if
we
can
have
our
own
instance
of
shields
dot
io
that
provide
these
badges
in
the
same
machine
as
ci
jenkins
iu.
That's
the
scenario
for
now,
because
then
we
don't
need
to
put
any
token
or,
and
we
can
keep
api
or
remote
api
disabled
on
cigo
to
avoid
script
kiddies.
A
B
B
If
we
don't
receive
an
adoption
request
in
the
next
two
weeks,
it
will
be
suspended
because
it
includes
a
proprietary
component,
so
the
the
catalyst
event
was
hey.
This
plug-in
has
a
component
that
does
not
comply
with
jenkins
license
requirements
and
because
of
that
non-compliance,
it
started
this.
Shall
we
remove
it,
and
I
suspect
I
may
ultimately
be
the
one
who
adopts
it
actually,
because
there
are
cases
where
I
need
it.
B
C
Instance,
publicly
accessible,
you
don't
need
any
plugin.
You
can
already
use
the
public
instance
of
shield
data,
but
maybe
there
are
probably
private
one.
B
A
C
Yeah
I
was
seeing
for
a
little
bit,
but
it
was
a
great
way
to
discover
a
lot
of
things.
A
No
problem
enable
development
integration
in
jira.
I
failed
to
make
this
one
go
forward.
I
need
to
ping
the
right
person
on
that
area,
evaluate
retry
condition.
There
is
one
last
plugin
to
be
released
before
we
close
it.
It's
the
kubernetes
plugin,
so
please
don't
upgrade
the
kubernetes
plugin
on
ci
jenkins
iu.
Until
this
issue
is
closed,
jc
is
doing
your
last
minute
fixes
and
we
are
running
a
incremental
version
on
ci
quincy,
which
is
not
the
latest.
A
B
At
this
point,
I
don't
think
so,
because
I
think
the
best
thing
is
for
me
to
document
it
in
the
run
book,
how
to
do
it
and
then
later
we
add
a
new
ticket
that
says:
okay,
now,
let's
make
it
smarter,
the
the
the
agent
is
running
well
for
me.
In
my
private
instance,
it
runs
great.
It's
just
a
matter.
I
haven't
done.
The
configuration
work
for
the
public
instance.
A
Would
you
mind
sharing
an
access
to
that
machine
with
us?
The
goal
for
us
won't
be
to
take
over
but
to
test.
If
we
can
start
a
puppet
agent,
because
we
have
played
a
run
during
the
past
10
days
with
puppets,
and
that
could
be
interesting
to
know
if
we
can
install
it
even
without
the
official
package
like
we
do.
For
iran,
for
instance,
yeah.
A
C
B
A
A
B
A
You
sold,
I
get
some
wine,
so
if
it's
okay
so
correct
me,
if
I'm
wrong
but
the
status
is
you
are
working
on
doing
the
puppet
part.
So
you
started
working
on
creating
a
role
for
that
machine.
That
machine
as
puppet
agent
is
connected
to
the
puppet
master,
which
means
on
oracle.
Everything
is
started
network
cloud
resources
managed
by
terraform,
and
so
now
the
next
step
is
being
able
to
install
the
same
role
as
the
update
center
machine
and
to
manage
the
volume.
A
A
While
on
oracle
you
need
a
system,
a
root
volume
which
is
40
gigabyte
and
a
data
volume
which
is
clearly
better
because
we
can
trash
the
virtual
machine
and
start
a
new
one
provision
it.
We
still
have
the
real
data,
the
persistent
data
and
the
volume,
but
we
need
to
be
able
to
mount
that
volume
correctly.
A
So
we
have
lvm
things
that
might
or
might
not
be
useful
on
puppets.
So
that's
a
problem
that
stefan
is
working
on
so
congratulation
on
that
one,
because
yeah
oracle
cloud
wasn't
the
easiest
one.
A
A
A
We
created
some
kind
of
name
species
name
compartment
and
right
now
the
existing
machines
are
outside
this
compartment.
They
are
at
the
root,
so
we
will
have
to
move
some
resources
there.
That
might
have
some
outages
so
for
archives.
We
will
manage
it
on
the
other
topic,
but
here
for
your
machine
that
might
have
some
consequences.
B
A
To
see
the
import,
if
you
can
do
that,
while
I'm
around
yep,
so
is
there
any
objection
to
move
all
the
issues
of
the
current
milestone
to
the
next
one?
A
Okay,
just
a
look
at
the
new
elements,
so
first
I
missed
infrared
team.
Think
next
from
the
notes
right
now,
I
don't
see
any
emergency
new
issues.
I
have
some
to
write
that
I
will
mention
out
loud
there,
but
today
was
too
slow
to
fulfill
that
tomorrow
I
will.
I
will
have
some
times
with
olivier
about
the
data
dog
management.
A
A
I
need
the
help
of
olivier.
So
the
goal
of
that
issue
that
will
be
written
for
that
milestone
will
be
the
takeaway
of
the
discussion
with
olivier.
So
you
have
actionable
on
your
own
and
the
goal
is.
I
should
not
be
the
person
doing
that,
ideally
versus
the
constraint
we
will
have,
because
some
of
you
will
be
off
on
the
upcoming
days.
A
This
jobs
as
code,
do
you
have
new
issues
that
we
should
look
on?
The
upcoming
milestone.
A
One
two:
three:
okay:
I
just
need
help
from
all
of
you
folks,
including
mark
about
how
to
evaluate
alex's
request
about
javadoc.
So
there
is
an
issue
broken
taglib
docs,
I'm
not
sure
who
we
should
contact
to
diagnose
that,
because
I
have
no
idea
how
the
javadoc
works.
I
assume
it's
a
set
of
files
that
we
serve
on
a
static
web
server.
I'm
not
sure
there
is
anything
we
can
do
except
saying.
B
So
jesse
glick
jessica
knows
details
of
this.
I've
done
some
detailed
work
on
it.
If
you
want
to
just
assign
this
one
to
to
me
for
now,
I
don't
I
don't.
I
think
this
is
a
low
priority
thing,
the
it's,
I'm
glad
that
it's
been
reported,
but
the
transition
from
java
8
to
java
11
and
again
a
transition
from
11
to
17
tends
to
cause
breakages
in
this
area,
because
the
java
java.jenkins.io
site
is
somewhat
of
a
special
case.
B
It
started
originally
as
a
single,
a
single
javadoc
site
for
jenkins
core.
We
extended
it
to
allow
it
to
also
be
a
javadoc
site
for
all
plugins
and
for
jenkins
components,
but
in
order
to
do
that,
we
had
to
do
some
link
trickery,
some
link
magic
in
in
its
interactions.
So
so
there
are
some
complications
hiding
here
and
I
think
it
is
managed
as
code,
but
it
will
need
need
some
research
to
go,
find
it.
B
A
B
Yeah,
I'm
I'm
not
I'm
not
I'm
not
entirely
persuaded.
We
want
this,
so
I
I'll
want
some
discussion
on
this
one
before
we
say
yes,
we
should
do
it
just
because
I
don't.
I
don't
know
that
I
want
people
to
to
well
yeah,
let's,
let's,
let's
bring
some
discussion
to
this
room
before
ever,
consider
putting
it
into
our
backlog.
B
I
think
I
think
that's
that's
a
yeah.
It's
worth
a
discussion
on
the
mailing
list,
because
that's
probably
a
place
where
people
could
the
developer
list
could
tell
us:
do
they
actually
need
access
to
javadoc
for
lts
versions?
Is
there
enough
difference
between
lts
and
weekly
for
them
to
care
about
having
published
javadoc
for
for
lts
versions.
A
C
B
A
Were
there
other
new
issues
or
things
for
you
done
for?
Okay,
just
one
mention
that
thanks
and
stephan
for
the
huge
work
you
did
on
puppets,
because
I
did
some
unplanned
work,
which
is
a
foundational
work
to
keep
puppet
framework
updated
and
cleaned
up.
So
we
can
operate
efficiently.
A
The
fact
that
we
were
able
to
deliver
a
multiple
element
in
production
during
the
two
past
days
is
a
proof
that
we
are
growing
on
that
area.
The
fact
that
stefan
has
started
autonomously
on
the
pupat
means
that
we
are
clearly
improving
compared
to
what
we
had
olivia
and
I
one
year
ago.
So
thanks
for
your
feedbacks,
keep
giving
me
feedbacks.
You
are
not
annoying
b,
even
if
I'm
grumpy
that's
really
foundational
work,
and
during
the
weekend
I
was
ill.
A
So
I
had
some
time
to
kill
and
I
was
able
to
upgrade
all
the
games
to
the
latest
version
except
puppets
to
the
same
version
as
production.
So
it's
like
four
years
of
dependencies
jump
and
I
was
able
to
make
it
work
on
the
unit
tests.
We
will
have
to
do
it
on
production
now.
That
would
be
the
next
step.
I
don't
want
to
hear
that
french
people
are
lazy
when
I
hear
a
french
guy
walking
during
his
illness
to
do
that
kind
of
thing.
A
So
it's
all
for
me
folks,
many
many
thanks
for
your
work
and
you
help
keep
keep
that
pace
for
everyone
going
to
long
weekends.
I
hope
you
will
you
won't
do
the
same
as
me.
I
hope
you
won't
be
healed
and
take
care
of
you
is
there
anything
else
you
want
to
share
works,
take
care
of
the
weather
too,
because
it
will
be
very
hot.