►
From YouTube: 2023 09 05 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
A
A
2.422
is
out
War
packages
and
Docker
image,
Mark
Kevin
I
believe
you
are,
if
not
already
done
on
the
change
log
of
that
release,
and
the
last
items
is
that
correct.
A
A
C
Yeah
sorry
I'm
I'm
a
bit
I'm
a
bit
of
a
loss
of
person
open
source
as
a
whole,
but
yeah
but
I
feel
like
I,
could
give
some
guy
a
great
contribution
to
shenkins
as
well.
I
mean
I
used
to
work
with
Jenga
in
the
past
and
yeah
I'm.
Pretty
much
grateful
for
what
has
caused
me
to
well
earn
a
salary
anyway.
A
Cool
so
I've
shared
I'm
I'm,
adding
back
the
link
because
I
don't
see.
We
have
collaborative
notes
for
that
meeting
that
you
can
follow,
at
least
on
the
read-only.
A
Oh,
the
note
have
been
added
on
the
IRC
channel,
it's
arcmd
link,
so
that
gave
us
the
same
structure
every
week
when
we
run
the
meeting.
So
if
it's
okay
for
you,
we
will
proceed
on
the
usual
step
of
the
meeting.
So
you
can
see
how
we
tend
to
proceed
and
then
we
will
take
some
time
at
the
end.
If
you
have
question,
if
you
want
to
discuss
some
elements
that
are
unclear
and
if
you
have
a
point
you
want
to
to
contribute
to,
is
that?
Okay,
for
you.
A
A
A
A
Thanks,
do
we
have
a
security
advisory
I
believe
one
has
been.
A
A
A
A
A
The
first
one
is
remove
IP
restriction
on
Bounce
or
migrates
to
VPN.
So
it's
finished
so
since
30
minutes.
If
you
need
to
reach
trusted
cigo,
you
absolutely
need
the
SSH
bounce
Gateway,
but
you
also
need
your
VPN
access
to
be
enabled
and
connected,
and
you
need
the
user
account
on
the
VPN,
which
is
allowed
to
root
trusted.
Ci
virtual
Network,
so
I
believe
Stefan,
I,
Airway,
a
team
and
Alex
have
that
access
because
they
are
known
to
be
there.
A
A
No
problem
now
we
only
have
one
VPN,
so
that
should
be
easier.
Just
a
note
that
required
peering
networks
between
each
other
and
the
naming
that
was
used
for
the
original
virtual
network
was
creating
issues
and
overlapping.
A
So
earlier
today,
this
morning
in
the
in
Europe,
I
had
to
destroy
the
free
trusted
virtual
machines
and
recreate
brand
new
on
the
new
virtual
Network.
So
that
means
our
confidence
and
ability
to
restore
this
critical
part
of
the
infrastructure
is
good.
We
can
do
it
in
less
than
24
hours
without
losing
any
data.
It's
just
that
it
kept
the
update,
Center
index
to
be
updated
during
two
hours.
That's,
that
was
the
external
impact.
A
I
haven't
seen
any
other
problem.
I
reported
what
I
saw
during
the
bootstrap
minor
issues,
but
at
least
it's
written.
If
someone
has
to
do
it
in
emergency
in
the
upcoming
months,
is
there
any
question
things
unclear
about
that
task?
How
can
we
proceed
to
the
next
one
foreign,
okay,
next,
one
Stefan
virtual
machine
improve
command,
prompts
to
avoid
confusion
between
services
and
controller.
Can
you
just
give
us
a
report
of
what
you
did
and
what
is
the
result
of
that
closed
issue.
D
I
did
not
match
I
extends
in
the
in
the
pupet.
The
way
we
provide
the
prompt,
and
now
we
have
the
the
variable
and
the
colors
directly
within
the
prompt.
Of
course,
what
I
the
the
screenshot
I
did
was
before
the
merge
and
it's
from
background.
So
we
can
see
on
the
localhost,
but
we
should
see
now
that
it's
merged
I
haven't
checked
since
it's
merged,
but
we
should
see
the
the
correct
name,
the
full
name
of
the
controller.
A
Exactly
the
goal
was
to
avoid
confusion
when
some
operational
members
are
on
one
of
the
free
virtual
Machines
of
the
free
controllers,
just
to
be
sure
you
don't
run
a
command
expecting
to
run
in
a
trusted
CI.
While
you
are
running
it
on
CI.
These
are
not
the
same
instances.
I.
A
Okay,
it's
nice
to
have
so
you
can
comment
back
on
the
issue
later,
but
the
most
important
part
is
there
what
has
been
requested
by
the
Jenkins
security
team?
Now
they
have
the
fully
qualified
domain
name
inside
the
prompt.
So
now
the
color,
you
have
to
decide
the
color
with
Daniel,
yes
deciding
color
is
always
the
most
difficult
for
rest
is
implemented.
A
Thanks
for
the
work
Stephen,
still
your
turn
ath
Bill
commonly
become
in
responsive.
That
was
an
old
issue
and
there
were
one
last
step
we
wanted
to
run
the
first
try
on
building
an
ath
step
on
a
spot
virtual
machine
instance,
because
it's
really
cheap
10
times
cheaper
than
the
usual
instance,
and
we
want
we
wanted
to
implement
something
if,
if
we
have
to
retry,
because
the
spot
instance
is
reclaimed
by
the
cloud
provider,
we
want
the
second
run
to
execute
an
on-demand
instance
to
ensure
that
developers
still
comes
to
a
result
on
the
ends.
A
D
A
So
we
should
start
to
see
results
when
I
will
do
the
weekly
billing
reports
on
Azure
clouds,
so
in
one
or
two
day,
I
will
report
there
next
week.
On
that
result,
we
should
see
the
result,
the
direct
result
of
that,
because
we
are
back
to
spot
instance
by
default.
With
this
any
question
think
then
clear
cool
thanks
for
the
job
here.
A
So
the
new
tentative
was
trying
to
use
a
new
account
with
a
different
set
of
parameters,
and
one
of
the
parameters
that
were
required
for
a
successful
renewal
has
been
set
manually
years
ago.
I
tracked
it
in
2017,
but
since
it
was
persisted,
the
renewal
always
views
the
same
configuration,
but
that
thing
was
done
manually
and
never
puts
inside
configuration
as
code
hiding
it
from
us.
So
thanks
to
that,
I
was
able
to
understand
that
issue.
A
I've
linked
the
the
nice
article
that
helped
me
to
understand
the
problem
and
then
it
was
fixed
and
did
the
pull
request
on
puppets.
So
now
that
one
shouldn't
be
a
problem
anymore,
so
the
certificates
has
been
renewed.
After
applying
my
fix,
I
didn't
renew
manually
I.
Let
the
system
do
it
and
it
worked
so
thanks
Mark.
C
I'm,
not
just
I'm
sure
I
mean
have
you
guys
ever
thought
of
a
way
to
monitor
the
SSL
expiration
before
I
think
everyone
has
thought
of
that
already
right.
B
A
A
So
I'm
that
need
to
be
checked
that
I
think
we
need
to
update
them
because
they
are
checking
if
the
yeah
I
remember
when
we
chat
cigen,
the
virtual
machine
down
data
dog
alert
us
that
the
certificate
is
not
up
to
date.
I
believe
it's
not
checking
30
days
before
when
you
were
like
Mark
is
doing
so.
That
could
be
a
nice
upgrade
to
the
existing
monitoring.
C
E
A
Cool,
so
that
means
we
should
come
with
a
new
issue
that
could
be
taken
if
you're
interested
soon
worst
case.
That
will
end
up
in
the
Oktoberfest.
But
if
you're
interested,
since
you
told
us
that
you
knew
a
bit
of
datadog,
you
should
be
able
to
start
checking
out
terraform
management
repository,
which
is
public.
A
Yes,
yep!
Absolutely
if
you
are
willing
to
write
an
issue
for
that,
that's
perfect
I
plan
to
write
it
after
the
meeting
and
point
it
to
you.
But
if
you
are
willing
to
to
open
one
yourself,
please
go
ahead.
That
will
be
a
great
help
for
us.
A
Okay,
thanks
for
this
one,
any
other
question
on
the
task:
nope
cool.
Next
one
delete
the
Legacy
VPN
related
resources,
so
we
used
to
have
formal
networks,
and
this
networks
were
only
available
through
a
VPN
instance
that
leave
that
vpn.jenkins.io
domain
name.
We
don't
need
this
network
because
we
have
migrated
the
last
remnants
two
weeks
ago,
so
we
remove
that
costly
virtual
machine.
Yes,
that
was
a
hate,
CPU
24
gigabyte
machine
just
for
running
a
single
VPN,
because
back
when
it
was
created,
that
was
the
only
way
to
have
more
than
two
network
interface.
A
A
Any
question
on
this
one:
okay,
plugin
build
pipeline
stopped
working
I
believe
that
was
so.
There
was
an
error
on
a
contributor,
CI,
building,
cig
and
kinsayo,
and
the
problem
was
located
on
the
settings
XML
that
we
use
for
Maven
that
we
use
to
capture
all
Maven
requests
to
retrieve
dependencies.
A
So
this
requests
are
sent
to
our
artifact
caching
proxy
system,
and
in
that
case,
that
was
where,
where
an
exotic,
Maven
Behavior
to
say
the
lists
when
you
define
plugin
repositories
instead
of
repository
in
order
to
download
the
may
even
plugins
instead
of
other
dependencies,
so
we
deploy
the
fix
that
so
I
provided
a
short-term
fix,
so
they
were
able
to
continue
working
on
the
Jenkins
plugin
and
then
as
infrastructure.
A
There
is
just
one
little
problem
with
this
one:
it
broke
the
integration
tests
of
the
maven
HPI
plugin,
thanks
Mark,
for
pointing
that
out.
During
a
banking
day
on
the
US
I
see
someone
was
behind
the
computer
Monday.
B
A
For
info,
we
close
this
okay,
we
will
keep
that
setting,
because
it's
the
only
way
for
us
to
not
depend
on
apache's
control
and
the
problem
that
has
been
caused
is
an
integration
test
setup,
so
that
one
should
be
easy
to
no,
no,
it
won't
be
easy,
but
it's
not
a
blocker.
It's
not
blocking
anything.
It's
just
something
to
to
resolve.
A
A
Any
question
can
I
move
on
okay
next,
one
migrate,
search,
CI,
Jenkins,
IO,
so
search
CI,
Joan
kinsayo,
which
is
a
private
controller
used
by
the
Jenkins
security
team
to
prepare
security
advisory
in
advance,
has
been
migrated
to
the
new
private
Network.
That's
the
reason
why
we
were
able
to
delete
Legacy
VPN.
A
The
virtual
machine
is
now
having
more
resources,
is
cheaper
and
is
using
more
profile
agent,
which
are
also
cheaper.
So
that
should
be
a
good
thing
for
everyone:
more
power,
less
money.
That's
perfect,
I
haven't
seen
any
issue
since
past
six
days
on
this
one,
the
Jenkins
security
team
user,
all
confirmed
they
can
reach
and
work
with
the
instance.
So
the
issue
has
been
disclosed.
A
Okay,
one
last
thing:
we
are
the
password
issue
that
was
closed
because
it
wasn't
related
to
an
account
so
now
ldap.
But
someone
didn't
gave
us
enough
information
and
it
looks
like
they
were
trying
to
use
their
own
Jenkins,
never
get
the
answer
from
the
reporter.
So
close,
there's
no
action
required.
A
A
A
Okay,
so
let's
cover
our
work
in
progress,
Milestone
thing,
I'm,
switching
to
the
open
issue,
I'm
taking
them
again
on
the
order
here
on
my
screen.
That
might
be
a
slightly
different
order
in
the
notes.
I.
Let
you
map
the
points
remove
remnant
of
the
Legacy
virtual
networks.
A
So
I
try
to
follow
everything
from
their
automated
support
answer.
You
know
it's
clippy,
but
for
Azure
Cloud,
which
is
really
good
assistant
by
the
way
way.
Better
than
Clippy
I
I've,
been
Amazed
by
the
links
to
documentation
are
very
precise,
with
good
indication,
so
that
was
really
useful,
but
on
the
end
it
it
kept.
Sending
me
the
HTTP
500
error
so
contacted
the
supports
and
it
looks
like
they
are
involving
their
backend
team.
A
They
see,
we
have
formal
resources
that
I
can
see
on
the
Azure
portal
or
the
API
that
are
linked
and
connected
to
that.
Network,
so
they
are
trying
to
either
surface
this
hidden
resources
on
the
UI,
so
we
can
delete
them
properly
or
remove
the
wall
thing
on
the
back
end,
and
we
can
forget
about
that
Network.
A
A
So
I
haven't
had
time
yet
to
report
the
result,
but
we
are
ready
for
this
week
to
remove
definitively
the
mirroring
of
the
Apache
Central
North
Factory.
The
plan
is
to
do
it
this
Thursday,
since
we
have
security
advisory
tomorrow.
A
So
from
infrastructure
point
of
view,
I
will
report
everything.
I
tried
jobs
in
cigo
job
in
trusted,
I,
don't
see
any
more
blockers
on
definitively
removing
Apache
Central.
That's
the
summary
I
need
to
write
details,
so
it
will
be
checked
one
last
time
before
Thursday,
but
unless
there
is
any
objection,
I
propose
we
proceed.
B
Do
we
need
do
we
in
terms
of
informing
people,
you'd
already
sent
the
email
to
the
developer
list?
That
seems
like
the
most
crucial
thing.
Do
we
need
a
blog
post
as
well
to
give
us
a
milestone
and
in
time?
And
if
so,
do
you
want
me
to
write
the
blog
post
since
you're
nearing
the
end
of
your
day?
Do
we
want
to
enlist
somebody
else?
B
Are
there
or
no
blog
posts?
What's
your
feeling.
A
A
We
need
to
decide
the
operation
time
Thursday.
The
operation
time
should
be
first,
an
artifactory
removing
two
of
the
16
mirrors,
the
repo
one
and
Maven
repo,
one
that
we
have,
and
second
an
operation
on
each
cluster
kubernetes
cluster
to
clean
up
the
ACP
caches,
just
to
avoid
some
warnings
about
repositories
and
changing
repository
paths.
B
And
now,
when
the
ACP
cache
is
cleaned,
will
that
cause
or
repopulated
of
the
cache?
So
that
we'll
see
an
initial
heavier
load
and
then
we'll
back
off,
because
we
will
stop,
we
will
have
cached
everything
again,
it
absolutely
okay,
great
all
right.
So
so
we
shouldn't
be
too
dismayed.
If
there
is
high
activity
in
next
week's
bandwidth
report,
but
the
following
week,
we
expect
no
no
more
requests
to
cut
the
copy
of
central
that
we're
no
longer
giving
it
no
longer
Distributing.
A
Absolutely-
and
there
is
no
easy
way
to
clean
to
keep
the
same
cash
because
Maven
keeps
an
internal
tracking
of
where
each
artifact
comes
from
and
that
one
is
encrypted
so
changing
it
means
decrypted
everything,
recursively,
changing
and
re-encrypting.
Technically,
it's
doable,
but
honestly
I
prefer
increasing
the
bandwidth
one
time
right.
B
A
A
B
I
assume
when
you,
when
you
said
that,
the
time
of
day
it's
probably
healthier
for
us
to
have
you
do
that
start
of
your
working
day,
so
that
if
there
are
surprises,
we
don't
don't
end
up
keeping
you
late,
it
doesn't
matter.
I
won't
be
any
help
resolving
things,
but
you
and
Daniel
are
both
good
candidates
to
help
resolve
things.
If
there's
another
really
an
artifactory
issue.
A
A
Cool,
so
almost
there,
if,
if
it's,
if
g-frog
is
happy
with
the
outcome
in
let's
say
two
or
three
weeks,
it
looks
like
we
will
be
able
to
close
that
topic
and
proceed
safely.
That
means
they
won't
kick
us
out
of
their
sponsored,
manage
instance
of
artifactory,
because
an
artifactory
of
that
size
is
not
a
pleasure
to
work
with,
especially
on
the
public
cloud.
A
E
E
So
we
don't
need
the
IP
and
DNS
records
for
this
instance,
but
it
can
be
useful
for
other
mirror.
We
can
this
dispatch
in
different
cloud
provider
like
digital
Oracle
or
else,
and
another
big
part
of
the
work
you've
done
is
to
upgrade
and
fix
here.
I
think
base
image.
We
are
using
for
this
service.
E
While
working
on
this,
you
also
noticed-
and
we
decide
to
split
the
mirror
with
shorts,
M
sharp-
we
we
were
using
in
three
parts
with
the
httpd
server
on
one
part,
see
I,
think
another
part
and
the
mirror
bits
alone
in
in
it
is,
and
I'm
I've
made
this
split
yesterday
and
I'm
working
today
on
creating
around
10
charts
to
get
this
free,
shata
subject.
E
E
Another
development,
as
we
didn't
received
any
response
from
cloudflare
and
as
it
seems
to
be
a
bit
difficult
to
contact
them
about
their
open
source
sponsorship
program.
E
We
might
not
be
able
to
use
cloudfare
yet
and
we
will
fall
back
on
digital
for
now.
I
think.
As
soon
as
we
are
putting
this
service
in
production.
E
A
E
E
But
this
direction
it's
also
going
well
for
our
relationship
with
them,
because
it's
they
asked
asked
us
to
try
their
data
service
I.
Don't
know
how
to
say
it
properly,
but
it's
it
can
be
a
good
good
would.
C
A
Absolutely
report
to
them
to
grow
and
nurture
the
relationship
yeah.
The
worst
case
is
that
will
cost
us
a
bit
less
than
100
of
books
in
the
worst
case
scenario
per
month,
which
mean
once
we
start
using
digital
lesson,
we
will
have
six
months
of
available
credits,
given
the
rate
we
have
today
with
the
current
usage
of
that
cloud.
A
Don't
forget
that
digitalocean
cluster
for
us,
where
we
should
deploy
that
mirror,
is
in
Frankfurt
Data
Center,
it's
in
Europe,
which
mean
we
also
have
to
think
about.
Can
we
have
a
us-based
mirror,
so
we
won't
change
the
latency
from
for
our
us
user.
Today
we
are
the
current
update.
Center
is
only
in
U.S
east
one.
So
that's
why
I
propose.
We
could
also
check
with
a
record
it's
not
mutually
exclusive.
A
With
ovh
the
more
mirrors
we
have
here,
the
more
distribution
and
spreading
of
the
cost
of
the
outbound
bandwidth
we
have
in
the
case
of
a
rocker.
We
don't
have
a
kubernetes
cluster,
so
when
we
might
need
a
bit
more
work
because
we
need
a
VM,
we
need
the
VM
and
a
bit
more
walk,
but
it
will
be
on
the
on
the
U.S,
Data
Center.
A
And
finally,
we
could
find
other
sponsor
hoping
that
cloudflare
answers,
but
right
now
yeah,
since
we
don't
have
any
option
from
cloudflare
which
provide
free,
outbound
bandwidth
and
they
provide
also
the
ability
to
create
buckets
inside
the
China
internal
Network.
We
could
have
covered
mirrors
on
different
areas
in
the
world,
so
I
propose
that
we
delayed
the
China
part
for
now
and
we
focus
on
migrating
away
from
AWS
to
Azure
for
the
radioactor
and
digital
Lucerne
as
the
primary
mirror.
A
A
It's
mandatory
that
at
least
two
weeks
before
the
effective
change
of
the
final
update
Center
to
the
new
system
after
testing
and
everything
that
we
publish
at
least
a
blog
post
and
communicates
because
that
means
we
will
change
the
public
ipus
for
which
the
update
Center
and
that
will
had
a
list
of
public
IP
where
the
user
will
be
redirected
to.
We
need
to
communicate
that
because
a
lot
of
Jenkins
users
are
behind
corporate
networks
where
they
tend
to
have
firewall
that
only
allow
some
internet
accesses.
A
A
Exactly
they
have
a
viable
information,
so
it's
just
a
note
that
we
will
need
blog
post
and
to
X
to
have
the
list
of
this
IP,
because
in
that
case
we
control
the
mirrors,
that's
the
core
of
that
new
system.
So
we
control
the
public
IP,
mostly.
A
Of
course,
some
of
this
public
IP
won't
be,
might
change,
for
instance,
a
cloudflare
public
IP,
but
in
that
case
each
company
will
have
to
select
the
mirror
that
works
for
them.
That
were
that
won't
allow
us
to
balance
through
the
HTTP
or
director
mirror
system,
but
at
least
they
will
have
a
backend
solution,
because
it's
not
for
us
to
control
that
kind
of
thing,
but
still
we
have
to
communicate
about
that
church.
A
A
D
A
Congratulations:
nice
working
is
now
served
with
a
ram
64
great
work
on
that.
One
which
means
for
the
upcoming
Milestone
I
only
have
one
request
for
you
about
that
issue
particularly,
is
now
to
take
a
list
and
exhaustive
lists
to
see
which
one
will
be
migrated
on
the
paper.
We
should
be
able
to
migrate
everything,
but
some
might
be
more
complicated
or
we
want
to
keep
an
Intel,
but
you
need
an
exhaustive
list,
so
we
can
know.
When
can
we
close
that
issue?
What
is
the
definition
of
done
is
that,
okay,
for
you,
Stephen.
D
A
Yes,
of
course
that's
there
is
an
exception.
The
Mato
modocer
image
does
not
need
to
be
on
that
issue,
because
it's
a
separated
issue
and
topic
to
track.
Once
matoma
is
deployed,
whether
it's
a
Ram
or
Intel,
then
we
can
close
the
topic.
So
it's
only
the
the
other
services
running
on
the
public
Gates
cluster
and
that's
a
scope
for
you
good
for
you
yeah.
A
A
D
I
just
started
so
I,
first
I
renamed
it
because
it's
matubo
and
and
I
did
some
cleanup.
Most
of
it
was
the
versioning.
It's
it's
still.
A
work
in
progress,
I
think
it's.
It
should
build
right
now
nicely
I
just
got
an
issue
about
the
docker
app
that
need
to
be
bootstrapped
for
that
name.
D
Matomo
I
did
also
another
pull
request
for
release
drafter
and
but
it's
done
and
right
now
I'm
preparing
Azure
to
be
able
to
have
the
MySQL
flexible
server
on
the
on
the
same
area
than
the
the
postgre
SQL,
one.
That's
not
area,
but
the
same
model,
template
and
I'm
working
on
that
right
now,.
A
Cool
thanks:
is
there
any
question
or
need
for
Clarity
on
this?
One
reminder:
the
goal
of
matumu
here
is
for
us
to
have
our
own
website
statistics
and
eventually
get
away
from
Google
analytics.
For
this
part,
we
will
have
our
own
hosting
system
based
on
matamu
Gavin,
who
initiated
the
matoma
process,
have
a
matter
more
instance
running
since
one
year
and
a
half
in
digital
lesson
with
Statistics
and
Jenkins
IO.
That
looks
good.
So
that's.
Why
deploying
this
one
we
can
start
to
have
our
own
Statin
then
decide
what
to
do.
A
Cool
thanks
for
the
work
and
Reporting
21
I
see
we
have
the
two
the
two
culprits
here
for
that
issue:
Don't
Run,
Away,
Bruno
and
Stefan.
What's
the
status
on
the
GD
cat
21
switch
to
the
EA
week,
I
think
it
believe
it's
weekly,
it's
built
weekly.
F
D
That's
completely
wrong,
yes,
I
I
did
in
fact
already
set
up
the
gdka
21,
but
not
on
that
specifically
available
version.
So
I
did
just
spend
time
to
explain
what
and
where
we
we
put
staff.
We
had
a
little
misunderstanding
of
of
what
was
really
the
the
aim
of
that
pull
request,
because
I
thought
that
we
would
just
change
the
the
version
and
in
fact
what
was
planned
was
to
used
it
as
if
it
was
the
the
definitive
one
and
to
have
only
the
version
in
only
one.
F
Are
it's
still
yeah
in
traffic
I'm
waiting
for
your
yeah
when
yours
will
be
merged,
we'll
be
switching
to
a
real
pull
request.
A
D
A
A
A
But
since
yesterday,
that
new
GDK
21
is
used
on
cigo
and
we
successfully
run
Jenkins
score,
builds
and
ath
runs
with
that
new
GDK
21ea.
So
that
means
we
bumped
off
two
weeks
compared
to
the
former
version.
Now
we
have
puppets
and
the
outcome
is
that
we
expect
the
date
CLI
to
track
an
open
pull
request
when
it
detects
the
new
version
of
the
gdka
21.
A
So
once
a
week-
and
that
means
then
we
can
let's
say,
propose
that
successful
update,
CLI
tracking
system
to
the
official
Jenkins
Docker
images
as
part
of
the
platform
Sig
initiative,
cool,
so
cool
thanks,
gentlemen
for
working
on
that
topic.
Is
there
any
question
you
need
for
clarity
for
that
topic?
A
Okay,
then
Mark
and
hi.
We
each
have
one
issue:
Linux
Foundation
status,
page
redirect
and
for
me
a
jira
administrator,
login,
page
setup.
I
believe
both
of
us
have
nothing
to
report
on
these
issues
because
we
didn't
work
on
it
at
all.
Is
that
correct?
That
is
correct,
so
these
two
issue
will
be
moved
like
the
others
on
the
next
Milestone.
Until
we
find
time
to
work
on
this.
A
C
C
A
It
yes,
it's
on
a
sign,
but
first
this
one
requires
administrator
access
to
jira,
which
only
a
few
people
have
and
the
less
people
we
have,
because
that
Shiro
instance
is
managed
by
the
Linux
foundation
for
us,
and
it
contains
a
lot
of
issue
tracker
and
some
are
private
and
rarely
highly
sensitive.
So
the
access
to
the
Geo
Administration
is
barely
closed.
Only
third
person
on
that
room
have
access
Mountain
High.
A
The
main
challenge
described
on
that
issue
is
that
we
use
our
internal
ldap
system
when
user
authenticate,
we
don't
use
GR
in
the
nodes,
and
we
cannot
use
the
jira
embedded
SSO,
because
jira
manage
instance
does
not
manage
SSO
system
with
so
much
users
as
what
we
have.
So
we
cannot
use
jira
cloud
license.
A
Does
it
make
sense
that
makes
sense
thanks
for
proposing
Albert
for
that
one?
That's
not
a
newbie
one
due
to
the
access
level
required
here
anyway.
If
you
know
how
to
change
that
on
the
usual
Jenkins
instance,
you
can
help
by
guiding
us
appointing
us
to
the
documentation
of
atlation
on
that
part,
but
I
I,
don't
think
your
your
brain
should
be
wasting
its
time
on
such
an
issue.
It's
a
low,
it's
let's
say
low
impact
issue.
A
A
C
A
Right
we
have
one
issue
that
must
be
treated
Stefan
on
the
next
milestone.
A
So
we
need
to
start
with
simple
services
that
only
have
two
replicas
and
we
ensure
that.
Then
it
leads
to
two
nodes
on
the
Note
pool
with
one
replica
on
each
and
then
we
will
iterate
to
the
one.
With
three
or
six
replicas,
so
that
Jenkins
orbits,
because
we
might
need
to
fine
tune
that
kind
to
avoid
having
too
much
nodes
which
are
empty.
A
We
might
have
to
reconsider
some
of
the
replica
amount
choices,
mainly
because
it
was
done
few
years
ago,
and
none
of
us
have
controlled
that
we
are
not
having
too
much
replica
and
we
have
a
bunch
of
metrics
in
data
doc
to
help
us
on
deciding.
So
we
will
have
to
look
at
the
consumption
and
see
if
maybe
we
can
decrease
the
amount
of
replicas
for
some
of
these
services.
D
Was
I
was
not
because
your
your
face
was
elected
on
that
issue,
so,
as
is
that
assigned
to
you,
I
was
like
okay,
it
says
his
team
is
okay,
but
if
you,
if
you
need
some
help,
I
can
I
can
rub
it
up
with
you.
Whenever
you
want
that's.
B
A
A
E
Requests
apparently
I
haven't
noticed
that
on
the
master
Branch
but
I've
proposed
a
fixed
by
removing
the
clean
Gradle
task
as
The
Cider
drinking
satayo
is
using
ephemeral
Legends.
So
there
is
no
need
for
cleaning
to
workspace
when
building
a
plugin
on
theater
jenkins.io
I
propose
a
pull
requests
on
the
plugin
I'm
waiting
for
Denise
feedback.
If
it's
an
acceptable
work
around
six
or
if
there
is
more
to
do
as
running
I'm
like
Tanya
I'm,
almost
know
nothing
about
other,
but
yeah.
B
E
A
Okay
is
that,
okay
for
that
topic
in
work
in
progress.
A
Okay,
so
I
believe
we
have
a
few
new
topics,
but
not
that
much
I
have
one
that
needs
an
issue
to
be
created
which
I
will
do
right.
After
this
meeting,
we
received
on
the
team
calendar
an
alert
that
in
two
weeks
the
VPN
serial
will
expire.
So
we
will
need
to
renew
the
crl
for
six
months,
like
we
do
every
six
months,
so
VPN
serial
to
renew
before
I
think
it's
the
20..
A
We
had
past
issues
to
process.
Anyone
here
can
do
the
process.
Anyone
here
with
administrative
right
on
Docker,
openvpn,
sorry
for
Kevin
Bruno
and
how
new
contributors
but
yeah
that's
an
easy
one.
It's
the
outcome
is
a
new
Doc,
a
pull
request
once
more
generate
a
new
Docker,
open,
VPN
image
that
we
have
to
deploy
in
puppets.
Update.
Cli
is
doing
most
of
the
EV
lifting
here
once
generated
and
also
created
a
calendar
alerts
in
six
months
for
the
next
expiration.
A
That's
the
most
difficult
part
of
that
task,
so
an
issue
will
be
created.
Anyone
interested
can
take
it.
Otherwise,
I
will
I
will
points
fingers
as
someone
randomly
and
they
will
be
designated
volunteer
to
take
it
in
two
weeks.
A
I
also
saw
and
I
need
help
from
people
knowledgeable
on
email,
but
I
add
a
notification.
It
looks
like
some
emails
again
are
filling
the
SPF,
as
per
team
commands,
so
I
will
I'm
adding
that
issue
on
the
upcoming
Milestone
and
I
will
need
help,
because
my
knowledge
on
email
and
SPF
and
stuff
is
close
to
zero,
even
negative.
F
A
That's
the
title
of
the
issue:
that's
all
okay,
I,
don't
know
what
the
problem
is.
If
it's
really
a
problem,
I,
don't
know
anything
on
that
area.
So
I
need
help
from
people
knowledgeable
here.
Okay
looks
like
you
are
self-designating
right,
Stefan,
yeah
I
will
add
the
issue
and
assign
anyone
can
take
its
I,
don't
mind.
A
We
have
Nexus
Jenkins,
plugin,
bundles
Preparatory
dependency.
That's
an
issue
opened
by
Danielle
as
a
top
level
issue.
No
action
expected
from
us,
but
just
for
so
that
you
know
the
goal
is
to
suspend
distribution
of
that
Jenkins
plugin
because
of
a
license
thing.
No
action
expected
from
us,
except
keeping
trusty.ci.jenkins.io
up
and
walking,
because
it's
required
to
update
a
bit
Center.
So
I
will
add
that
issue
on
the
Milestone.
But
no
one
need
to
be
on
that
one
I
believe
Morocco
have
been
pinged,
so
I
will
attribute
the
issue
to
you.
A
F
B
A
So
again,
no
action,
it's
more
for
information
and
that
issue
should
be
closed
once
the
plugin
Jenkins
are.
You
won't
serve
anymore,
the
problem,
the
the
problematic
plugin
so
I'm.
Looking
at
new
issue,
we
have
a
GitHub
permission,
but
that's
special.
It's
not
inside
the
infrastructure,
so
no
need
to
add
it
to
the
milestone
and
PKG
origin.
Jenkins
IO
is
waiting
for
the
work
on
updates
then
can
save,
which
means
the
last
big
one
is
kubernetes
1.26
upgrades,
because
digital
Lucerne
will
stop
supporting
1.25
in
October
2020
fresh.
A
A
So
I'm
starting
brainstorming
about
the
newbies
issue,
that's
a
good
opportunity
for
us
to
start
thinking
about
the
Oktoberfest.
A
We
will
need
to
think
about
easy
issues
which
can
be
challenging
on
the
infrastructure,
because
sometimes
the
required
accesses
and
the
fact
that
we
are,
we
might
not
always
have
the
time
to
Monitor
and
follow
the
person
who
propose
a
pull
request,
because
you
know
the
net
tickets,
as
the
French
says,
opening
a
pull
request
out
of
the
wall
on
a
given
open
source
project
can
be
really
costly
in
terms
of
time
context,
switching
for
the
maintainer
reviewer
and
contributors.
A
A
A
I
I
haven't
had
the
time
yet
to
think
about
that.
So
I
propose.
If
it's
okay
for
everyone
that,
if
you
see
anything
that
I,
could
take
on
the
issues
and
updates
dependency
somewhere,
we
can
start
writing
a
decision
on
the
Milestone,
so
how
you
could
start
get
working
on
one,
and
we
that
mean
we
need
to
give
him
clear
scope
on
what
is
expected
to
not
let
him
alone
yeah
Mark.
D
C
B
Okay,
Vietnamese,
that
all
the
same,
that's
great,
so
the
reason
the
reason
I
I
ask
is:
is
we've
got?
We've
got
a
documentation
site
for
Chinese
that
needs
to
be
retired.
Oh,
we
need
it
redirected
to
the
English
site,
and
so
there's
a
there's,
a
learn
about
the
infrastructure
to
figure
out.
How
is
how
is
the
current
thing
hosted?
B
B
A
You
might
need
guidance
at
least
some
entry
point
if
you
are
interested,
of
course,
to
the
let's
say
the
kubernetes
resources,
which
are
public
that
we
use
for
serving
the
website,
at
least
on
the
back
ends,
but
that
also
require
analysis
on
the
fast
clipboard,
because
I
don't
remember.
Very
fastly
is
caching.
The
Chinese
website
I
believe
not
because
fastly
is
not
projected
inside
the
China
Network,
but
that
need.
B
C
Uml
redirections
and
sprinkling
up
Chinese
here,
I
suppose.
B
B
A
Right
so
that's
a
proposal.
You
have
the
right
to
say
no,
it's
only.
B
F
Yep
and
Damon
cited
updates.
Eli
did
you
ever
try
update
July
hi.
C
Oh
yes,
in
the
past,
I
mean
I
have
to
agree.
I've
done
plenty
of
three
directions
of
my
old
companies
domain
to
21.,
so
that
that
that
would
qualify
me
as
well
right.
B
B
Well,
so
the
redirect
is
a
very
different
thing.
What
Bruno
was
changing
redirect
is,
it
sounds
like
you're
very
qualified
update.
Cli
is
a
tool
that
we
use
to
maintain
to
automate
the
updates
of
versions
that
are
specified
in
our
source
files,
for
instance,
node.js
releases,
a
new
version
and
our
configuration
is
code.
Definitions
need
to
be
updated
to
use
that
new
version,
okay
yeah,
so
so
this
is
what
update
CLI
is
and
I'm,
assuming
you
probably
haven't
seen
this
before,
because
it's
a
relatively
new
tool,
yep.
C
A
My
predecessor,
who
wrote
this
tool
and
now
is
working
at
Hughes
and
is
growing
the
usage
of
that
tool.
That
tool
has
been
adopted
since
then
by
as
kid
doctor
project
by
the
k3s
project
on
shoes
and
some
internals
use
project
as
well,
we're
using
it
because
we
run
the
update
process
compared
to
renovable
or
Dependable.
It's
not
a
cloud
or
an
external
system.
A
F
E
F
You
have
any
idea
of
what
could
be
updated
with
update
live,
which
hasn't
been
updated.
Yet
what
is
not
tracked?
Is
there
dependency
on
obvious
dependency
that
we
would
need
to
update
with
a
dhli
no.
A
You
already
fixed
all
the
obvious
one,
so
I
need
time
to
search
and
look,
but
that
means
the
world
team
need
to
search.
If
you
see
obvious
dependencies
that
are
not
tracked,
that
could
be
a
way
to
at
least
track
them
with
issues
and
propose
to
High
by
defaults
and
if
high
you're
not
interested
any
way.
That's
useful
because
we
could
label
these
issues
as
newbies
for
at
least
the
Oktoberfest.
D
And
we
need
to
be
careful,
because
sometimes
that
sends
easy
and
and
just
a
track
in
the
Manifest
and
at
the
end
it's
it's
just
a
nightmare
like
the
last
discussion,
where
the
I
forgot,
when
yesterday
two
days
ago
about
the
the
fact
that
we
need
the
same
version
of
a
tool
between
cin
and
try.
That
start
to
be
not
so
easy
and.
F
D
Do
you
have,
do
you
have
a
sorry,
Daniel,
yeah,
hey,
okay,
do
you
have
any
any
specific
competence,
I
mean,
do
you
know
terraform
or
do
you
know
Packer?
Do
you
know
what
kind
of
of
Technology
do
you
already
know
for
us
to
to
drive
you
in
in
a
way
that
you
already
knows
a
little
at
least.
D
C
B
Awesome
so
so
another
candidate
idea,
possibly
not
so
much
infrastructure
as
development,
but
needs
the
skills
that
Hyde
just
mentioned.
Add
Debian
12
support
to
oh
dear
I,
forget
which
one
it
is.
Is
it
the
agents?
Is
it
the?
Oh?
No
add
Debian
12
support
to
the
packaging
tests.
B
B
A
No
problem,
sorry,
so
on
my
side,
I
will
think
about
I.
Don't
have
some
immediate
I
have
some
in
the
back
of
my
mind,
but
I
want
to
check
them
to
see
what
will
be
required
for
you
to
get
started.
So
if
it's
okay,
I
will
come
back
with
issues
next
week
during
the
upcoming
team
meeting,
it's
not
mandatory
that
you
attend
every
week.
If
you
want,
you
are
welcome
it's
open
to
everyone,
as
we
said,
but
I
don't
want
you
to
feel
any
pressure.
A
If
you
start
a
subject
and
are
not
able
to
land
it,
that's
not
a
problem.
You
are
here
because
you
will-
and
you
want
to
spend
some
time
on
this,
but
there
is
no
criteria
of
oh
yeah.
We
will
trust
him
only
if
he
succeed.
No,
no
pressure
on
that
part.
You're
free!
It's
your
time.
You
do
whatever
you
whatever
you
want.
So
if
you
help
that's
really
cool
and
useful,
if
you
cannot
finish,
that's
not
a
problem.
You
will
have
learned
something
on
here
and
the
process
is
already
valuable
for
us.
A
A
C
A
Okay,
oh
that's
yeah,
so
we
use
the
tool
only
for
collaborative
notes,
but
then
these
nodes
are
publicated
in
GitHub,
Jenkins,
Central
documentation
and
on
the
community
Forum
at
community.jenkins
every
week,
so
that
link
will
disappear
in
a
few
days.
It's
only
a
temporary
tool
until
we
publish
the
notes.
Okay,.
A
So
is
that,
okay,
for
you,
you
take
the
time
you
need
to
watch
the
topic
and
you
can
get
started
on
the
one
that
interests
you
and
we
will
report
with
eventually
new
issues
next
week,
whether
you
are
there
or
not,
we
will
just
report.
If
you
choose
a
topic
and
then
we
will
also
continue
working
on
selecting
issues
with
the
October
first
in
mind.
A
C
Kevin
just
one
short
thing:
yes,.
C
I
mean
I
assume
that
I
would
need
some
Kaiser
if
I
want
to
work
on.
One
of
the
items
right
here,
bullet
pause
right
here.
I
would
need
to
to
ask
for
some
sort
of
access.
First
right
to
the
infrastructure,
not.
A
At
all,
you
don't
need
most
of
the
code
is
public
and
the
the
most
important
part
is
that
we
need
to
select
issue
that
you
can
reproduce
partially
or
totally,
and
then
you
can
once
you
have
started
the
discussion
and
I
want
to
solve
that
problem
and
I'm
going
on
that
direction.
You
can
then
proceed
on
opening
a
pull
request
if
it
looks
like
a
solution
and
we
most
of
the
time
we
have
CI
feedbacks
that
you
can
see
publicly
so
everything
being
public
you
can
get
started.
A
The
goal
is
not
having
to
create
accesses
to
any
kind
at
any
moment.
If
we
see
that,
for
whatever
reason
that
we
forgot,
we
discover
who
you
might
need,
then
we
will
discuss
this
all
together,
including
you,
but
right
now
you
don't
need
any
kind
of
access,
except
eventually
a
GitHub
account.
So
we
can
interact
inside
the
issues
where
you
will
propose
on
the
panpool
requests.
E
D
E
With
me
are
good
first
issue
too,
since
most
of
the
time
old
and
they
need
this
updates.
So
if
you
reading
a
readme
and
you
see
increments
or
problems
or
outdated
link,
don't
hesitate
to
edit
them.
It
would
be
great.
E
And
it
also
help
us
to
know
what
is
not
explained.
What
is
not
correctly
explained
for
newcomers
or
someone
discovering
it's
a
specific
Repository.