►
From YouTube: 2023 09 26 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
Hello,
everyone
welcome
to
the
Jenkins
infrastructure
team
weekly
meeting.
Today
we
are
the
26th
of
September
2023.
So
that's
that
will
be
a
word
session
because
I'm
alone
today,
Mark
weight
is
currently
traveling.
A
Our
velomer
is
unavailable.
Stephen
is
giving
a
course
on.
Kevin
Martins
is
healed,
so
anyone
trying
to
poison
poison
the
team
must
be
brought
to
Justice
right.
Okay.
So
let's
do
that
quickly,
just
for
the
sake
of
running
the
meeting,
one
first
of
all
announcements,
so
the
weekly
release
2.425,
has
been
released
with
success,
so
I
believe
packages.
Docker
image
are
out
already
deployed
to
infrastia
Jenkins.
So
it's
running
well
for
now.
A
Next
release
check.
This
item
will
be
done.
I
assume
tomorrow,
since
Kevin
is
Hitler
to
be
done
later,
no
more
announcement
on
my
side
as
far
as
I
can.
Oh
no
there's
been
a
quick
incident
on
incremental
publisher,
which
was
in
words
that
stayed
after
an
M
deployer
opened,
so
we
had
to
delete
the
deployment
and
recreate
it.
So
that
was
five
minutes
of
unavailability
of
outage.
A
Today,
I'll
open
a
posteriorly
afterwards
status
elements
with
explanation,
but
what
happened
is
that
the
end
state
was
unable
to
deploy
in
West
stock
because
the
old
replica
set
was
being
deleted
but
never
terminated
and
it
was
on
unwanted
state.
So
we
had
to
remove
replica
sets
but
deployment
and
then
apply
and
file
again
walked,
so
replica
set
was
not
atomically
deleted.
A
I
had
to
remove
it
manually
and
redeploy
next
weekly
will
happen
next
week,
2.426
as
usual.
A
Next
LTS
I,
don't
know
so
I
will
put
n
a
I
assume
it
will
be
middle
of
October,
so
we'll
confirm
next
week,
when
everyone
will
be
there.
As
far
as
I
can
tell
no
security
advisories,
as
you
can
see,
none
announced
we
had
one
last
week
for
the
course
you
can
everyone
remember
next
major
event.
We
have
mock
weight
currently
attending
the
devops
world
tour
at
Chicago
this
week,
then
Santa,
Clara
and
London
I
believe
London
might
change
so
be
careful
I'm,
removing
the
dates.
A
Don't
forget
the
first
DM
and
October
we'll
see
the
Octoberfest.
We
need
to
be
ready,
okay,
so,
let's
get
started
with
the
work.
We're
able
to
finish
blocked,
we
have
a
task
user
blocked
by
an
anti-spam
system
when
it
looks
like
we
have
some
IP
ranges
that
are
considered
as
spam
ranges,
but
these
happy
ranges
are
shared
by
different
isps,
so
we
had
to
unbox
the
user.
Here,
there's
been
an
issue
on
the
plugin
not
showing
up,
but
it
was
on
the
plug-in
side.
A
The
maintenance
took
care
of
that
and
it
was
fixed
by
itself
no
action
recoil
from
us.
We
had
an
issue
with
launchable
last
version.
It's
still
failing.
We
tried
to
deploy
it
and
it
failed
Jenkins
score
built
during
Alpha
day.
So
we
are
to
roll
back
to
1.66.0.
That
has
been
raised
on
the
launchable
command
line,
issue
tracker
and
we'll
see
when
the
problem
will
be
fixed.
That
is
an
important
thing.
It
means
next
launchable
updates
require
us
to
be
more
careful.
A
We
might
probably
want
to
test
it
directly
using
test
test
it
next
time
using
the
pipeline
library
or
a
custom
installation
function
in
a
pipeline.
A
Another
issue
due
to
anti-spam
fixed
same
same
kind
of
problem,
same
result
and
finally,
the
mirror
the
list
of
mirrors
forget
Jenkins
IU
are
now
stable,
is
now
stable
and
enabled
bell
net
is
back.
There
was
I
think
it
was
servana
which
is
now
back
and
we
have
removed
the
server
that
weren't
used
due
to
no
AirSync
or
FTP.
So
we
sent
an
email
last
week
to
the
maintainer
of
these
minerals.
They
weren't
response
responsive
enough,
so
we
have
removed
the
mirrors
for
now.
A
If
they
contact
us
back
to
re-enable
the
mirrors,
then
we
will
take
care
of
adding
them
back.
It's
not
it's
not
written
in
row,
but
yeah.
Now
we
have
a
full
and
clean
list
of
mirrors,
just
not
removing
a
mirror
trigger
a
full
riskan,
which
means
the
fallback
might
be
used
for
a
few
hours
delegating
most
of
the
traffic
to
all
backs.
A
Should
be
used
as
fallback
even
with
a
lower
weight
or
as
a
mirror
or
the
lower
weight
or
we
need,
is
a
full
back
mirror
or
Steed
on
the
Jenkins
infrastructure,
because
some
old
packages
are
fought
backed
to
OSU
SL,
which
seems
to
have
a
Time
range
and
after
the
time
launch
they
delete
the
packages
should
be
the
fallback
why
archive
chain
can
say:
oh,
we
are
moving
it
to
digital
ocean,
so
it
can
under
being
a
fallback
Mirror
by
default
in
one
ways
and
performances
so
that
tune
from
the
old
machine
that
was
used
as
a
low
priority.
A
Mirror
there's
been
discussion
on
that
topic,
I,
remember,
Mark
and
Olivier.
The
thing
that
we
want
both,
but
in
that
case,
given
the
infrastructure
effort
since
archives
in
Kentucky
has
everything
the
goal
is
to
put
it
as
a
as
a
low
level
and
fallback
mirror
and
or
lower
ways
by
default.
It
has
all
the
content,
so
being
only
fallback
should
be
the
way
to
go
issue
to
create
on
the
new
milestone.
A
Now
what
about
the
work
in
progress,
I'm,
taking
them
on
the
order
of
the
list?
First
thanks
Stefan
Merrill
for
walking
and
helping
our
new
contributor.
So
there
is
a
walk
on
the
backer
image
to
all
in
one
image
we
are
building.
Since
we
are
back
trying
to
build
Windows
container,
we
are
more.
We
are
trying
to
move
all
the
test
Earnest
to
a
tool,
Named
Gus,
which
will
make
things
easier
for
testing
and
more
portable
there's
been
an
effort
on
ghosts,
especially
with
the
incoming
3v
thing.
A
So
Stephanie's
worked
a
lot
that
help
on
the
playwright
issue
from
our
new
contributor
that
will
help
on
the
incoming
Windows
support
and
that
will
help
on
making
the
build
faster.
So
that
issue
is
a
set
of
tiny
step
by
step
thanks
Stefan,
for
taking
care
of
that.
There
is
some
automation
with
update
CLI,
and
the
next
step
will
be
to
move
all
the
sanity
check
to
either
a
acceptance
test
or
sensitive
test.
We
need
the
the
two
of
them
details
on
the
issue:
walk
in
progress
on
a
regular
cloud
and
tools.
A
The
goal
is
to
remove
them,
so
the
status
is.
We
have
removed
the
job,
we're
going
to
Archive
the
terraform
project,
and
then
we
will
remove
the
wireless
system
integration,
but
only
once
archive
thinking,
so
you
will
buy,
will
have
been
migrated
away
next
step.
We
are,
we
have
effectively
switched
from
the
fsec
to
3v
for
static
analysis
of
terraform
files.
A
3V,
sometimes
is
a
bit
complicated
to
manage
it,
because
the
inline
exception
are
a
bit
more
sensitive
due
to
the
regular
support.
It's
work
in
progress.
It
has
already
been
reported
to
the
aqua
sector
3B
project
on
the
working
hard
on
it.
So
now,
the
next
step
before
closing,
the
issue
will
be
to
remove
the
effect
form
everywhere
on
the
infrastructure,
speed
up
the
docker
image
library
to
create
push
tag
at
the
same
time
for
both
kitab
and
Docker.
That
is
an
important
part
required
for
the
next
step
of
irm
transition.
A
I,
haven't
done
any
changes
and
didn't
have
time
to
work
on
the
request
field
from
Jr
login
page,
so
to
be
continued.
If
I
don't
have
time
on
the
next
Milestone
that
will
go
back
to
the
form
to
the
that
will
be
back
to
the
back
end
of
issues
h
a
I'm
sure
for
the
replicated
Services
huge
work
from
Stefan
on
that
part.
A
So
we
have
identified
that
we
need
to
be
careful
on
the
on
T
Affinity
on
pdb,
and
now
we
have
a
list
of
the
replicated
services
that
we
are
treating
one
by
one
to
ensure
it
has
both
anti-affinity
to
ensure
services
are
spread.
So
if
we
lose
a
node
or
do
maintenance,
then
the
service
is
still
answer
if
it's
replicated
and
the
pdb
to
ensure
that
normal
operations,
such
as
rotating
the
operating
system
or
upgrading
kubernetes
nodes.
A
In
that
case,
this
is
the
scheduler
no
out
orchestrate
start
how
much
node
can
go
offline
at
a
given
moment.
So
that's
nice
job.
We
are
going
to
iterate
on
the
pdb
to
open
the
road
on
fully
migrating
these
services
to
lm64..
So
thanks
Stefan
for
that
great
work.
The
list
is
really
useful,
so
we
can
split
the
burden,
repo.
A
So
we
have
decided
of
the
architectures
and
everything
is
ready
to
roll
for
starting
the
my
sequeler
and
I'm,
taking
over
the
docker
image,
build
to
help
Stefan.
So
we
don't
have
too
much
tasks,
so
we
should
be
able
to
deploy
the
new
MySQL
instance
to
support
that.
No,
that
new
machine
reminder
matomo
should
run
from
the
start
on
iron
64.
A
A
world
about
artifactory
bandwidth
reduction
options,
so
every
issues
has
been
fixed
technically.
So
now
it's
on
Mark
weight
area
to
confirm
that
the
statistics
that
you
receive
weekly
from
g-frog
confirmed
that
we
have
reduced
the
bandwidth
and
then
next
month
we
should
be
able
to
report
success
or
failure
to
g
frog.
So,
let's
see
the
result
of
the
real
life
system,
if
it
doesn't
decrease,
then
we
will
need
to
analyze
where
this
traffic
come
from.
A
The
topic
about
deleting
the
pages
on
Jenkins
IO
that
aren't
accessible
and
indexed
anymore
is
will
be
put
on
hold
because
they're
always
busy
an
update,
Center
and
other
tasks
and
less
availability
for
him.
This
week,
I
will
check
this.
I
will
put
this
issue
on
the
next
Milestone
and
I
will
try
to
remove
at
least
the
40
page
on
short
term
before
every
can
continue
his
work
around
backing
up
and
doing
the
migration
finally
award
on
update
Junkin,
Sayo
migration.
A
A
We
weren't
able
to
create
or
spend
time
on
the
Oktoberfest
issue.
I
hope
we
will
have
this
week.
Otherwise
we
will
just
say
no
Oktoberfest
for
the
Jenkins
infra
I
hope
anyone
ready
to
help
could
help,
but
yeah
don't
hesitate.
If
you're
interested,
though
we
still
have
a
few
issues
that
could
be
done
and
marked
on
Oktoberfest
on
last
minute,.