►
From YouTube: 2023 05 02 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
Let's
get
started
with
announcements,
the
weekly
release,
2.402.
B
A
A
C
A
Thanks
Mark
second
announcement
updates
under
certificate
since
the
1st
of
May,
the
crawler
job
and
the
update
Center
job
stopped
working
because
they
are
one
month
ahead
of
the
certificate,
a
certificate
expiration,
so
I
forgot.
It
was
one
full
month,
I
booked.
It
was
one
week.
So
there
is
an
internal
safety
system
that
say:
oh
one
month
left,
let's
fail
with
an
error,
so
we
will
need
at
least
for
today
and
tomorrow,
for
a
few
days
until
next
week
to
disable
to
find
a
way
to
disable
that
check.
I'm
almost
sure
we
can.
A
There
is
a
way
on
the
code
until
we
can
renew
the
certificate,
but
that
was
mentioned
that
we
will
need.
We
will
have
plugins
that
are
expected
to
be
released,
but
not
available
on
the
update
Center
since
yesterday.
So
we
also,
we
will
also
have
to
update
job
configuration,
which
is
currently
six
hours
floating
window
to
be
48
hours,
just
to
be
sure
we
catch
back
the
deployment.
A
So
need
to
catch
back,
so
yeah
I
think
a
message
on
status.
Jenkins
are
you
wouldn't
kill,
as
well
as
an
updates,
because
we
haven't
updated
the
existing
elements?
I
will
take
care
of
that
if
it's
okay
for
you
plugin
releases,
disable
the
check
at
least
for
one
week.
A
So
that
means
the
tasks
are
to
be
more
important.
Hopefully,
I
tried
this
morning.
I
had
a
virtual
coffee
with
Olivier
now
and
the
key
he
sent
me
privately
after
the
validation
from
the
board.
Isn't
the
ca
key,
but
the
last
year
certificate
key?
So
it's
a
Miss.
We
need
Olivier
to
start
again
his
whole
machine
on
his
volts
to
send
to
encrypt
and
send
me
the
new
ca
key.
Otherwise,
I
won't
be
able
to
sign
the
Certificate
request
from
Stefan,
but
once
it's
done
that
should
be
easy
to
solve.
A
That's
all
for
that
specific
topic,
but
that
means
Update,
Center
and
crawler
the
jobs
in
charge
on
trusted
CI
to
generate
the
update,
Center
index
and
the
tools
index.
You
know
these
tools,
GDK
tools,
Maven
the
Jenkins
scanner,
to
install
the
metadata
for
both
these
elements
are
signed
by
these
jobs.
So
there
aren't
updated
since
the
last
24
hours.
A
A
word
about
Azure
maintenance
is
as
well
because
of
this
planning
of
human
tenancies
during
the
month
of
May.
So,
just
to
let
you
know,
we
will
have
to
open
issues
if
we
are
if
some
of
our
services
are
under
these
maintenances
I
saw
an
email
just
before
the
meeting,
but
I
had
two
or
three
on
my
backlog.
A
A
The
most
important
one
is
Ubuntu.
Ubuntu
1804
reaches
end
of
support
at
the
end
of
the
month
of
May
okay.
So
we
need
to
update
all
of
our
remaining
Ubuntu
1804
instances.
A
A
The
Only
Exception
is
the
packaging
system
on
PKG
jenkinsayo,
so
I
was
waiting
for
the
LTS
that
will
happen
tomorrow
before
putting
hands
dirty.
The
goal
will
be
to
containerize
to
use
the
docker
container
for
the
packaging
steps
to
provide
a
proper
tool
before
trying
playing
around.
That
will
allow
us
to
upgrade
the
host
machine
2.224,
and
then
we
should
be
able
to
work
on
the
container
version
to
have
a
reproducible
process
for
the
packaging
steps.
A
The
main
targets
are
the
red
ads
packagings
tools
on
Ubuntu
18.
We
have
a
specific
version
that
we
know
that
work
on
Ubuntu
20
the
tool
doesn't
exist
at
all.
No
one
was
able
to
run
create
repo
on
Ubuntu
2004
and
there
is
a
new
version
on
2204
the
current
LTS
that
we
are
targeting,
but
it's
a
rewrite
from
python
to
Pure.
C
So
Damian
yes,
there
is,
there
is
a
facility
that
we
could
consider
purchasing
the
extended
support
maintenance
from
from
canonical.
If
we
say
we
have
to
stay
on
Ubuntu
1804
for
a
little
while
longer
I,
don't
know
if
they
offer
it
for
free
to
open
source
projects.
I
doubt
it,
but
but
there
is
a
product
that
extends
the
life,
the
security
support
for
1804.
If
we
really
need
it.
C
A
A
So
kubernetes
1.25
we
should
be
able
to
do
it
in
June,
because
the
end
of
life
for
Azure
and
digital
lesson
for
the
1.24
that
we
have
in
production
today
is
end
of
July.
So
my
proposal
is
that
we
target
the
upgrade
to
of
our
cluster
to
kubernetes
1.25
to
June.
A
There
is
one
new
upgrade
I
wanted
to
push
during
the
summer
or
later,
but
we
might
need
to
do
it
earlier,
but
the
good
thing
is
that
it
looks
it's
going
to
be
okay
with
the
one
year
of
cleanup.
That's
the
puppet
7
version.
A
A
The
preliminary
test,
at
least
on
the
unit
test
and
vagrant,
shows
no
problem
on
that
one,
whether
we
are
on
Ubuntu,
18
or
22,
so
that
one
should
be
quite
easy,
but
that
will
require
shutting
down
the
wall
puppet
thing.
We
should
not
break
services,
but
we
will
have
to
do
it.
It
will
it's
a
slow
and
careful
operation
because
we
have
to
do
it.
Machine
by
machine,
so
that's
a
full
day
of
work
and
full
day
one
full
day
of
preparation.
A
So
I'm
not
sure
when
we
should
be
able
to
do
it.
There
is
no
emergency,
so
I
propose
to
do
it
once
Ubuntu
222
is
finished.
A
I
will
share
the
pull
request
and
the
link
to
you
once
it
will
be
done.
A
A
Will
be
the
third
April,
no
3rd
May
2023?
We
expect
2.387.3
Chris
turn
Israelis
lead
unanswered
on
the
Jenkins
release,
channel
and
plan
you
plan
to
start
at
4,
AM
UTC
to
start
at
four
a.m:
UTC,
which
means
6
a.m,
for
the
European
Central
of
European
timeline,
which
Maps
perfectly
to
the
time
of
us
being
awake
because
it
takes
two
hours
to
build
a
release
bit
more
2
hours
and
30
minutes.
A
So
that
means
starting
at
eight
eight
past
30
in
the
morning
on
our
time
on,
at
the
time
for
Stefan,
Bruno,
I
and
Harvey,
we
should
have
the
end
of
the
release
and
beginning
of
the
package.
So
if
the
package
fail
that
will
be
morning
beginning
of
of
day
for
us,
I
will
be
there
in
any
case,
since
I
will
wake
up
start
early
and
finish
early,
so
we
are
covered
Airway
and
Stefan.
A
C
A
I
will
try
to
be
as
brief
as
possible.
The
burn
bills
are
now
split
so
theoretically,
and
what
I
saw
during
the
weekend
tend
to
prove
that
that
assumption,
even
if
you
have
multiple
bomb,
builds
running
and
waiting
or
using
kubernetes
agents,
the
other
normal
builds
for
plug-in
developers
or
other
projects
are
still
allocating
without
waiting.
So
if
you
have
a
bomb
pickup
bill,
you
won't
wait
for
one
to
two
hours
before
your
build
is
taken
as
a
plugin
developer.
That
should
be
a
nice
Improvement.
A
A
Reproducible
between
two
builds
ISO
ACP
failure
due
to
DNS
temporary
DNS
resolution
failure,
I
mean
I,
don't
see
anything,
we
could
do
about
AWS
DNS
failing
for
a
few
seconds,
not
worth
the
effort,
so
some
failures
on
what
appears
but
I'm,
not
sure
of
myself
there
what
appears
to
be
test
failure
inside
the
bomb
code,
so
I'm
not
sure
if
it
was
real
test
issues
that
could
be
because
Bowman
plugin
were
updated
while
working
on
the
info.
If
it's
related
directly
to
the
info,
I'm,
not
sure
I
can
correlate
it.
A
C
Yeah
so
there's
there
as
far
as
I
can
tell
there
may
be
well
I
attempted
to
release
a
new
version
of
the
bomb
over
the
weekend
and
the
build
failed.
I
didn't
do
the
analysis
to
understand
why
I
just
launched
one
now
and
if
we're
lucky
it
will,
it
will
pass
and
if
we're
not
lucky,
it
won't
pass
and
we'll
diagnose.
Why.
A
We
were
able
to
contain
the
excessive
consumption
on
two
Azure
different
usages.
First,
one
was
because
of
cig
and
kinsayu
that
had
a
lot
of
increased
activity
during
the
past
two
weeks,
especially
the
acceptance
test
and
core
IM
machines.
A
The
data
we
have
on
datadog
shows
that
this
machine
were
clearly
underused,
so
we
decreased,
Alf
cost
machine
same
amount
of
CPU,
even
if
I'm
sure
we
could
decrease,
but
twice
less
memory.
32
gigabyte
instead
of
64.,
that's
effectively,
half
the
cost
of
the
previous
instances,
so
that
helped
a
lot
we'll
see
if
it's
stay.
That
way.
A
So
that's
why
it
has
been
closed
and
the
Packer
builds
that
was
on
us.
We
shifted
one
month
ago.
The
pattern
we
use
for
the
resource
Group
it's
again
see
that
as
a
namespace
or
a
box
continue
Cloud
resources
and
we
shifted
the
way
we
were
using
them
on
Packer
for
security
purpose,
but
we
didn't
adapt
the
garbage
collector
so
effectively
with
all
the
experiment
and
walk
and
fixes
done
on
the
Packer
image
builds.
A
A
A
They
were
dangling
Archive
of
the
puppet
installation
that
were
staying
on
the
mission.
They
should
have
been
deleted
and
one
gigabyte
per
per
archive
with
three
archives:
duplicated
on
the
root
directory
and
Olivia
Vernon's
repository.
That
was
a
lot
of
gigabytes
used
for
nothing
so
removing
them
and
rotating
the
vacuuming.
The
journal
CTL
was
okay,
so
that's!
Okay,
we
had
ground
commit
permission
that
was
repository
permission
that
data
not
direct
infrastructure
thanks.
Everybody
thanks.
D
A
Cool
having
validation,
issue
and
pull
requests,
new
maintenance
of
a
new
plugin
was
discovering
all
the
tasks
to
do
it.
Nothing
expected
from
the
infrastructure
to
summarize
better
reading
the
dock,
a
login
issue,
not
Factory.
That
seems
like
same
same
kind
of
issue
in
your
main
nerd.
There
is
a
egg
and
chicken
problem
when
you
have
an
account,
never
connected
to
artifactory,
but
that
has
been
solved,
though
certificate
issues
on
the
CI
Joint
inside
your
machine.
We
also
have
a
virtual
host
assets.
A
We
had
the
same
word
issue
I
think
it
was.
Was
it
Becky,
G
Mark,
or
was
it
another
machine
everything
it
was
updated
in
CIO
last
week,
where
the
third
board
system
wasn't
working.
If
we,
the
Chrome
tab,
was
running,
but
it's
in
quiet
mode,
and
we
can
change
that
it's
part
of
the
puppet
module,
so
we
don't
have
a
log
on
what
did
it
fail
or
what
did
it
refuse?
But
it's
been
weeks
since
the
certificate
should
have
been
renewed.
A
That
might
or
might
not
be
consequence
of
the
the
refactor
I
did
in
March
with
the
python
version,
and
there
were
a
lot
of
Tangled
issues,
so
the
certificate
where
we
knew
we
will
have
to
be
careful
in
July.
For
the
renewal
of
this
one
hope
it
will
be
fixed
with
Ubuntu
22204
upgrade,
though
that
will
feature
recent
version
of
third
but
I
hope
we
should
be
able,
with
this
and
recent
puppets
to
have
this
issue
fixed.
A
A
C
A
I
want
to
open
an
issue
to
track
adding
SSL
age
like
this,
because
you
are
watching
or
your
system
Mark
is
watching
this
for
us.
That's
really
useful,
but
I
think
it
will
be
a
nice
team
Improvement
to
move
that
burden
away
from
your
infrastructure,
or
at
least
rely
first
as
first
level
of
of
watching
to
our
data
log
system.
There
is
already
a
datadog
prob
monitoring,
with
alert
on
cigo
that
one
always
each
time
that
there
is
a
security
advisory
on
crjgin
kinsayu
is
put
down,
I,
don't
know.
A
C
I
I,
like
that
I
I,
think
the
detection
of
assets,
dot
Seattle
Jenkins.
That
I
was
more
of
a
happy
accident
from
my
detection
system
than
an
intentional,
because
I
don't
think
that
I
had
ever
enabled
checking
of
assets,
dot,
Sierra,
jenkins.io
I
think
it
was
a
happy
accident
that
the
message
was
inside
another
check
and
that
that
we
we
don't
like
happy
accidents
right.
That's
really
nice
to
have
them,
but
we
don't
like
them
long
term.
A
Makes
sense
thanks
for
that
Mark
everybody.
So
everybody
thanks
for
managing
the
switch
to
melgen
for
sending
emails
of
account,
Jenkins
CI
no
I
could
drink.
A
The
goal
was
for
us,
as
infrastructure
team,
to
have
a
way
to
observe
and
get
a
status
on
the
send
email
for
you,
helping
user
who
said
I
never
received
the
email.
There
are
numerous
cases,
and
but
we
were
blind
before
that
change.
So,
thanks
survey
for
that
Airways
currently
driving
the
melgan
parts,
we
still
have
the
old
accounts
and
grid
by
kosuke,
but
as
far
as
kosuke
chat
with
us
Dash,
there
is
only
one
administrator
at
a
time.
A
D
A
A
A
A
So
back
in
line,
we
had
also
two
issues
closed
with
no
action.
One
was
closed
by
the
requester
basil
about
say
there
was
a
issue
with
the
CD
process
on
one
of
his
projects
inside
the
Jenkins
project,
but
it's
not
the
case
anymore.
Thanks
Brazil
for
cleaning
it
up.
A
A
Okay.
So,
let's
cover
the
work
in
progress
elements
so
element
currently
on
the
Milestone
and
let's
see
if
we
should
keep
working
on
this
element
before
looking
at
the
new
items,
so
can
create
accounts.
Are
they
what's
the
latest
status
of
this
one
I
haven't
checked
since.
D
A
Them
because,
most
of
the
time,
that's
people
don't
want
to
do
that,
for
whatever
reason
we
don't
have
to
care,
I,
don't
know
if
they
don't
like
them
or
if
it's
complicated
topic
or
whatever
the
reason
they
have
to
check
with
their
admin
or
change
the
email
to
be
used.
There
is
nothing
else
we
can
do
about
that,
because
maybe
their
admin
have
blacklisted
the
old
domain
or
IPS
or
I,
don't
know
whatever
so
accept
that
if
they
don't
contact
them,
we
won't
have
anything
to
show
to
the
admin.
A
If
we
go
to
their
admin
ourselves,
that's
why
we
need
at
least
them
to
start
the
discussion,
and
if
they
don't
want
to
contact
them,
then
they
will
use
another.
But
thanks
for
managing
that,
because
it's
not
an
easy
one,
any
question
I
propose
that
we
keep
that
one
on
the
Quran
on
the
new
milestone
and
wait
for
the
feedback.
A
So
it's
okay
for
you
already
yep,
artifact,
caching,
proxies
and
reliable,
so
that
when
we
keep
it
open
because
it's
a
reality,
the
bomb
builds
since
Friday
or
Saturday
are
not
using
digital
lesson
anymore,
neither
for
ACP
neither
for
agents.
A
So
the
the
issues
we
saw
in
digital
Essence
should
be
gone
because
we
weren't
able
to
reproduce
or
to
see
any
case
outside
the
bomb
builds.
That
was
a
certain
threshold
of
requests
that
mean
we
know
there
is
a
limit
on
the
ability
of
our
ICP
system,
at
least
on
digital
ocean.
When
it
starts
to
not
answer
properly,
it
might
be
fixes,
but
if
we
don't
need,
then
let's
keep
things
like
that.
A
A
B
A
We
should
be
able
to
to
check
after
the
meeting.
For
that
part.
I
just
realized
you
can,
you
might
want
to
add
a
private
DNS
with
a
record
for
the
to
the
IP
using
static.
Ap
can
be
complicated
so
better
to
use
a
dynamic
with
a
private
DNS
record.
Okay,
that
shouldn't
block
you
one
should
be
a
viable
solution.
B
D
That's
a
good,
somewhat
working
python
installation,
but
when
I
try
to
install
launchable
I
have
it
doesn't
it
doesn't
success
at
finding
the
setups
tool
with
your.
A
Okay,
so
I
believe
might
need
to
do
a
bit
of
help
on
that
area,
as
we
discussed
this
morning,
yeah
it
per
session
to
unblock,
but
almost
there
cool
thanks
for
the
report.
Anything
to
add.
D
As
soon
as
this
installer
will
be,
good,
I
will
be.
D
D
D
The
part
where
we
can
gain
must
have
separate
time
with
launchable,
so
it's
yeah
as
soon
as
it's
available
as
better.
It
is.
A
That's
a
mix
of
what
Stefan
is
doing
on
trusted
and
what
used
to
be
done
for
the
current
cig
in
kinsayu,
we
have
a
tag
on
the
Azure
project
named
legacctf,
which
was
a
set
of
terraform
code
used
for
most
of
all
the
Azure
resources
that
we
removed
that
but
kept
the
tag,
because
we
can
that
helps
a
lot
when
trying
to
understand
what
resource
is
doing.
What
are
listing
resources.
A
These
plans
might
not
be
up
to
date.
That's
what
I
see
most
of
the
attributes
have
been
changed
and
some
resources
doesn't
exist
anymore,
but
anyway,
mixing
both
of
codes
allows
me
to
have
let's
say
a
proper
code,
so
I've
also
selected
the
new
instance
size
with
a
bit
smaller
than
the
current
one,
because
we
don't
choose
all
of
the
memory
for
CI
Jenkins
IU,
that's
still
40
books
per
month.
It's
not
a
lot,
but
I
mean
we
don't
need
a.
We
don't
need
High
Performance
Machine.
If
it's
not
needed
right
now.
A
The
status
for
me
is
naming
and
I
spent
some
time
carefully.
Reviewing
Stefan
work
to
be
sure,
I,
don't
miss
anything
on
the
new
terraform
provider
for
azure.
A
My
main
challenge
is
that
we
have
different
cases
between
trusted
and
CI
in
the
case
of
CI
join
kinsayu.
That
machine
will
need
two
network
interface,
one
for
Public
Access
through
HTTP
or
inbound
agents,
and
that
will
be
exposed
through
a
public
IP
and
one
private
interface
in
the
public
network
to
be
reached
through
SSH.
A
A
And
that's
one
of
the
points
that
team
yakon
made
on
new
pull
request.
Stephen
I
will
want
him
to
discuss
a
bit
more.
You
want
to
use
the
terraform
module
for
avoid
reusing
for
providing
do
not
repeat
yourself,
but
I.
Don't
see,
I,
don't
see
the
point
if
it's
to
say
oh,
that
will
be
one
if
for
each
case,
one
if
Ci
or
if
trusted
or
if
search
Ci
or,
if
or
the
machine
that
we
don't
have
and.
A
Yeah,
in
that
case,
even
the
argument
of
that
I
might
be
missing.
Something
that's
why
I
want
him
to
to
explain
a
bit
more,
but
I
don't
see
what
to
reuse.
We
have
three
cases.
Each
case
is
acceptably
different.
One
is
fully
private,
but
through
VPN,
so
one
only
interface
for
all
search,
CI
need
two
interfaces
for
two
different
network
and
trusted
is
fully
private,
but
through
SSH
machine
I
mean
that
three
different
cases,
so
we
cannot
put
on
the
module.
A
The
network
interface
We,
cannot
put
the
public
IP
yeah,
eventually,
data
disks,
that's
data
disk
and
the
base
of
a
virtual
machine,
but
the
virtual
machine
don't
have
the
same,
the
same
setup
so
yeah.
If
the
goal
is
to
write
a
10
line
of
map
structure
in
a
local
variable
for
terraform
instead
of
10
line
of
terraform
I,
don't
see
the
point
honestly,
but
there
might
be
other
reason
that
I'm
missing
now
and
we
might
change
in
the
future.
That's
not
a
problem
question
worst
case.
We
factorize.
A
What
do
we
have
migrate
application
from
system
pool
to
Linux
pool
and
private
Gates
Airways
Stefan?
We
we
saw
this
one,
we
have
the
Bots
running
on
the
system
pool,
so
we
need
to
add
Toleration
and
things
and
not
selector.
Eventually.
A
Let's
add
nut
selector
first
and
contained
Toleration
later.
Why
I'm
writing
these
surveys,
because
node
selector
will
help
you
to
to
try
to
create
Affinity
to
run
to
the
Linux
pool,
because
if
we
add
Danes
on
the
system
pool
that
might
have
side
effects
on
the
technical
systems
such
as
core
DNS
or
or
the
cni,
the
CSI
controller,
so
better,
starting
with
node
selector
to
fulfill
this?
A
If
you
don't
mind,
I
will
want
to
take
this
one
for
a
specific
reason:
I,
don't
mind
pairing
with
the
two
of
you
or
just
one
of
you
are
doing
it
alone,
it's
just
because
in
the
Ubuntu
22204
campaigner,
we
have
to
update
the
the
system
pools,
so
I
will
want
to
create
a
new
system,
pools,
migrate,
the
traffic
and
then
bump
and
finally
do
the
update
at
the
ends,
because
since
we
have
to
update
system
pools,
that
will
be
a
way
to
try
a
new
way
to
update
system
boards
too,
with
a
green
blue
deployment
that
will
avoid
any
errors
in
the
future.
A
B
B
A
A
A
Alternatives
are
KK
or
Taylor,
which
aren't
responsive
past
releases
sites
are
taking
long
time
to
load.
If
you
don't
mind,
I
will
postpone
this
one
to
the
Milestone
after
because
we
won't
have
too
much
time
to
pass
on
this.
A
One
and
I
will
want
to
walk
on
the
Ubuntu
before,
because
the
cases
we
have
are
using
Ubuntu
1804
nodes
and
the
driver
on
the
Kernel
of
Ubuntu
is
way
different
for
Samba
CFS
mounts
with
the
new
Ubuntu
222,
so
I
would
rather
upgrade
the
Ubuntu
operating
system
with
the
new
kernels
co-ba
for
the
release
and
the
getjenkins
IU
web
service
and
then
decide
if
we
have
to
switch
to
NFS
base,
PVC
or
other
solution.
A
A
I
will
add
the
message
to
Alex
because
it
might
be
waiting
for
this
one
and
finally,
Airway.
Are
you
still,
okay
to
start
again
planning
the
public
cluster
migration.
A
A
Now
new
items
or
items
on
the
backlog
that
will
want
us
to
to
have
a
look
on
decrease,
AWS
cost
I've,
updated
it.
We
were
able
to
consume
5K
less
than
last
month,
which
is
good,
but
it's
still
too
much
so
did
error
is
continuing
our
effort.
The
the
bill
is
split
Alpha
between
two
regions,
so
the
work
that
Stefan
is
doing
and
the
date
Center
migration
somewhere
else
would
help
on
the
area
on
the
other
area
that
these
are
directly
the
builds
from
cig
and
kinsayo.
A
The
efforts
done
by
Bazil,
Jesse,
team,
Mark
and
and
Irving
on
the
bomb
builds
I
hope
this
efforts
to
pay
on
the
month
of
May
to
decrease
the
billing
here,
I
hope
so
we'll
see
in
the
future.
Right
now
we
are
trying
to
contain
this
cost,
but
we
need
to
move
the
web
services
ports
to
decrease
the
health.
The
bill
by
half
so
Stefan
keep
continuing
on
that
area.
A
There
is
no
immediate
thing
for
us.
We
confirm
that
what
we
did
on
the
past
weeks
was
okay,
garbage
collecting,
decreasing
instant
size.
I,
don't
see
immediate
action
for
us
there.
So
if
it's
okay
for
you
like,
we
keep
that
item
on
the
backlog
and
I
plan
to
close
it.
If
we're
able
to
pass
below
the
threshold.
A
To
bet
a
great
campaign
to
latest7.x,
so
I
started
some
experiments,
and
this
one
will
be
automatically
on
the
new
Milestone.
The
goal
is
to
prepare
updating
puppet
to
puppet
7
I
propose
to
keep
it
on
the
backlog
and
wait
for
Ubuntu
220
to
all
four
companies
that
okay
for
everyone,
as
we
stated
earlier,.
A
A
A
No
problem,
so
the
first
step
you
will
have
is
to
select
which
job
on
infra
CI
could
be
a
good
candidate
for
using
a
ram,
64.
and
then
start
using
it.
Okay,
my
recommendation
is
to
look
at
the
job
using
something
a
tool:
a
set
of
tools,
building
go
so
terraform
or
kubernetes
jobs
could
be
a
good
thing.
Packer
itself
could
be
really
good
to
try.
That
could
be
a
nice
first
step.
I
will.
A
Job
in
info.ci
to
test
with
okay
that
so
adding
to
the
next
Milestone,
then
thank
you.
Renew
Update
Center
certificate
definitively
going
to
the
next
milestone,
because
what
we
said
earlier,
AKG
origin
Jenkins
keeps
updating
the
gpg
that
one
stays
in
the
backlog.
It's
really
annoying
to
be
spawned
by
the
puppet
agent,
but
I
won't
have
time
to
spend
on
this.
One
Ubuntu
2204
campaign
is
not
on
the
backlog
anymore,
as
you're
building
on
CI
Jenkins
ioi
will
keep
it
on
the
Milestone.
A
Just
for
me
to
do
two
things
summarize
the
world
month
of
April
in
terms
of
outbound
bond,
with
cost
day
by
day
to
see
if
we
saw
an
increased
decrease
or
if
it
stayed
same
since
we
enabled
the
S3
artifact
manager
and
what
I
did
just
before
the
meeting
I'm,
adding
a
reminder
once
a
week
for
the
whole
month
to
check
for
cloud
custom
at
least
Azure
and
I
believe
also
in
AWS.
We
can
clearly
improve
with
the
alerting
system
and
everything
but
need
to
check
these
elements
because
they
are
costing
us
a
lot.
A
To
another
Cloud
that
one
will
allow
us
to
work
on
the
AWS
cost
right
now,
delaying
it
of
one
Milestone
I
want
to
focus
on
into
you
in
Azure
first,
so
this
one
stay
on
backlog
use
websocket
for
agent.
If
one
of
you
is
bored,
you
could
start
working
on
that.
The
goal
is
to
enable
websockets
on
the
Apache
server
for
cigen
games,
IO
and
experiment,
whatever
pod
template
experimental
but
template,
you
want
to
use
websocket
instead
of
TCP.
A
You
know
that
you
can
take
it
if
you're
interested
I'm,
not
adding
that
on
the
Milestone,
but
you
can
keep
it
if
you're
bored
one
last
element,
as
per
Mark
last
log
analysis
for
the
g
frog.
We
are
still
consuming
way
more
than
expected.
It's
below
it's
still
way
less
than
the
month
before,
at
least
we're
able
to
gain
10
terabytes,
but
still
there
isn't
any
obvious
way
of
blocking
an
IP
or
doing
something.
A
The
good
news
is
that
so
first
we
expect
to
check
carefully
the
logs
and
by
she
frog
and
see
if
there
are
any
issue
on
the
logs
on
the
way
we
calculate
the
Advent
bandwidth
and
check
with
you
frog.
If
the
current
state
is
okay
for
them
or
not
in
the
event,
if
they
want
us
to
enable
authentication
on
the
non-release
repositories,
I've
successfully
started
the
high
availability,
ldap
instance
on
bare
metal.
A
So
we
are
the
the
rate
at
which
we
change.
The
data
is
not
enough
for
us
to
risk
losing
data.
When
there
is
a
network
partition,
we
are
clearly
far
away
from
the
the
limits
of
this
system,
so
that
will
help
us
a
lot,
especially
with
the
PVC
that
is
slowing
down
the
stop
and
start
of
the
container.
In
that
case,
we
should
we
should
be
able
to
keep
one
PVC
per
instance,
and
we
we
should
be
able
to
operate
the
cluster
without
any
downtime
for
the
ldap.
A
A
Okay,
not
to
pick
so
then
moving
to
the
issue.
Let's
look
under
recent
issues.
We
had
to
find
a
way
for
to
avoid
non-experable
missing
Update
Center
support
Linux
for
running
VM.
So
thanks
James
for
opening
that
issue.
We
had
a
private
discussion
about
there
are.
There
are
at
least
two
projects:
I
think
these
both
are
plugins.
Yes,
two
Jenkins
plugin,
which
build
process
needs
to
run
the
maven
and
Java
command
on
the
Windows
hosts
and
the
required
to
execute
Docker
command
from
that
Windows
host
to
a
Linux
container
enabled
docker.
A
We
don't
have
this
in
the
infrastructure
today,
that's
a
legit
that
legit
requirement
I,
don't
say
we
have
to
work
on
it
now.
The
thing
is
we
are.
There
is
a
discrepancy
today,
most
of
the
developer,
using
a
Windows,
10
or
own
system
with
Docker
desktop
and
Docker
desktop,
is
able
to
switch
from
Windows
container
to
a
Linux
container.
A
The
downside
is
that,
in
our
case,
we
use
only
Windows
Server,
because
we
have
to
work
on
this
on
headless
system
so
yeah.
The
question
I've
tried
to
summarize
the
different
choices
we
have.
None
of
this
choices,
obviously
better
than
the
others,
but
each
one
has
its
Pro
and
cons.
I
will
want
to
hear
feedback
right
now,
with
the
help
of
GC,
we
were
able
to
to
improve
failure.
A
A
We
have
different
solution
that
will
require
adding
a
Windows
11
template
on
Packer
that
could
either
be
next
to
the
existing
or
new
one.
The
problem
is
for
ACI
or
kubernetes
container.
There
is
no
base
OS
container
for
Windows
for
Windows
11.,
so
that
need
to
maintain
both
a
Windows
server
for
container
and
windows
11
for
virtual
machine,
but
that's
quite
the
effort
I
personally
like
the
the
WSL
ID.
A
Maybe
we
could
have
WSL
installed
by
default
on
the
Windows
machine,
and
if
this
plugin
want
to
to
use
local
Linux,
they
could
start
WSL
engine
that
will
provide
Docker
inside
Ubuntu
and
it
should
be
able
to
bind
off.
But
that's
still
a
lot
of
effort,
so
yeah
that
might
need
specific
work
right
now.
D
D
A
A
That
happened
for
one
of
the
most
important
is
people
running
agent
on
Windows
and
they
are
the
used
Docker
Docker
pipeline
workflow
and
they
have
their
Windows
machine
standard
machine
with
the
gvm
running
the
agent,
because
that's
the
way
it
works
with
a
Windows
system,
that's
stored,
inbound
engine
process
and
they
have
a
WSL
Linux
machine
and
you
need
to
test
the
case
of
when
the
agents
runs
on
Windows
machine
and
need
to
start
container
with
a
Linux
case.
A
We
need
to
test
this
element,
especially
for
the
file
path,
conversion
between
both
osis
between
the
container
agent
and
the
host
machine.
These
are
real
use
cases.
We
don't
have
a
lot
and
it's
not
library,
but
we
need
test
for
these
elements.
Uni
test
cannot
allow
that
and
you
need
integration
or
acceptance
test
for
that.
A
These
are
exotic
case.
So
that's
why
that's
a
legit
use
case.
It's
not
priority
because
we
weren't
able
to
run
this
this
test
until
today,
but
still
increasing
the
coverage
on
that
area,
wouldn't
kill.
A
Unless
the
solution
proposed
by
gems-
that's
really
nice
of
him
I
share
with
us
the
switch
demon,
but
that's
a
specific
feature
of
Docker
desktop
and
it's
my
proposal
to
use
the
docker
desktop
on
Windows
11.,
because
of
course
you
cannot
install
it
on
Windows.
Server
would
have
been
too
easy,
then
otherwise.
D
B
A
A
A
Yes,
oh
yeah,
yeah
good
point
good
point:
is
that
later,
just
a
point,
keep
in
mind
that
it's
interactive
versus
non-interactive,
so
what
you
can
do
interactively?
We
are
not
skilled
enough
on
the
Windows
area
to
easily
make
it
non-interactive
like
we
do
on
Linux,
so
that
that's
I
spent
some
time
last
months.
You
are
you
spend
some
time
on
launchable
ports,
so
Docker
rest
stop
is
another
order
of
magnitude
in
terms
of
complexity
but
yeah.
If
it
work.
Please
add
a
comment
on
the
issue,
because
we
could
then
try
something
with
this.
A
Thanks
for
the
feedback
array,
I'm,
removing
the
triage
and
I'm,
adding
that
to
the
infatim
sync
next,
next
one
find
a
way
to
avoid
non-experiable
access
for
the
update
Center
certificates.
For
that
one,
oh
just
a
minute.
A
Sorry
so
there
there's
been
a
misunderstanding
that
they
took
that
we
had
to
share
the
the
key
for
the
certificate
for
10
years,
but
it's
a
certificate
Authority.
A
However,
most
of
this
pain
of
his
points
remain,
and
you
want
to
start
the
discussion
about
what
would
be
the
threat
model
that
led
to
a
10-year
valid
CA
to
validate
on
Jenkins
score
site,
the
metadata
from
the
update
center
with
a
one
year
or
six
month,
rotated
certificate
for
a
plate.
Center
there
might
be
other
solution
that
could
be
valid
or
invalid,
but
the
goal
is
to
reassess
the
threat
model
to
validate
or
change
how
it's
implemented
inside
junkies
itself.
A
So
no
action
expected
from
us
here,
except
the
keep,
keep
the
description
ongoing
that
might
switch
to
a
GE
speed.
That's
why
I'm
removing
the
triage,
but
no
action
expected
from
us.
So
no
Milestone
here
looks
good
for
you.
A
And
the
third
triage
issue,
I'm
not
sure
to
understand
everything
here.
I
will
assign
this
one
to
mark
I,
understand
that
we
have
spare
distribution
line,
Mainline
version
Update
Center
file
created
when
the
update
Center
generates
its
index,
and
when
we
have
plugin
released
under
a
new
LTS
version
that
one
is
created,
it's
not
created
when
the
version,
the
core
version
is
released.
A
It's
created
after
a
given
release,
weekly
or
LTS
of
the
core
when
a
new
plugin
is
released,
that
new
plugin
is
the
first
to
say
a
I've
been
released
under
that
maximum
version
of
Jenkins
that
explain
the
discrepancy
that
Alex
cooked
on
the
update,
Center
files,
so
as
per
Mark,
there
is
no
action
expected
here
for
us.
I
will
remove
the
triage
and
assign
that
to
Mark
and
I,
just
want
Mark
to
be
sure
that
it's
okay
and
there
isn't
something
hidden
behind
for
us.
A
D
B
A
A
You
want
to
enhance
your
programming
skills.
Yes,
then
Airways
tip
is
the
best
because
yeah
we
don't
code
a
lot
of
java,
that's
infrastructure
layer
that
what
we
do
so,
if
it's
okay
for
you
I
will
I
would
yeah
follow
whatever
Side
open
topic
on
community
Jenkins
IO.
You
will
have
plenty
of
mentors
here
that
will
help
you
on
the
job
area,
for
specific
programming
skills.
A
A
A
A
Okay,
I'm
gonna
stop
sharing
my
screen
cool,
so
you
did
write
to
ask
the
question:
vignan,
that's
a
good
way
to
start
the
first
step
so
welcome
to
the
community.
I
hope
you
will
find
what
you
expect
and
see.
You
see
you
on
the
upcoming
days
or
month
for
everyone.
I'm
gonna,
stop
recording!
So
for
everyone
watching
us
see
you
next
week,
bye.