►
From YouTube: 2021 11 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
We
will
have
a
new
lts
upgrade
this
thursday
for
november,
so
please
restrain
merging
and
deploying
changes
at
least
the
tuesday
the
thursday
morning
on
the
us.
Ideally,
we
should
also
avoid
wednesday,
but
yeah
we
never
know
that's.
Lts
release
would
also
be
synchronized
with
a
weekly
release,
of
course,
with
the
security
fixes
involved.
A
C
C
B
On
sunday,
the
deadline
to
restart
for
the
election
is
on
sunday
and
next
monday
I'll,
send
invitation
to
vote
and
will
communicate
about
the
candidates.
A
Still
announcement
thanks
cool
okay,
so
we
can
start
by
the
elements.
Unless
someone
has
the
last
announcement,
one
two,
three
okay,
so
note.
First,
we
discovered
not
sure
if
it's
something
that
we
used
to
have,
because
I
remember
we
have
seen
that
behavior
before,
but
when
the
release
team
is
working
on
security
a
few
days
ago
and
when
they
disabled
a
weekly
job
or
any
multi-branch
job
on
release
ci
on
infrasi,
we
have
a
job
that
regularly
apply
the
configuration
as
code
and
so
each
time
the
configuration
as
code
and
job
dsl
setup
is
reapplied.
A
I
was
not
able
on
during
the
past
15
minutes.
So
let's
say
if
you
know
how
to
do
that
or
if
you
are
better
at
searching
documentation
on
understanding
job
dsl
than
me.
Please
let
us
know,
but
it
seems
like
that.
It's
not
possible
to
disable
multibrand
job
or
github
organization.
Through
a
directive
on
job
dsl.
A
There
is
a
directive,
a
function
disabled
on
the
freestyle,
maven
and
simple
pipeline
job.
But
I
I
didn't
find
an
obvious
one
for
multi
branch,
which
means
it
changes
the
state
of
the
job.
But
it's
not
exposed
as
a
configuration
item.
So
we
must
use
it
use
the
ui,
which
is
quite
annoying
because
I
had
to
disable
the
kubernetes
management
job
for
now
and
it
should
be
disabled
until
thursday,
because
it's
trying
to
run
again
new
releases.
A
C
A
It
seems
that
daniel
told
me
that
it
should
be
okay.
There
should
be
there
shouldn't
be
a
new
one,
so
I
assume
that
the
script
is
already
once
you
have
built
something
it
won't
be
lit
again
or
I
don't
know,
but
there
is
something
there.
That's
that
should
be
his
but
yeah
that
that's
a
good
idea
or
and
maybe
use
it
here
until
we
are
able,
with
job
dsl
to
disable
it.
A
I
had
a
message
from
jenkins
contributor
that
told
me
that
maybe
it's
only
not
implemented
on
top
dsl,
so
that
should
be
a
contribution
to
do,
because
there
is,
since
multibranch
pipeline
are
inheriting
from
the
standard
job
structure
that
should
be
easy
to
reuse.
The
disable
is
just
not
exposed
and
it's
already
changing
the
state
on
jenkins
instances.
So
there
is
already
some
code
that's
at
play
there,
so
maybe
something
to
check
but
be
careful.
A
When
you
apply
changes
on
the
charts
repository,
they
might
be
skipped
unless
we
are
carefully
enabling
the
job
running
your
changes,
merge
on
the
master
branch,
disable
the
job
and
ensure
that
you
disable
the
weekly
job
as
well.
So
please
communicate.
If
you
want
to
do
that
prior
to
your
change,
so
we
can
ensure
that
we
don't
slow
down
the
security.
B
And
and
what
about
just
commenting
the
the
part
and
jenkins
infrastructure
repository
that
configure
release
at
ci?
So
we
are
sure
that
we
don't
modify
that
configuration
so.
B
A
B
A
A
Yeah,
that's
the
time
fix
okay,
who
is
willing
to
pull
request
that
one?
That's
an
easy
one!.
A
A
A
Okay,
so,
with
the
two
temporary
fixes
that
tim
and
olivia
proposed,
we
should
be
able
to
be
safe
to
work,
continue,
walking
and
ensure
that
next
security
release
should
be
okay,
I'll,
take
care
of
communicating
that
to
the
security
team.
If
it's
okay
for
you
once,
we
will
have
implemented
at
least
the
first
one.
B
A
Me
so
I'm
moving
to
the
next
item
plug-in
site.
Last
week
we
were
having
a
dns
issue
during
the
past
team
meeting,
so
that
issue
has
been
solved
by
switching
from
alpine
to
debian
base.
It's
not
because
alpine
is
buggy.
It's
because
the
the
base
docker
image
used
for
the
back
end
of
the
plugin
site
is
the
official
jetty
and
they
dropped
support
of
alpine
since
two
years.
So
that
was
a
really
a
really
hard
alpine
image.
A
Not
it
was,
it
was
only
dns
and
absolutely
not
dns
sex.
So
no,
no
way
it
was
with.
Let's
encrypt
that
was
the
the
symptoms
were
some
randomly.
Some
domains
were
not
receiving
dns
answer,
while
checking
the
logs
of
core
dns
on
the
cluster.
You
saw
the
request
piling
up
on
the
core
dns
agent,
on
the
walker
where
the
pod
was
running.
That
was,
that
is
a
characteristic
of
an
old
alpine
version,
not
able
to
deal
with
the
dns
system
inside
cube.
A
That
was
alpine
3.9,
it's
really
hard,
and
so
the
the
logs
of
the
application
were
saying.
Oh,
I
cannot
resolve
ci
the
jenkins
dota.
U,
it
was
able
to
resolve
other
sub-domains
of
jenkins
io,
but
not
randomly
ci
jenkins,
and
if
you
restart
the
pod
that
might
switch
to
another
domain
randomly
which
is
the
which
is
a
smell
that
okay,
you,
you
have
an
issue
at
low
level.
Dns
there.
A
D
Is
there
a
general
way
that
we
can
check
for
outdated
images
like
that
as
they
arrive
in
the
cluster
or
as
they're
running
in
the
cluster?
Or
is
it
not
a
not
I'm
just
thinking
in
terms
of
the
health
and
the
monitoring?
Is
it
something
worth
considering
looking
at?
What's
the
base
os
version
or
that
kind
of
thing.
B
I
think
I
think
you
need
a
security
tool
that
would
analyze
based
images,
because
in
our
case
we
don't
know,
I
mean
that's
the
same
with
the
jenkins,
the
official
junkies.
I
mean
the
official
jenkins
image
if
you
run
docker
full
jenkins,
you'll
get
a
very
old
champion's
version,
and
not
I
mean,
unless
you
use
a
security
tool
to
tell
you
that
it's
an
old
version
or
if
you
know
the
context
of
the
docker
image
that
that
helps.
But
in
this
case
it's
really
hard
to.
C
A
A
B
Yes,
like
yeah,
if
someone
is
interested
to
contribute
on
that
domain,
improving
the
security
of
our
infrastructure
is
definitely
one
of
those
domain
where
we
need
help,
because
we
don't
necessarily
have
the
time
to
work
on
those.
B
Thank
you
just
for
the
context.
I
think,
with
the
work
that
the
linux
foundation
is
doing
with
at
fixer
creative
v2,
we
may
we
may
be
able
to
detect
that
kind
of
issues,
I'm
not
sure,
but
I
think
I
think
there
are
they
can
analyze
the
code
file
from
each
repositories.
A
A
That
yeah,
that's
all
for
me
on
that
topic,
something
else.
A
Okay,
let's
go
ahead,
just
a
note
on
the
aws
costs,
which
is
the
one
of
the
main
priority
of
these
times.
We
started
some
work
on
using
spot
instances
on
ec2
that
the
experiment
worked
really
well.
We
were
able
to
cut
costs
during
the
experiment
pair,
which
is
really
impressive,
and
there
is
a
lot
of
features
that
are
not
documented
on
the
plugin
on
the
ec2
plugin
for
jenkins,
so
incoming
pull
requests
and
the
final
configuration
is
gonna.
The
pull
request
for
applying
that
on
long
term
on
our
instance
is,
is
coming.
A
Next
step
will
be
to
do
the
same
with
the
ks
cluster,
with
the
walk
pool
and
ice.
I
cooked
that
the
azure
vm
plugins
also
has
directive
around
spot
instances
on
azure
as
well,
so
that
might
be
worth
it
to
enable
but
haven't
checked.
I
don't
know
if
team
or
someone
else
have
already
played
with
that.
C
D
C
Yeah,
so
basically
they
should
you
shouldn't,
lose
out
on
anything
because
so
yeah
we're
bidding
at
the
mac
but
being
at
the
regular
price,
but
we'll
take
anything
less
than
that.
So
you
should.
You
should
always
get
something
and
and.
D
If
we
get
evicted
damien
will
we
see
that,
as
as
build
failures,
I
mean
we
get
some
60-second
notice
or
something
like
that,
we're
about
to
be
evicted,
but
that
won't
be
long
enough
to
finish
most
jenkins
plug-in
builds.
So
I.
A
Assume
so
now
the
build
will
fail,
because
the
agent
will
receive
so
jenkins
will
be
aware,
and
will
note
on
the
agent
logs
that
it
has
been
evicted.
So
I
assume
that
the
bill
failure
should
be
able
to
tell
us
that,
at
least
for
ec2,
however,
jesse
glick
recently
stated
that
there
will
there
could
be
an
improvement.
A
I
saw
your
he
mentioned
an
issue
on
the
public
tracker
about
being
able
to
retry
builds
when
the
cause
was
when
the
cause
of
the
failure
was
the
agent
died
or
was
evicted
or
whatever
depend
on
the
implementation.
C
A
C
A
Everything
so
that
means
we
might
see
some
build.
Failure
on
that
part.
Most
of
the
build
on
ci
jian
can
say
you
have
a
retry
will
be
retried
quite
often.
So,
even
if
it's
annoying
like
for
adath,
that
might
be
an
issue
we
have
to
see
in
reality.
The
strategy
I
proposed
there
is
to
bid
a
bit
a
bit
more
than
the
current
price
like
right
now
for
imem
instance.
It
has
been
0.16
for
the
hour
in
dollars,
so
bidding
at
0.20,
which
has
never
been
reached.
A
You
are
sure
that
you
always
have
machine,
because
right
now
the
thing
is,
if
you
bid
a
bit
more
on
ec2,
they
are
automatically
putting
you
on
what
they
they
call
spots
block
where
you
say
I
want
a
spot
price
grant
and
usage
grantee
for
one
hour
or
two
hours
or
six
hours
that
behavior
has
been
deprecated.
A
It's
still
it's
still
working
until
next
year
for
the
customer,
using
it.
The.
What
I
understood
from
the
ec2
support
is
that
if
you
bid
a
bit
more
expensive
than
the
price
market,
then
you
will,
you
won't
be
evicted
because
they
assume
that
will
be
a
six
hour
block
by
default
for
now.
So
we
should
benefit
from
this
behavior
until
next
summer,
based
on
what
the
the
what
they
wrote
on
the
support.
A
However,
the
risk
is
not
zero
and
we
might
see
some
bills,
so
we
have
to
be
careful
and
do
you
I
mean
do
we
have.
B
A
way
to
detect
such
eviction
I
mean:
do
we
have
a
way
to
measure
if
just
improving
or
decreasing
the
situation,
because,
as
far
as
I
know,
we
remove
the
datadog
agent.
So
we
don't
and
we
discussed
we
discussed
about
having
working
with
elastic,
to
have
the
open,
telemetry
plug-in
in
place,
but
we
have
not
so
maybe
would
be
nice
to.
A
A
We
communicate
to
the
developer
mailing
list
that
we
did
that
change
and
we
communicate
to
the
end
user
to
the
developer
that
okay,
if
you
see
build
failure
due
to
an
agent
dying,
please
contact
us
because
that
might
be
related
to
that
change,
and
we
want
to
be
sure,
because
we
are
not
able
to
monitor
it
carefully
right
now,
and
that
means
we
should
start
also.
The
opponent
image
will
use
h
as
well.
B
I
think
we
should
find
some
way
to
start
working
on
open
telemetry,
because
relying
on
people
crying,
I
mean
that's
something
that
it's
not
really
reliable.
A
D
A
So
I
try
to
check
weekly
these
times
to
see
the
impact.
So
it's
been
two
weeks
we
change.
We
surveyed
the
labels.
We
saw
a
trend,
a
decreasing
trend.
Even
the
peaks
is
a
smaller
the
two
pass
peaks.
So
we
have
decreasing
trends
so
now
we
should
have
one
or
two
weeks
before
we
start
things
excellent.
Thank
you.
Thanks
very
much.
A
That's
all
for
the
aws,
unless
someone
has
a
question
one
two:
three
okay,
next
topic
we
have
is
the
work
in
progress
on
the
wiki,
so
everybody's
working
hard
on
putting
a
static
version
of
the
wiki
content
that
should
be
in
in
the
form
of
nginx
server
a
static
web
server
inside
the
kubernetes
cluster
so
static.
That
means
all
the
html
export
is
put
under
that's
currently
being
tested.
A
B
B
So
this
is
the
idea
just
to
have
a
docker
image.
You
can
you
can
play
with
that
repository,
so
just
docker
image,
nginx
and
that's
it
and
then
I
don't
think
they
mean
you
already
mentioned.
Pubic
charts,
which
is
a
new
git
repository,
but
rv
is
also
working
there
to
create
a
hand
chart
that
would
allow
us
allow
us
to
deploy.
B
A
So
the
next
topic
is
around
the
cleanings
up.
We
have
different
area
where
we
need
to
remove
dead
code,
remove
that
dependencies,
remove
your
new
things
in
in
the
area
of
the
charts
who
are
working.
There
are
already
some
issues
on
that
topic
to
clean
up
the
end
file,
the
location
of
the
m-files
and
so
ervis
started
a
public
chart
repository
that
should
be
aimed
to
provide
elm
charts
to
someone
else
than
the
jenkins
infrastructure
team,
which
means
the
development
methodology,
the
testing
methodology
and
the
deployment
life
cycle.
A
A
A
So
that's
the
that's
the
reason
of
that
cleanup,
so
it
has
been
started
already
with
the
public
chart
with
the
wiki
chart.
We
uninstalled
during
the
cleanup
last
week,
something
that
was
an
arc
mirror.
That
was
a
mirror
running
inside
aks.
A
That
was
aimed
to
be
a
demonstration
of
how
to
install
a
mirror
if
you
have
a
kubernetes
cluster
at
home
for
the
infrastructure,
so
instead
of
hosting
that
mirror,
which
is
unused
and
cost
us
some
dollars
on
aks.
The
goal
is
to
provide
the
associated
n
chart
in
the
public
chart
in
the
future.
So
we
can
advertise
and
show
that
as
a
resource.
A
In
the
cleaning
zaps,
there
are
some
incoming
proper
requests,
which
should
be
deleting
everything
related
to
kubernetes
in
puppet,
because
pupet
is
not
managing
kubernetes
since
a
few
years
now
under
us,
there
are
still
some
manifest
on
things.
The
reason
is
because,
if
we
want
to,
if
we,
if
we
want
to
start
working
on
using
the
osu
sl
machines
as
k3s
cluster
for
providing
workload
to
cigo,
the
risk
is
to
mix
accidentally
different
kind
of
kubernetes
code.
D
A
A
And
finally,
we
have
cleaning
up
of
issues
in
general,
so
that's
a
weekly
work
in
progress
with
rv
olivia
high
that
we
do
from
time
to
time
trying
to
clean
up
all
the
issues
that
doesn't
make
sense,
close
the
incoming
issues
or
migrate
them
when
they
need
when
they
have
been
created
accidentally
in
our
tracker.
A
So,
as
we
said,
I
think
it
was
two
weeks
ago,
the
user
experience
when
opening
an
issue
is
terrible.
That's
a
topic
that
we
should
bring
to
the
advocacy
team,
because
there
is
no
nothing
that
helps
the
user
when
they
click
create
an
issue
that
helps
them
to
know
if
they
have
to
choose
infra
or
jenkins
project
or
something
else
on
jira.
A
D
So
so
we've
got
is
the
is
the
work
that
gavin
mogan
did
on
the
plug-in
site
for
report,
an
issue
already
a
beginning
towards
that,
when
I
click
record
an
issue
on
this
plug-in
site
now
it
takes
me
to
a
page
that
presents
three
choices.
Do
I
want
to
create
a
bug,
an
enhancement
or
a
security
issue?
Is
that
kind
of
concept?
What
you're
looking
for
or
something
different?
A
Great
help,
I
don't
know
how
much
we
can
rely
on
jira
behaviors
because,
for
instance,
we
realized
that
if
by
any
google
search,
you
ended
up
on
jira
looking
for
an
issue
inside
the
infra,
the
infra
project
is
put
as
the
last
default
project.
When
you
create
an
issue
on
the
next
time,
so
maybe
some
setup
and
jar
is
needed.
I
don't
know
how
much
of
gavin
walks
will
help
to
overcome
that
kind
of
behavior
yeah.
D
D
A
Yeah,
so
that's
all
for
the
clean
cleanings
up
some
less
someone
there
as
a
question,
something
to
add.
Okay,
let's
jump
up
olivier
that
one
is
for
you
digital
ocean.
So
last
week
we
we
were
not
able
to
see
the
credits.
You
contacted
another
response
from
loren
from
digitalocean.
What's
the
status.
B
That's
true,
so
she
confirmed
that
we
received
the
crit,
but
we
still
don't
see
it
in
our
user
interface,
so
she's
looking
at
it
and
trying
so
she
yeah
she
raised
shoulders
under
on
digitalis
inside.
A
B
A
Two
minor
topics
there,
first
one
there
is.
There-
has
been
some
walk
last
week
on
update
cli
to
ease
the
how
we
change
a
value
in
a
file,
because
that
was
not
really
user
welcoming
it
was
working,
but
it
was
creating
some
ghosts,
pull
requests
where,
like
requests
say,
update,
gdk8,
where
in
fact
it
was
changing.
Something
else
on
another
line
sounds
like
that
should
be.
It
will
change
with
that
change.
A
That
should
help
so
minor
and
another
minor
elements
mark
and
high
started
to
work
in
pair
on
working
on
putting
the
docker
images
for
the
infrastructure
on
cigo.
A
A
So
the
next
one
is
kubernetes
1.20
upgrades
since
digital
ocean
is
delayed
because
we
don't
have
the
credits.
Yet
I
propose
that
we
put
back
the
upgrade
to
kubernetes
1.20
as
a
important
topic
to
treat
on
the
upcoming
weeks,
because
1.19
kubernetes
vanilla
is
now
one
of
life.
B
So,
just
to
add
more
context
on
that
topic,
so
we
have
created
some.
I
can
d
templates
that
we
can
use
that
we
can
use
when
we
do
an
upgrade,
and
so,
if
you
want
to
look
what
we
did
in
the
past,
you
can
go
to
jenkins
infrastructure
documentation
and
under
documentation,
maintenance
kubernetes.
You
see
the
bus
upgrade,
so
the
idea
is
to
do
the
same
where
we
plan
in
advance
all
the
things
that
may
change,
and
then
we
just
document
the
procedure,
so
it
just
gets
easier
and
easier.
B
A
A
D
A
A
The
bridge
completely
so
so,
let's
say
ever
you
lead
the
subject
I'll
be
there
as
you
back
up.
If
you
need
anything,
I
volunteer
to
help
on
that
topic.
A
Okay,
that's
all
I
saw
someone.
I
did
gdk
update
in
docker
image.
D
So
that
was
me,
the
I
saw
red
hat
issued
a
security
advisory
for
jdk
that
included
a
need
to
update
to
jdk
8
u3
312
and
jdk
8
11
0
13..
So
so
we've
we've
updated
the
docker
images,
but
their
first
exercise
in
doing
a
release
will
be
with
2.319
and
with
2.303.3
security
releases.
So
one
of
my
worries
was
that
I
I
would
it
would
be
an
awkward
thing
if
the
docker
build
process
failed
and
caused
daniel
or
vader
problems
in
the
security
release
on
thursday.
Is
there
something
we
should
be?
D
B
A
D
A
A
That
means
we
might
need
to
create
a
new
lts
release,
because
last
time
we
had
to
change
something
on
the
docker
image.
That
was
not
direct
jenkins.
The
last
email
on
the
dev
mailing
list
was
okay.
If
you
want
to
change
whatever
environment
variable
under
official
image,
you
need
to
create
a
new
jenkins
version.
Yes,
because.
A
A
I
need
I
need
to
double
check
that
I'm
not
saying
crap
and
that's
it's
not
my
imagination,
but
we
have
merged,
update
cli
releases
last
week
and
it
has
been
deployed.
So
let
me
check
not
sure
if
it's
available
for
trusted
ci,
that
that
could
that
should
be
easy,
though
power
pc.
I
don't
know
if
they
were
able
to
release
the
power
pc
for
gdk8,
because
the
previous
had
version
had
version,
which
is
not
the
case
of
that
one.
A
D
A
Okay,
so
if
you
leave
the
subject,
mark
don't
hesitate
if
you
need
backup
on
that
one
as
well.
If
you
are,
you
have
a
lot
of
tasks
since
we
are
all
there
underwear
and
we
already
started
working
on
that
we
can
help
the
security
team
if
they
want
great.
Thank
you.