►
From YouTube: 2023 01 17 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
weekly
infrastructure
team
meeting.
We
are
the
I,
don't
even
know
the
date
17th
of
January
2023.
Today
we
have
reported
Stephen,
Merrill,
Marquette,
Kevin,
Martin,
hello,
everyone
I
hope
you
are
doing
well.
A
A
Next
release
is
the
23.
Is
that
correct,
where
17
no
24.
B
A
Okay,
thanks
Mark
Jenkins,
we
have
a
publicly
advertised
at
history.
A
A
A
There
any
comment
about
calendar,
no
upcoming
event
that
we
forgot
okay.
So
let's
get
started
with
the
walk
with.
We
were
able
to
completely
finish
so
at
Jenkins,
your
component
to
see
agents.
A
A
Of
course,
thanks
again
for
the
huge
walk
on
that
area,
GitHub
app
for
plugin
is
scoring.
So
thanks
survey,
you
helped
Adriana.
As
far
as
I
can
tell
the
application,
the
GitHub
apps
on
installed
and
ready
now
it's
a
matter
of
providing
the
correct
key
to
the
application
or
the
in
the
correct
format.
C
A
Okay,
so
I'm
quite
a
bit
optimistic
that
you
will
help
and
both
of
you
I
will
finish
that
so
nice
job
folks,
a
component
has
been
archived.
A
A
However,
an
improvement
on
cig
and
kinsayor
thanks
Stefan
for
adding
AWS
virtual
machine
based
on
Windows
2022,
so
that's
an
add-on
to
the
actual
Azure
virtual
machine,
Windows
12
2022
from
last
month,
which
means
now
if
Azure
goes
down
first,
if,
as
it
goes
down,
we
still
have
machines
in
AWS
and
CI
Jenkins
IO
spread
the
load
between
the
two
clouds
and
the
costs.
A
C
C
C
A
C
C
A
Okay,
I
think
that
somewhere
else
I'm
not
blaming
you
or
I.
You
looked
on
the
defensive
I'm,
not
blaming
you
I'm,
asking.
A
C
A
A
Okay,
that
it's
closed
and
it's
okay,
we
add
the
account
next
issue
is
an
account
related
issue
that
has
been
solved
from
my
bank.
Can
you
please
read
the
title
so
I
remember
it
was
a
translated
it
on
Google
and
it
was
something
like
I've
been
cooked
by
the
anti-spam
system,
but
in
Russian.
A
Okay,
so
I've
checked,
but
that
was
weird
because
the
person
opened
a
twin
issue,
so
I
triggered
the
password
reset
and
I
checked
that
the
SMTP
relay
was
okay.
Based
on
the
logs
in
the
printed,
let's
say
the
Gmail
is
MTP
received
the
email.
So
if
that
person
doesn't
see
any
email
on
their
mailbox,
I
can't
do
anything
for
them,
so
I
told
them
to
look
their
spam
and
we'll
see
that
one
was
weird
because
using
two
unrelated
emails
with
stone
related
account
name
word
anyway:
Ash
STS,
block
use
of
trustees
and
search
CI.
A
The
Gen
gensec
team
security
team
was
blocked
when
using
Chrome
to
reach
both
controllers,
because
for
both
of
them
we
use
private
channels,
his
ossh
tuner
or
VPN
private,
and
both
of
a
private
vipin.
Sorry
and
the
with
chrome,
since
publicly
the
jenkins.io
domain
says
that
all
the
subdomain
require
hsts,
which
say
which
tell
the
browser
to
always
switch
to
https
with
a
valid
certificate
and
don't
accept
manually,
signed
certificates,
untrusted
certificate
or
http.
A
The
thing
is
that,
in
the
case
of
these
two
machines,
they
are
private
and
they
are
machines.
So
we
use
let's
encrypt
with
HTTP
challenge,
for
the
virtual
machine,
usually-
and
in
that
case,
since
they
are
private
machine,
they
cannot
validate
the
let's
encrypt
challenge
for
a
new
certificate
because
they
are
private
and
they
are
not
exposed.
A
A
We
never
had
time
to
spend
on
this,
so
I
generated
manually,
the
DNA
or
using
the
DNS
technique,
a
first
set
of
certificate
to
unblock
them
instead
of
callbacking
the
chestis,
because
Asha
stairs
takes
time
to
it
has
a
long
detail.
It
would
have
taken
three
months,
so
instead
we
generated
a
valid
certificate
and
it
it
unblocked
them
immediately,
and
so
that
issue
links
to
another
issue.
A
A
A
Maven
387
is
now
generally
available
for
developer
on
cigo.
So
thanks
everyone
involved
in
that
especially
Stefan,
but
not
only
your
verse,
Diddy's
work.
We
haven't
heard
about
any
issue
with
that
Maven
version
and
it's
all
all
Container
machines
and
setups,
and
thanks
Mark
for
adding
it
to
the
new
the
CPUs
machine.
A
We
had
an
LTS
release
last
week
and
all
of
our
instances
were
updated
at
least
the
one
using
LTS
version.
So
thanks.
Everyone
on
that
part
as
well
I
wasn't
available
that
day.
So
thanks,
Stefan
and
ervy
for
backing
me
up
on
that
area.
That
proved
that
the
team
is
not
dependent
on
me
and
these
areas,
which
is
a
good
thing
which
is
healthy.
A
B
A
A
So
manually,
if
you
do
everything
manually
that
works
very
well,
we
validated
that
as
a
first
step,
but
then
automating
that
permission
model
with
terraform
and
the
Azure
API
was
quite
an
issue
thanks
a
lot
team
for
pointing
us
to
the
element
that
we
missed
or
misunderstood,
and
thanks
Stefan
RV
for
Robert
the
king
with
me,
and
asking
a
lot
of
good
questions
which
allowed
us
to
succeed
on
that
area.
But
here
we
spend
one
day
and
a
half
on
that
topic.
We
learned
a
lot
on
the
process.
A
So
now
we
have
to
apply
to
puppets
to
change
the
let's
encrypt
system
to
use
DNS,
so
we
need
to
play
around
with
puppets,
but
the
good
news
is
that
since
we
manifested
ourselves
on
the
puppet,
let's
encrypt
module,
saying
we
are
interested
in
the
support
for
DNS
as
your
last
week,
they
already
merged
the
pull
request
that
was
stealing
for
monthses
and
they
released
the
world
thing.
So
we
should
be
able
to
not
deal
with
third
bot
binary
at
all
and
do
its
all
in
pure
puppets.
A
A
A
The
the
reason
is
because
we
want
to
put
every
builds
in
the
near
future
on
only
the
backer
image
image.
So
we
don't.
We
need
to
install
it
and
Transplant
the
changes
we
did
on
the
web
builders
foreign
from
giving
about
sourcing
in
dash
index.html
for
get
to
and
kinsayo.
We
didn't
have
time
to
work
on
that.
We
should
be
able
to
do
it
next
week.
A
A
When
you
have
a
requests,
it
goes
through
the
redirector
and
if
the
redirectors
finds
the
file
it
gets
Ash
and
from
the
ash
on
its
database,
it
decide
to
redirect
one
of
the
closed
mirror
or
to
serve
the
file.
As
a
fallback
in
the
case
of
the
index
HTML
file,
we
need
a
need
that
the
root
file
on
the
bucket
that
one
was
moved
manually
on
the
buckets
the
request
from
giving
is:
can
we
Source
it
somewhere?
So
it
can
be
changed?
A
So
I
propose
so
sorry:
I
am
I'm
a
bit
tired,
so
I
forgot
to
reschedule.
A
A
A
A
A
Okay,
I
have
a
personal
matter
that
there
is
that
giving
us
an
IRC
three
weeks
ago
and
almost
every
day,
I
asked
Lee
major
publicly
or
privately.
Can
you
open
an
issue
for
that?
Please,
so
I
will
feel
bad
if
we
don't
take
it
now,
even
if
it's
not
prior,
but
that's
only
personal.
So
if
it
bother
anyone
else,
I
don't
mind
taking
it
because
of
that.
Well,.
A
A
We
had
a
new
issue
and
that
one
I
don't
mind
waiting
for
this.
One
I
will
add
message
because
last
time
I
had
an
exchange
with
that
user.
The
exchange
was
quite
complicated,
so
I
will
add
the
message
and
reschedule
for
later,
that's
related
to
the
way
that
mirrors
are
managed
and
basically
I,
don't
want
to
provide
any
more
support
for
that
person,
because
that's
how
the
under
mirror
Management
on
their
own
infrastructure,
so
either
they
use
a
standard
mirror
or
not.
A
A
So
no
objection
if
I
move
it
to
infra
team
Sim
next
and
I
need
a
message.
Yeah.
B
A
I
still
plan
to
just
throw
an
eye
and
decide
if
it's
an
issue,
there
might
be
an
issue
now
home.
So
I
just
want
to
send
it
to
check
from
someone
of
us,
but
when
time
will
come.
A
Next
Issue
bump
terraform
module
for
AWS
eks,
so
that
one
was
moved
on
that
Milestone
back,
because
we
weren't
able
to
so
sorry
Stefan
discovered
that
there
was
a
an
older
cluster
consequence
of
that
issue
that
had
to
be
cleaned
up
to
avoid
spending
too
much
credits
on
AWS,
and
we
have
a
solution
for
the
let's
encrypt
setup
on
that
one.
Now
that
we're
able
to
do
it
for
trusted
CI,
there
is
no.
A
A
I
propose
that
we
remove
any
Milestone
from
this
one,
because
we
don't
have
any
more
expected
action
and
the
course
of
the
course
of
action
will
be
that
pull
request
being
accepted
or
merge
and
Update
Center.
So
it's
outside
our
scope
is.
B
That,
okay
for
everyone
agreed
and
and
the
pattern
I
specifically
asked
Daniel
back
a
while
ago,
I
have
merged
permission
to
the
update
Center
repository,
but
I
asked
him
specifically.
Do
you
prefer
that
I
exercise
that
permission
or
not
and
his
preference?
Is
that
I
not
exercise
that
permission,
so
he
would
rather
be
the
one
who
merges
all
changes
to
update
Center
and
I
like
that.
That
is
perfect.
He
maintains
it
very
well.
A
And
given
the
title
of
the
pull
request
once
if
that
pair
is
merged,
then
that
will
close
the
issue
anal
disk
back,
because
it's
the
same
so
we
don't
have
to
worry
about
cleaning
up
the
issue.
A
A
B
So
so
there
are
lots
of
things
that
we
get
from,
that
that
data
analysis
and
we'll
take
action
on
those
right.
We've
got
several
places
that
we
need
to.
We
need
to
improve,
including
more
caching
on
my
home,
lab
and
and
more
caching,
on
ci.jenkins.io
and
and
we've
got.
Some
consumers
that
were
reasonably
confident
are
are
not
contributing
enough
to
the
Jenkins
project
to
justify
the
bandwidth
they're
using.
A
So
one
of
the
takeaways
we
will,
we
will
have
to
confirm
I,
will
had
a
message
on
the
issue
after
the
defrog
meeting
tomorrow
we
have
two
meetings.
One
Stephanie
and
iron
Mark
about
Mark
will
show
us
the
data
on
how
to
treat
it
and
then
Mark
and
I
will
have
a
meeting
with
g
frog
to
ask
them
to
send
us,
if
possible,
weekly
reports
to
discuss
about
what
Mark
discovered.
A
But
one
of
the
takeaways
is
that
we
we
need
to
confirm
by
with
the
real
IPS,
but
we
have,
let's
say
a
good
feeling
that
our
infrastructure
is
still
consuming
a
lot.
So
the
work
that
everybody
did
on
the
caching
proxy
might
have
way
more
impact
than
what
than
what
we
expect,
which
means
the
work
on
private
Gates
and
public
Gates.
The
two
new
cluster
with
the
network
solving,
is
top
priority
in
order
to
put
the
ACP
back.
A
The
rest
will
be
exchanges
with
g
frog
to
ask
if
we
can
ban
some
eyepiece
that
marks
that
mock,
discover
where
High
consumers
I
don't
give
name
right
now
and
eventually,
if
g-frog
doesn't
have
any
objection,
the
world
authentication
of
repo
one
or
Cache
or
mirrors
and
ldap
in
high
availability
modes.
That
are
closely
related.
That
topic
might
be
de-prioritized
with
the
other
steps
first,
because
we
cannot
treat
all
the
tasks
at
the
same
time
we
have
to
sequentialize
and
the
ACP
might
make
more
sense.
For
now,
all.
B
Right,
yeah,
the
the
data,
the
data,
the
data
bandwidth
or
the
bandwidth
data,
certainly
supports
the
artifact
caching
proxy
being
a
crucial
part
of
this
of
this
effort,
because
a
big
chunk
of
the
actual
data
transfer
that
I
saw
is
really
right
from
our
own
releases
repository.
So
it's
delivering
our
own
bits
to
ourselves.
A
So
that
issue
keeps
being
on
the
Milestone
anyway,
your
turn
private
Kate.
Can
you
give
us
a
status.
C
C
So
yes,
experimentation
about
this
job.
Even
when
this
search
up
is
running
correctly,
we
will
be
able
to
backup
the
current
I
think
inside
you,
data
and
move
it
to
this
new
cluster.
Then
we
will
be
able
to
to
move
the
DNS
record
to
point
to
this
new
cluster.
A
Thanks
a
lot,
that's
cool,
don't
forget
the
pull
request
to
add
the
the
outbound
IEP
kubernetes
management.
A
A
We
all
do
you're,
not
alone
on
that
on
that
war,
yeah
mirror
start
report
wrong
results
on.
C
A
Oh
I
was
I,
didn't
have
time,
I
propose
to
move
it
back
to
in
Fatima
suggested.
Last
week.
I
was
a
trigger
because
I
told
I
was
going
to
help
you.
Whenever
you
want
a
Hyatt
time,
so
I
propose
will
remove
a
Simi.
We
might
spend
some
time
on
it,
but
I
propose,
let's
see
later.
A
A
And
it's
on
me:
I
forgot,
it
was
on
my
side
and
they
didn't
check
it
so
definitively
to
be
done
next,
milestone
our
Dean
bondage
on
Publishers
latest,
hey
that
one
untrusted
cigen
can
say.
Oh
it's
been
numerous
months
where
an
a
set
of
all
tags
on
the
agent
images
in
Bound
agent
and
SSH
agents.
These
old
tags
are
rebuilding,
sometimes
daily,
sometimes
weekly,
sometimes
monthly.
We
weren't
able
to
find
why
and
we
thought
it
was
a
bug
or
a
word
Behavior,
but
today
we
were
able
to
find
the
one
of
the
causes.
A
Can
anyone
see
what
does
commit?
Does
it's
important
so
I
prefer
sharing
the
information
that
pipeline
instruction
says
for
that
pipeline.
So
for
that
specific
tags,
all
the
tags
that
adds
a
Jenkins
value
with
that
instruction
in
the
past
once
they
have
been
parsed,
so
one
build
triggered,
read
the
chain
can
find
and
say:
oh
I
need
an
additional
trigger
at
pipeline
level,
not
at
multi-branch
level.
That's
the
trick
part
and
the
pipeline
say:
oh
I
will
try
to
pull
the
SCM
and
I
if
I
see
any
change.
I
will
rebuild
myself.
A
Second,
we
don't
need
a
policym.
We
have
a
multi-branch
pipeline
which
takes
care
of
oh
at
least
once
a
day.
Let
me
scan
the
world
repository
and
decide
if
a
build
should
be
triggered
or
not,
and
all
the
analysis
that
Mark
Daniel
team,
high
and
other
people
did
was
to
check
the
multi-branch
setup
with
build
strategy.
A
That
say
if
a
tag
is
older
than
three
day
then
consider
it
should
not
be
built
only
discovered
which
work
well,
we
demonstrated
each
time
you
manually,
scan
it
work
as
expected
and
as
configured
so
that
setup
is
okay,
but
now
the
challenge
is
these
all
tags.
We
don't
want
to
change
all
the
old
tags
from
the
past
to
remove
that
from
these
old
tags,
but
these
tags
already
have
the
polling
enabled
so
I've
asked
the
question
on
different
location
and
I'm
waiting
for
answers.
A
A
Another
solution
will
be
to
recreate
the
multi-brand
from
scratch
that
they
would
check
all
the
tags
and
say:
oh
these
tags
are
old,
I
won't
try
to
build
them,
meaning
I
want
powers
that
Jenkins
file
and
I
won't
enable
pulling
a
Sim
so
that
one
can
be
tested
immediately
on
Docker
agent
and
Docker
inbound
agents
for
SSH
agent.
We
will
have
to
wait
a
few
days
because
yeah
it
was
done
five
hours
ago.
A
So
issue
has
been
commented
and
we
definitively
need
to
work
on
that.
We
worked
the
three
of
us
on
that
one
for
knowledge,
sharing.
A
It
has
been
backup
backed
up
already
and
I,
don't
mind,
removing
it,
because
most
of
these
tags
have
a
build,
build
rotation
policy,
so
Jenkins
already
deleted
the
builds.
The
last
two
did
builds
and
that's
why
the
polycam
keep
rebuilding
because
it
lost
the
previous
one.
So
it's
a
B4,
nothing.
So,
of
course
it's
from
no
known
state
to
code.
It's
a
oh
new
code.
I
have
to
build,
but
it
fails
of
course.
A
A
Any
question,
so
we
keep
working
on
that.
One
finally,
account
then
can
say
you.
Admin
access
for
Stefan
I
did
not
have
time
to
check
on
that
one
Stefan.
Are
you
mad
if
I
move
that
one
to
entrust
team
next
to
be
sure
that
we
walk,
because
clearly
we
had
too
much
issues
on
our
plates
for
that
milestone,
so.
B
A
A
Thanks
for
your
understanding,
okay
on
the
backlog,
I,
don't
think
we
had
so
I'm
checking
for
the
new
issues.
First,
do
we
have
new
issues
that
we
don't
have
either
on
the
backlog
or?
Oh,
that
one?
We
just
removed
no
new
issues
that
are
not
on
the
current
Milestone
on
the
backlog,
right.
C
A
No
problem,
I,
don't
think
we
should
plan
for
more
and
see
if
we
can
terminate
our
other
issues.
If
we
are
able,
then
we
will
take
on
the
backlog
just
a
few
things.
For
next
week
we
will
have
to
start
thinking
about
the
Ubuntu
22204
campaign,
because
we
have
a
lot
of
machine
on
1804
and
2004.
A
2004
is
okay,
because
it's
five
years
support
for
LTS,
but
we
have
a
lot
of
machine
on
18.
We
can
upgrade
this
machine
in
place.
We
can
migrate
these
machines
to
new
machines
with
updates,
or
we
can
change.
Architectures
I
don't
mind,
but
we
have
to
think
about
that
and
that's
are
they
found
in
December.
We
are
now
able
in
Azure
to
get
Ubuntu
22,
which
means
we
should
be
able
to
update
the
agent
virtual
machine
and
container
templates
to
Ubuntu
22..
A
A
A
bit
more
pressing,
though
kubernetes
update,
we
will
have
to
schedule
the
next
1.24,
if
I'm
not
mistaken,
because
we
risk
to
have
one
of
our
providers
stop
stopping
to
support
that
version.
C
C
A
Certainly
I
propose
that
we
sequentialize,
so
that
your
mind
is
not
overloaded.
A
Is
that?
Okay?
For
you?
Yes,
okay,
if
you
are
waiting
for
builds
to
take
one
hour
to
finish
and
your
mind,
is
free
I
propose
that
you
start
thinking
about
the
Battle
plan.
So
then
you
prepare
on
one
issue
that
you
can
exchange
on
a
written
form
with
Stefan
before
you
start
discussing
the
two.
A
A
few
of
what
need
to
be
done
is
that,
okay
for
you
so
first
the
written
better
plan
on
the
issue
that
is,
okay
and
as
soon
as
you
start
synchronizing
with
Stefan,
then
you
can't
move
to
the
current
Milestone.
The
related
issue
is
that,
okay,
for
you,
that
gives
you
enough
space
to
think
and
start
thinking
and
start
preparing
the
better
plan
without
forcing
you
to
do
it
at
all
costs,
so
you
can
focus
on
private
Gates.