►
From YouTube: 2022 05 31 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
Call
to
cloud
okay,
everyone
welcome
to
the
weekly
jenkins
infrastructure
meeting.
We
are
the
31
of
may
2022..
Today
we
have
myself
naman
de
portal,
bruno
barton.
A
A
A
A
A
A
A
third
announcement
that
will
be,
we
already
have
an
issue
to
track
that,
but
that's
important.
The
certificate
of
the
update
center
expires
in
two
weeks
five
hours
ago,
the
jobs
in
charge
of
generating
the
json
started.
Failing
due
to
that
error,
while
the
crawler
failed
since
two
or
three
weeks,
so
stefan
and
I
we
started
on
the
renewal
of
that
certificate,
there
are
things
that
we
don't
understand
on
the
private
repository
hosting
that
so
the
readme
might
not
up
to
date.
So
we
need
help
from
danielle
or
olivier
to
understand.
A
What's
going
on,
the
core
of
the
issue
is
that
it
seems
that
since
last
year
there
are
two
certificates,
one
used
by
the
crawler
job
and
one
by
the
update
center
job
on
trusted.
Ci
there
are
two
zips:
the
update,
center
keys
and
associated
search
file
are
the
same,
but
the
full
certificates
associated
to
these
keys
seems
to
be
different
between
two
jobs.
We
are
not
sure
which
one
should
be
the
correct,
and
if
we
could
only
generate
one
so
we
will
need
help
today
or
yesterday,
because
it's
impacting
the
plug-in
release.
A
I
don't
know
tim
if
you
are
teased
with
that
part
or
not.
I
assume
I
assume
not,
but
maybe,
if
you
ever
tried,
the
readme
is
good,
as
stefan
can
confirm,
we
have
to
open
ssl
commands,
the
only
issue
is
be
sure
being
sure
which
certificate
is
which
which
key
is
which,
which
is
complicated.
A
No
I've
never
done
it
before.
I
think
only
olivier
k,
okay,
yeah
and
taylor,
but
yeah
thailand
didn't
touch
that
repository
since
2017..
A
C
A
A
A
A
A
It
seems
that
it's
not
required
and
mark
took
care
of
everything
that
was
missing,
but
still
since
vanson
is
also
the
main
one
of
the
main
mentors
of
the
kubernetes
plugin.
A
So
certificate
expired
for
pkg.jenkins.io,
it's
one
of
the
part
of
the
outage
that
I
mentioned
earlier
so
for
that
one,
the
enabling
puppets
last
friday
on
that
virtual
machine.
It
hasn't
been
run
since
two
years
and,
as
I
said,
it
broke
the
certificates,
so
there
has
been
a
quick
fix,
but
it
took
a
few
hours
to
get
to
this.
A
A
Okay,
so
the
domain
stories
jen
kinsey
has
been
verified.
There
were
an
issue
between
the
c
name
that
cannot.
You
cannot
have
a
cname
and
the
txt
report.
If
I
understand
correctly,
I
don't
know
which
method
I
gave
indeed
in
the
end-
and
I
confirmed
that
I
received
an
access
to
the
google
console,
I
can
give
access
who
there
is
interested
or
should
have
access,
raise
your
hand,
yep
team.
A
A
Update
center
plugin
in
stable,
so
stephan,
and
I
worked
on
that-
I
tried
to
work
always
with
someone
else
to
not
be
the
only
person
fixing
the
incident.
So
stefan
thanks
for
the
help
around
the
apache
configuration
we.
A
Head
scratches
about
how
the
heck
that
the
piece
of
software
is
working,
the
answer
is,
we
still
don't
know,
but
we
tried
to
guess-
and
we
guessed
right,
because
it
seems
that
the
machine
is,
we
don't
have
alerts
anymore.
So
not
only
we
fixed
the
issue,
but
we
improved
the
situation
from
the
four
past
months,
where
we
regularly
had
alerts
on
update
jenkins
sayo.
A
The
main
part
is
being
able
to
handle
enough
workers
process
that
are
able,
after
five
or
six
hours,
to
keep
serving
requests
without
being
in
a
world
states.
So
it's
a
matter
of
handling
between
the
keeper
of
connection
the
amount
of
threads,
the
amount
of
processes,
the
amount
of
parallel,
simultaneous
connection
etc.
A
But
now
it
seems
we
have
some
margin
just
to
not
record
that
the
virtual
machine
seems
to
be
located
and
pinned
to
an
ec2
hypervisor,
which
is
in
poor
state.
We
have
a
lot
of
cpu
still
on
that
machine
and
except
changing
to
the
category
of
just
the
one
upper
or
the
one
lower
in
size.
We
cannot
change
the
the
cpu
main
line.
We
cannot
move
to
another
hypervisor.
A
I
assume
that
that
machine
is
really
really
old
and
it's
in
and
it's
weird
it's
using
a
ec2
line
of
category
instance,
which
is
2013
generation,
so
we
cannot
benefit
from
the
latest
network
and
we
are
not
able
to
migrate
it.
The
only
solution
is
either
we
used.
We
create
a
snapshot
and
start
a
brand
new
machine
and
provision
it
and
move
everything.
So
if
we
have
to
do
that
on
ec2
better
to
do
it
on
a
rocker.
E
E
This
email
in
a
github
org
profile
with
me,
so
it's
still
accessible
and
it
was
just
for
this
public
email.
It
was
just
for
displaying
on
top
of
the
jenkins
safra
main
page
homepage,
nice.
A
E
It
was
an
issue
something
I
wanted
to
do
since
some
months
already,
so
it
was
an
opportunity
to
do
it.
It
can
be
improved,
but
I
think
it
can
it's
fast.
Let's
try,
first
text.
A
A
A
Okay,
thanks
alex
caller
bill
is
failing
untrusted,
so
that's
the
subject
the
main
priority
subject
in
short
term,
we
need
to
generate
a
new
certificate
for
update
center.
To
be
sure
that
also
the
updates
she's
on
is
is
working.
A
A
Okay,
continue
duplicate
tmg
in
favor
of
docker.
E
I'm
I
have
some
tests
to
or
which
are
failing,
but
it
will
be
fixed
quickly
and
then
I
will
do
another
part
which
is
removing
every
trace
of
emg
in
the
pipeline
library
and
some
other
repurposed.
A
A
Okay,
migrate
updates,
jenkins
io
to
another
cloud.
So
that's
what
I
mentioned
earlier,
so
I
didn't
have
time
to
work
on
that
one.
I
hope
I
should
be
able
to
do
it
after
the
update
center.
A
The
goal
is
to
spawn
a
temporary
first
machine
on
oracle
and
start
adding
it
to
the
existing
flow,
but
it
won't
be
serving
data
to
the
end
user.
For
now,
the
goal
is
to
be
sure
that
each
time
the
date
center
is
on
generation
is
done.
It
will
upload
the
files
not
only
on
the
actual
machine,
but
also
under
a
new
oracle
machine.
A
There
might
be
a
proposal
on
that
issue.
I
haven't
written
that
yet
to
spawn
two
machines
to
have
a
kind
of
hca,
because
right
now,
each
time
we
operated
on
the
apache
server
and
we
had
to
restart
it
to
apply
a
specific
settings,
we
were
breaking
the
all
the
jenkins
installation
that
we
are
trying
to
get
updates
and
turn
that
moment.
A
So
the
goal
is
to
have
a
poor
person.
Aha,
which
means
one
that
a
volume
mounted
on
both
virtual
machine,
and
so
each
virtual
machine
is
only
a
tiny
one
with
apache.
The
goal
will
be
to
spread
the
load
between
two
machines
and
when
we
have
to
do
maintenance,
we
don't
break
the
update
center
for
everyone.
A
One
two:
three:
okay,
so
we'll
continue
working
on
that
one
important
manager
required
cloud
resource,
so
I
propose
given
that
it's
been
at
least
two
or
three
iterations,
that
we
have
both
issues.
I
propose
to
not
put
the
import
managed
on
the
next
milestone
and
if
anyone
has
time
and
is
willing
to
do
it,
then
you
can
do
it,
but
I
want.
I
don't
think
I
will
have
the
material
time
to
get
on
this
one.
So
I
propose
with
delay
of
at
least
one
iteration
sounds
good.
A
E
E
E
A
A
A
Thanks
a
lot
harvey
any
question
on
that
area.
A
Should
we
keep
it
on
the
next
iteration,
okay,
cool.
C
And
one
quick
question
on
something
else:
I
raised
an
issue
on
the
rate
limiting
cigarettes
io
for
the
jenkins
ci
docker
builds,
I'm
not
sure.
If
anyone
has
any
ideas
on
other
things,
we
can
do
there.
Yes,.
A
So
here
we
are
waiting
for
docker
docker
inc
to
promote
the
organization
to
tim,
because
they
already
did.
They
promoted
us
to
the
open
source
program.
A
A
However,
in
the
case
of
the
docker
images,
we
pull
official
images
which
are
accounted
on
api
rate
limit
since
it's
the
bigger
bandwidth
they
have
to
pay
for
that
and
the
rate
limits.
So
I
I
had
a
discussion
with
them
two
weeks
ago.
They
said
they
would
have
to
wait
after
that
long
weekend,
because
most
of
the
the
team
is
in
europe,
so
they
were.
They
were
all
out
of
office
last
week,
but
they
are
going
to
give
us
that
that
should
be
okay
for
us,
because
right
now
we
have
200.
A
We
have
the
right
200
request
for
six
hours,
time
window
and
we
are
rate
limited
which
mean
each
time
there
is
a
dependable
or
opening
a
few
requests.
We
are
done.
C
A
I
don't
know
for
today,
but
this
weekend
when
was
it
friday
or
saturday.
Last
time
we
had
the
first
batch
when
basil,
it's
when
basil
opened
all
the
adolent
pull
requests
on
the
docker
image
and.
A
A
So
yeah
the
alternative
is
thinking
about
bringing
cash
having
spawning
cash
on
the
thing
is
that
will
be
a
service.
We
need
to
restrict
that
service
to
avoid
being
spammed
or
mining
bitcoins.
A
It
has
to
be
ip
restricted
to
the
ip
range
of
both
azure
and
ec2,
where
we
spawn
the
virtual
machines
with
the
docker
builds.
So
we
need
to
spawn
a
registry
with
the
caching
mode,
yeah.
Okay,
I'm
adding
that
to
the
next
milestone.
I
will
ask
rv
he's
back
from
holiday
since
today.
Yes,
another
herb,
not
this
one.
A
Because
he
this
manager
is
in
holidays,
I'm
adding
it
and
taking
it.
Since
I'm
the
person
in
contact,
I
will
ping
them,
we
should
have
something,
but
so
so.
Yes,
I
saw
that
and
if
we
don't
have
anything
end
of
week
from
them,
then
we'll
try
to
docker
register
registry.
A
D
I
saw
one
last
week,
I
think,
but
I
told
you
and
they
corrected
it
was
on
their
part.
You
know
they
weren't
able
to
handle
the
308
status
code.
A
D
A
So
some
linux
distribution
package
jenkins
by
themselves
and
when
they
try
to
download
the
wire
from
the
mirrors,
sometimes
they
have
a
tool
that
doesn't
follow
the
http
redirection
so
most
of
the
time
they
have
to
get
the
full
link
on
get
jenkins
io
and
ideally
they
can
use
archives
for
that
because
that's
not
I
that's
not
something
done.
Often,
okay
might
be
good
to
add.
Maybe
a
warning
or
documentation
somewhere.
A
A
No
sorry,
my
bad,
the
runbook
is
already
merged,
but,
as
tim
you
proposed
that
should
be
public
documentation.
So
we
should
add
that
part
on
a
public
page.
So
we
don't
have
to
get
information
from
a
private
documentation
and
send
them
to
people
that
should
be
a
public
link
for
the
future.
A
Now
I
don't
know
if
they
answered
to
that
email.
I
didn't
saw
any
answer.
Last
friday
I
haven't
seen
okay,
I'm
watching
that
there
is
no
action
expected
on
outside.
They
have
to
to
run
the
action
and
send
them
send
us.
The
url
for
the
jenkins
mirror
so
I'll
propose
that
we
clear
the
milestone
and
then
we
wait
for
from
them
and
we'll
bring
them.
I
will
ping
them
in
two
weeks.
E
Tim,
you
also
suggested
to
add
an
issue
type
on
the
help
desk
for
the
mirror.
Oh
yeah,
I
yeah,
are
they.
E
E
A
I'm
clearing
the
milestone
for
the
mirror
itself.
Anyone
willing
to
reside
the
issue
or
whatever
is
welcome.
A
Digital
ocean
erv
and
I
need
to
take
an
appointment
with
them
to
discuss
the
goal
as
explained
last
week,
is
to
prepare
different
scenarios
of
sponsorship
needs
and
based
on
that
they
will
renew
or
not
and
will
negotiate.
They
seem
quite
positive
to
continue
with
us.
That's
a
good
new.
Now
we
have
to
just
have
to
do
it
so
rv,
I'm
adding!
U
and
I
on
this
one
and
we
need
to
just
take
the
appointment.
So
I'm
adding
it
to
the
next
milestone
looks
good.
A
Okay,
permanent
redirects
stories
is
that
isn't
that
one
finished?
Oh
no,
so
we
have
a
redirector
a
service
created
by
stefan
on
kubernetes
cluster,
which
works
very
well.
That
has
been
updated.
To
may
keep
the
context.
However,
it
seems
like
that.
I
don't
know.
Mark
and
alisa
didn't
move
the
cname
to
our
infra.
They
tried
to
configure
the
direction
so
it
partially
work
it's
improved.
But
yes,
we
should
take
over
the
domain
name
from
godaddy.
A
A
Finally,
ci
jenkins
io,
so
that's
an
old
issue
from
outage
from
one
month
and
a
half
I
haven't
heard
from
anyone
feedback
on
the
postmortem,
so
I'm
gonna
proceed
this
week
to
publish
the
postmortem
and
close
the
issue.
Unless
there
is
someone
who
doesn't
agree,
but
then
I
need,
I
need
a
feedback.
If
that's
the
case,
I
said
it
was
great.
A
So
nothing
to
do
here
milestones
think
next.
Almost
there
are
there
any
issues
on
the
infra
team.
Think
next
that
you
want
to
bring
and
maybe
prioritize.
B
A
B
A
Nope,
it's
not
done!
Oh
yeah.
Let
me
rephrase
is
it
in
production?
Yet
no,
it's
not
so.
My
proposal
to
you
is
finishing
upgrading
cup
cattle
on
the
image,
because
it's
required
close
up
the
the
okay
s,
because
it
I'm
sure
you
will
start
the
upgrade
without
the
okay.
Yet
and
then
you
can
start
prepare,
read
the
change
log
both
of
your
events
different
or
continue
or
prepare.
It
is
that,
okay
and
next
week
we'll
discuss
the
timeline
depending
on
the
outage
of
the
week.