►
From YouTube: 2022 03 08 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
B
B
A
Maybe
it
will
be,
can
the
fourth
make
the
effort
for
the
next
lts
in
six
eight
weeks?
I
don't
remember
exactly
four
or
weeks.
B
A
Are
there
other
announcements,
then
so
that
lts
announcement
says
tomorrow
until
the
lts
is
released,
we
don't
deploy
on
in
production,
at
least
not
something
on
the
pod
public
gate
cluster
great.
As
far
as
I
know,
and
we
don't
deploy
something
on
pup
as
well,
because
that
could
impact
trusted
ci,
which
wouldn't
be
able
to
release
the
docker
images,
because
right
now
this
is
the
instance
in
charge.
A
A
Usually
there
is
that
big
zoom
meeting
on
the
end
of
afternoon
in
europe
for
us,
where
that
we
have
sometimes
someone
from
security
team
someone
not
but
having
someone
for
infrastructure,
is
always
a
peace
of
mind
for
the
person
in
charge
of
the
release,
because
we
are
there
if
something
goes
wrong,
so
you
don't
have
to
be
available
non-stop.
But
if
you
want
to
shadow,
if
you
are
interested
in
discovering
it's
open,
just
let
me
know,
but
it's
not
mandatory.
Okay.
A
Okay,
let's
start
with
the
notes,
unless
there
is
something
else,
one
two,
three,
okay,
you
had
the
proposal,
or
at
least
a
draft
of
proposal,
to
help
us
having
better
actionables
for
that
meeting.
Could
you
explain
that
at
least
to
mark
that
wasn't
there
yesterday,
when
we
shared
that.
C
A
C
C
So
I
think
it
can
be
a
good
way
to
gather
the
different
issue
or
subject.
We
are
currently
focusing
on
or
want
to
speak
about
in
this
meeting.
Not
so
I
started
with
this
week
this
week
with
this
milestone
and
now
when
I'm,
when
we
are
working
on
an
issue,
I'm
adding
it
to
this
milestone,
and
I
have
also
added
it
to
the
milestone
through.
B
B
D
C
A
C
Sorry
for
that,
much
more
to
add
it's
limited,
as
we
can
only
link
issue
from
one
repository
at
once.
We
can't
link
issue
or
pull
request
from
other
repository,
so
it's
implied
to
create
an
issue
in
eblask
you
if
we
want
to
track
it
that
way,
it's
not
monetary
but.
A
I
would
argue
that
it,
it
would
be
a
good
thing
to
create
one
health
desk
issue
for
top
level
items,
because
it
allows
us
to
share
the
state
of
our
work.
Not
only
we
have
the
new
triage,
but
we
will
have
the
top
level
items
that
we
do
and
then
we
can
link
to
other
issues
that
could
be
in
the
form
of
migrating
an
existing
issue
on
one
of
our
repositories,
moving
it
to
help
desk.
C
A
C
Their
link,
it
can
break
selling.
A
C
Separating
the
full
script
of
and
for
report
was
an
issue
in
the
in
the
employee
part
repository
and
you
created
another
one
in
helpdesk.
I've
added
on
class
wanna
link
to
the
employee
part
one.
A
That
we
create
one
issue
on
lds
per
top
level.
Okay,
just
to
be
sure,
I
understood
correctly,
the
milestone
that
is
existing
today.
The
slash
free
was
for
the
week
that,
for
the
iteration
that
ends
with
that
meeting,
is
that
correct
or.
B
A
Okay,
if
it's
okay,
so
I'm
creating
one
now,
just
to
be
sure
that
I
understand
the
goal
by
creating
a
new
one
is
to
support
to
that.
We
have
all
we
add
all
the
topics
we
need
either
not
done
from
last
week
or
new
topics,
and
we
add
them
right
now.
That
will
be
a
complementary
to
the
meeting.
Notes
sounds
good
for
you.
C
C
A
A
So,
first
of
all,
I
would
like
to
check
on
the
previous
milestone
the
work
that
has
been
done
by
the
team.
I
might
have
forgotten
to
add
some
issues,
but
these
one
two,
three
four
five
top
level
items
should
be
what
we
did
or
finished
during
the
previous.
So
that's
the
first
step
of
what
did
we
do
so
we
can
see
our
progress
altogether.
C
I'm
not
sure,
but
you
spoke
about
passing
this
issue
from
one
milestone
to
one
one
other.
C
What
did
we
yeah?
I've
put
them
in
the
notes,
so
I
don't
I'm
not
sure
it's
a
good,
I'm
not
sure
it's
a
way
to
list
and
review
the
issue.
We've
done.
I
I'm
I
don't
know
for
this
week.
I've
put
all
this
issue
in
this
in.
A
C
D
D
C
C
C
Later
but
right
now
I
was
I
didn't
plan
to,
and
I
tried
to
explain
what
I
thought
but
yeah.
I
didn't
think
about
any
everything
like
you
were.
You
wanted
to
look
at
this
list
right
now.
I
didn't
plan
you
where
you
will
have
put
this
on
the
meeting,
so
I
can
yeah.
I
prefer
what
I
have
to
prepare
and
it's
not
complete
yeah
okay,
but
I
didn't.
C
A
A
A
Fixed,
it's
not
a
weekly
issue
at
the
moment
on
time.
Two
weeks
ago,
one
of
the
plugins
on
the
plugin
suit
changed
the
behavior
of
the
pipeline
when
a
pipeline
defined
a
trigger
a
collection
of
triggers,
and
it
called
a
library
that
also
redefined
the
triggers
before
both
were
merged.
Now,
the
second
overrides,
the
first
and
one
of
our
library,
the
one
we
used
for
update
cli,
had
a
wrong
logic.
That
was,
if
you
provide
that
attribute
with
a
contributor
expression,
then
define
the
new
crown
trigger
otherwise
empty
list.
A
A
Technically
speaking,
so
now
we
understand
what
happened
technically,
we
have
a
short-term
fix
that
allowed
the
kubernetes
management
to
run
as
it
was
during
the
past
year
since
a
few
days,
so
that
part
is
fixed
and
we
can
operate
again
at
full
speed
medium
term
is:
there
is
a
pull
request
that
has
been
merged
one
hour
ago
on
the
pipeline
library
that
takes
care
of
trying
not
to
merge
just
in
case
we
still
have
one
other
jobs
without
the
hack
long-term
proposal
from
rv
to
migrate,
all
the
update,
cli
pipelines
on
their
own
multi-branch
projects,
eventually
using
a
marker
file,
and
we
define
one
pipeline
that
will
have
the
same
behavior
for
everyone
run
once
per
day
or
eventually,
once
weekly.
A
A
Yeah,
that's,
let's
say
user
experience
with
pipeline.
That's
that's
another
topic
outside
our
scope
as
your
portal
management.
So
with
the
changes
we
did
last
week
about
the
enforcing
mfa
for
everyone
on
azure
team
underline
that
there
is
a
one
click
button.
There
is
one
setting
somewhere.
So
we
could
try
next
week
that
topic
now
that
we
know
everyone
is
able,
and
but
the
thing
is
we
have
specific
settings
that
was
trying
to
enforce
certain
security
settings
that
are
defined.
A
A
Okay,
nginx
and
ingress
cert
manager
upgrade
done
this
morning.
A
A
We
had
the
status,
you
can
say
updated
this
morning,
one
hour
before
starting
the
operation
and
update
it
at
noon.
I
don't
have
anything
else,
that's
a
regular
operation
and
it
worked.
A
Yes,
based
on
the
change
log,
there
were
some
change
on
the
way
set
manager
used,
http
01
challenges,
but
we
are
not
using
http
01
challenge
on
kubernetes
manager,
so
I
thought
that
one
could
be
sensitive
but
seems
like
it's:
okay,
we
might
have
to
monitor
in
the
upcoming
weeks
the
certificate
renewal,
but
all
the
services
on
kubernetes
are
monitored,
so
we
should
have
alerts.
A
There
should
not
be
bad
surprise,
however,
that
one
isn't
me
grafenapod
was
stuck
in
three
days
and
by
talking
we
had
a
credential
that
was
not
expired
but
deleted
from
azure,
so
the
worker
nodes
on
pod
publicates
weren't
able
to
mount
volumes
because
they
didn't
have
the
service
principle
to
authenticate
against.
As
your
api,
I
was
a
bit
too
much
aggressive
on
cleaning
up
the
dead
service
principles
last
week
that
one
was
one
that
was
noted,
so
we
have
to
be
careful.
A
It
was
one
of
the
without
at
least
two
two
years
without
any
activity.
Well,
it
was,
it
was
active.
I
don't
know
why.
So
we
will
have
to
check
next
time,
so
we
only
created
one.
There
is
the
full
procedure
and
we
added
the
expiration
of
that
token
on
the
calendar,
because
the
current
one
was
due
to
expire
in
two
weeks.
A
C
C
B
C
C
I
was
in
the
process
of
creating
a
shared
pipeline
to
get
this
kind
of
access
token,
but
tim
mentioned
this
a
way
to
doing
it,
which
is
already
integrated
in
the
github
clone
and
sharpening
so
good
news,
and
we
will
be
able
to
replace
the
credentials
used
in
several
places
like
updately
or
the
repository
of
structure
parts
of
this
same
repository
by
by
this
mechanism
to
get
an
access
token
from
the
github
app
so
we'll
be
able
to
decommission
commission.
A
A
So
that's
also
an
important
topic
not
only
for
us
to
avoid
user
as
every
side,
but
also
thinking
about
the
cd
for
the
plugins,
because
that
one
one
of
the
reasons
why
github
action
is
used
for
the
cd
it's,
because
the
that
credential
was
problematic
for
the
automatic
part
in
charge
of
pushing
the
artifact.
Oh
sorry,
the
automatic
parts
are
in
charge
of
creating
the
releases
inside
github
because
you
need
to
use
the
github
api
for
that,
but
at
least
for
us,
that's
a
very
nice
one.
A
C
There
is
two
subtasks
two
two
different
tasks
only
for
report
to
do
separating
the
pipeline
running
the
four
scripts
at
once
in
four
different
pipeline.
C
This
work
will
be
beneficial
for
separating
all
main
work
hormonal
pipeline,
doing
the
main
work,
and
also
the
maintenance
tasks
like
objectively
manifest
and
so
on.
So
we'll
be
able
to
separate
these
in.
B
C
C
C
A
Nope
a
word
about
g
frog
incident
so
friday
we
started
to
eat
the
infamous
space
left
on
device
on
the
g-frog
managed
instance,
under
sas
system,
danielle
gavin
fighted,
with
that
daniel
was
able
to
purge
some
cash
at
least
a
hundred
of
gigabytes
that
allowed
the
service
to
be
back
again.
A
The
exchange
with
g
frog
was
delayed,
but
we
had
useful
information
on
where
we
can
check
the
size
of
each
of
our
repositories
for
information.
Daniel
has
started
to
apply
some
new
rules
because
when
that
instance,
one
of
the
repositories
inside
inside
that
instance
is
used
as
caching.
So,
as
you
know,
some
developer
might
complain
that
their
local
maven
builds
clean,
whatever
doesn't
work
as
expected.
In
that
case
they
have
to
fix
the
maven
configuration
so
that
only
certain
artifact
id
and
group
id
are
used
and
cached
inside
a
repository.
A
Only
the
one
from
jenkins
ci,
because
there
are
some
binaries
not
related
to
the
project,
but
there
are
transitive
dependencies
of
this
developer
or
wars
from
another
project,
the
that
they
own
on
the
machine
that
are
consuming
a
lot
of
things
another
not
for
us
on
infrastructure.
When
there
is
a
deletion
of
artifact
on
their
service,
they
have
a.
They
have
a
garbage
collecting
system
that
runs
every
two
hours
or
four
hours.
I
don't
remember,
and
it
has
to
run
at
least
six
times
before
the
full
garbage
garbage
collect.
A
A
So
we
have
some
cleanup
to
do
thanks
daniel
for
the
work
you
did,
that
that
was
an
opportunity
to
add
a
gave
in
on
the
list
of
persons
that
are
able
to
merge
and
status
jenkins.
I
o
because
thanksgiving
for
also
pre
sending
information
to
the
user
in
that
area,
and
also
we
are
waiting
for
g
frog
for
two
topics.
Now
the
four
of
us
and
also
team,
gavin
and
danielle
and
vadek,
should
be
now
allowed
to
open
issue
by
email
to
chief
rock
support,
not
only
mark
and
high.
A
They
should
be
recognized
because
gavin
sent
them
an
email
and
wasn't
recognized
so
they
weren't
able
to
discover
which,
which
instance,
what
is
the
dns
and
their
world
support
standard
process.
Second,
we
are
waiting
for
them
to
check
what
is
the
file
system
limit
and
to
check
if
they
can
increase
it
at
least
adding
one
terabyte
more.
We
are
at
5.6
setting,
one
should
be
okay,
given
the
cleanup
procedure,
we
are
also
doing
on
our
side
since
monday.
The
deployment
and
release
are
okay
again,
but,
as
jesse
glick
noted
yesterday,
the
service
was
slow.
A
We
didn't
hear
anything
from
g
frog
on
that
area.
That
could
be
either
the
file
system
when
a
file
system
is
more
than
eighty
percent.
Most
of
the
time
the
wall
blocks
device
is
going
really
slow,
but
that's
also
another
coin
in
the
machine
of
we
might
want
to
have
a
caching
proxy
on
our
infrastructure,
we're
using
what
was
done
two
or
three
years
ago,
because
that
kind
of
issue
will
be
completely
hidden
because
we
will
use
our
cache
instead.
A
C
Yes,
the
original
security
issue
was
worried.
Anyone
could
purge
cash
for
jenkins
data
or
plug-in
site
data,
but
it's
not
the
entire
seat
website,
which
is
purge.
It's
only
the
individual
url
so.
C
C
C
So
we
yeah
are
we
I'm,
I'm
not
sure
we
should
restrict
see
individual.
Your
helpers.
A
Okay,
are
you
okay
to
to
ask
one
more
time
on
the
security
private
issue,
but
both
vadek
and
daniel
daniel
has
the
requester
and
medic
as
the
security
officer
just
give
them
back
that
context
again
and
tell
them
okay,
we
want
to
rework
that
because
it's
causing
issues,
let's
say
operability
issues
for
team
gavin,
you
I
stephan
and
ask
them
their
advice
and
then,
depending
on
their
answer,
we
keep
the
current
restricted
process
and,
sadly,
for
for
team
and
giving
request
or
we
can
roll
back
and
everyone
sounds
good
to
you.
A
A
That's
a
github
action.
If
I
understand
correctly
that
run
when
someone
opened
an
elbasque
issue
that
holding
the
user
to
similar
issues
based
on
a
text,
research
algorithm,
the
idea
is
to
try
it's
not
definitive
as
always,
but
we
hope
that
it
could
be
useful
to
an
user
to
find
topics
that
should
be
the
same.
With
the
same
answer.
A
Stefan
on
your
own,
could
you
just
give
us
a
break
breaker?
Sorry,
I
need
a
break.
Could
you
give
us?
Could
you
share
the
status
of
your
main
tasks?
I
remember
that
you
opened
an
issue
on
update
cli
to
allow
us
I'm.
E
Sorry
it's
written
on
that
document,
but
it's
completely
below
I
didn't
mix
up
with
the
presentation,
but
yes,
I
tried
to
change
a
little
updately
for
for
it
to
be
more
useful
for
us
to
handle
a
matching
pattern
in
reg
apps
and
to
use
it
for
our
updating
process
and
checking
if,
if
some
security
groups
have
changed,
for
example-
and
I
did,
I
did
submit
the
pull
request,
I
also
did
the
submit
to
pull
requests
for
the
documentation
I
may
have
to.
E
Show
and
and
change
a
little
some
some
information
like
the
different
info
value
of
the
the
optional
parameters,
but
I
think
it
have
been
merged.
A
For
release,
so
your
design
volunteer
to
track
the
update
click.
Once
it's
released,
update
clear
update
on
our
docker
images,
so
you
can
use
it.
Can
you
remind
us
what
what
is
the
high
level
task?
What
what
are
we
doing
this
for.
E
E
And
that's
the
first
one,
the
the
second
one.
I
got
two
issues
that
need
that
particular
behavior
from
abducly.
The
second
one
is
depending
on
something
that
irve
did.
If
I
remember
correctly,
it's
probably
because
of
digitalocean
or
something
I'm
sorry.
I
didn't
want
my
main
goal
for
that.
E
A
Seen
it
yeah
but
yeah
we
are
on
given
minute
past
the
end
of
the
meeting,
so
I'm
gonna
stop
recording
and
the
delayed
issue
will
be
delayed
once
more.