►
From YouTube: 2022 08 09 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
B
Hi,
hello,
everyone
welcome
to
the
jenkins
infrastructure
weekly
team
meeting.
We
are
today
at
the
2nd
of
august
2022.
B
We
are
for
now
two
attendees
mark
waite
and
myself
stephan
murr.
For
today
it's
a
very
short.
It
should
be
a
very
short
meeting
as
it's
holidays
here
and
most
of
the
team
is
on
holidays
for
the
announcement.
B
We
are
the
today's
weekly
woo
2.362
2.,
sorry,
which
have
been
released
and
the
checklist
have
been
completed.
If
I
read
correctly
what
mark
just
wrote
down
last
week
on
the
27th
of
july,
we
had
a
security
release
that
dealt
with
a
few
advisory.
You
got
the
link
in
the
shared
knot.
B
Can
you
can
you
copy
and
paste
the
the
link
in
the
little
box
in
the
zoom
meeting,
but
we
are
the
only
two,
so
it's
not
really
useful.
We
got
a
little
discussion
about
the
caa
enforcement
for
the
certification
that
we
will
postpone
for
the
discussion
for
next
week.
It's
not
a
security
issue
per
se,
more
good
to
have,
I
think
it's
all
we
got
here
for
the
announcement.
B
As
I
told
you,
damien
is
on
holidays
until
wednesday
included,
so
until
thursday
rv
is
out
until
next
monday,
and
I
will
be
out
for
two
weeks
beginning
next
week,
so
the
bandwidth
is
quite
limited
for
the
for
the
task
that
we
got.
B
I
think
the
the
next
lts
baseline
was
not
secured
last
week.
It's
it's
now
selected.
I
think
so
it
will
be
2.361.,
oh
no
see.
Yes,
of
course
you
got
the
link
for
all
the
discussion
on
the
google
group
for
that
upcoming
calendar.
The
next
weekly
so
will
be
next
week
and
should
be
the
two
three
six
three
and
we
will
be
the
ninth
of
august,
the
next
lts.
A
B
B
Sorry
milestone
up
the
current
milestone
had
nothing
closed,
so
we
did
some
work,
but
it's
not
within
the
the
milestone
for
myself.
I
did
work
a
little
on
the
migration
for
update
at
jenkins.io,
mostly
working
on
puppet
stuff,
and
I
using
installation
but
nothing
too
risky.
B
As
I
was
alone
fatigue,
we
got.
We
had
a
lot
of
pedro
duty
and
datadog
alert
for
weird
time.
Loading
time
with
we
did
avoid
that
specific
alert
until
the
end
of
august.
I
also
prepare
a
pull
request
to
erase
the
page
of
duty
from
that
monitoring.
B
B
We
discovered
that
the
updates
of
the
packaging
docker
packaging
was
not
pushed
everywhere,
so
I
did
prepare
an
update,
manifest
to
take
care
of
that.
It's
ready
and
working.
We
will
just
have
to
merge
and
validate
the
docker
packaging
upgrade
through
through
update
by
merging
those
peers.
So
it's
almost
done
sorry.
B
We
are
here,
oh
for
this
issue.
It's
for
you
mark
the
replacement
of
s
390
ubuntu.
A
Yeah-
and
I
it's
still
on
my
list
I'll-
I
hope
to
get
to
it
this
week.
B
If
you,
if
you're
okay,
with
that,
when
we're
done
checking
all
the
issue,
I
will
move
them
all
to
the
next
milestone.
It's
easier.
Yes,
then
in
fallout
mention
has
expired
in
the
datadog
ap.
I
think
rv
did
some
work
on
that.
B
B
Yes,
that's
from
last
time
and
that's
still
a
an
ongoing
thing
here.
I
know
that
talk
with
tom
about
that
they're
working
on
that
and
they
try
terms
and
they
try
to
get
back
the
npm
namespace.
B
B
B
Boom
here
great
and
then
working
progress,
so
it's
done
and
new
and
important.
We
got
word
that
we
had
last
week
so
nothing
new.