►
From YouTube: 2021 10 22 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
Hello,
hello:
everybody
welcome
to
the
weekly
team
meeting
for
the
22
of
october.
So
today
we
are
leaving
irvine
high.
It
seems
no
mark
my
turn
first
of
all,
no
announcement.
Yet
nothing
happened
on
the
finger
planned
in
the
upcoming
weeks.
B
So
let's
jump
straight
to
the
operational
parts.
First
points:
aws
cost
management.
So
thanks
survey
for
managing
the
high
mem
labeling
issue,
so
now
some
label
convention
on
ci
the
jenkins
data
have
changed.
The
goal
was
that
we
should
not
use
imm
machines
that
are
beefy
and
custom,
really
expensive
machines
when
we
only
want
to
build
a
few
docker
containers.
B
B
Something
else
that
came
yesterday
is
that
a
team
detected
that
the
current
gvm
options
that
are
used
for
some
acceptance.
Testing
on
jenkins
core,
even
though,
are
using
im
machines,
which
are
64
gigabytes.
There
are
still
parameters
for
eight
gigabyte
machine,
which
means
the
tests
are
slow
compared
to
most
of
the
developer
laptops.
B
So
we
should
be
able
also
to
improve
the
speed
of
these
builds
leading
in
less
using
these
machines
because
they
will
be
released
and
stopped
sooner
next
step.
Regarding
the
cost
management,
the
two
elements
we
have
identified
that
could
be
highly
valuable
for
us.
Are
you
configuring,
ci
jenkins,
io,
to
use
spot
instances
for
the
aws
instances?
B
A
So
on
that
topic,
I
received
no
no
response
from
digital
at
this
time,
so
yeah
we
are
still
waiting
for
the
credits.
B
Okay,
we
could
bump
gave
in
maybe
later
today
when
he
will
be
awake
just
in
case.
If
we
don't
have
answer,
we
can
still
start
creating
another
cluster
on
those
usb
machines.
That
will
be
another
topic,
but
that
was
not
identified
as
a
priority
for
now.
B
Regarding
the
transition
of
the
account
so
based
on
the
feedback
from
the
club
b's
id,
it
seems
like
we
won't
have
to
migrate
the
resources,
which
is
a
good
news,
because
that
will
be
less
effort
at
first
sight.
That
should
be
only
accounting
and
billing
changes
so
worst
case
we
might
lose
the
access
for
one
or
two
days
on
the
aws
console.
That
will
be
the
worst
case
scenario.
B
No,
we
have
to
reconsider
that
cloudbees
asked
us
to
to
do
that
as
soon
as
possible.
I
have
to
that.
That's
on
me.
I
have
to
to
propose
a
date.
The
proposal
would
have
been
end
of
november,
so
it
left
us
some
time
to
decrease
the
cost.
Still
to
be
sure
we
are
safe.
B
B
So
where
the
plan
is
that
arvie
and
I
plan
to
do
that
monday
monday
afternoon,
statues
will
be
updated
in
the
next
hour
to
to
tell
the
users,
and
I
will
send
an
email
to
the
jenkins
developer.
B
We
should
not
expect
based
on
erv's
research
and
the
double
check
we
did.
We
should
not
expect
any
service
interaction
interruption,
but
still
better
to
have
notice
for
the
users
just
to
be
sure.
If
something
goes
wrong,
we
might
have
the
services
being
cut.
All
the
services
could
be
services
hosted
on
aks.
That
could
be
cut
for
a
few
minutes.
B
C
B
Upgrading,
it
is
usually
really
smooth
because
we
have
high
availability
on
the
nginx
controllers.
However,
here
we
are
speaking
about
changing
api
implementation
for
defining
doing
these
rules,
so
that
one
was
a
big
thing
on
the
kubernetes
cluster,
and
so
it's
just
what
we
have
to
prepare
us
correctly,
because
the
migration
path
is
not
really
smooth.
To
be
quite
honest,
whatever
ingress
controller
you
choose
but
based
on
early
research,
it
will
be
easier,
as
I
initially
anticipated.
B
B
Issue
triage
nothing
to
say:
we
did
a
big
effort
this
week
and
the
past
weeks
to
clean
up
and
remove
all
the
issues
so
yeah.
If
you
continue
to
see
all
the
issues
that
seems
like
either
an
error
or
project,
and
that
should
be
migrated
to
the
jenkins
project
or
that
should
be
closed
because
not
up
to
date,
don't
hesitate
to
wait
and
close
it
with
a
message,
so
we
can
clean
up
and
start
working
again
based
on
tracking.
B
That's
all
on
the
part.
Is
there
any
question
about
issue
trajec
specifically.
B
There
is
still
some
work
regarding
changing
files.
That's
a
weak
point
of
update,
see
a
light
ability
to
change
a
specific
line
based
on
the
pattern
or
line
number
that
should
help
and
had
way
more
use
cases.
So
we
spent
some
amount
of
time
this
week,
since
we
did
not
have
something
really
critical.
B
So
we
took
the
opportunity
to
work
on
that
report
thanks
server,
also
for
wasting
on
the
update
cli
pair.
B
So
that
could
be
a
good
usage,
a
good
use
case
allowing
changing
xml.
If
you
want
to
keep
track
of
dependencies
inside
pub
xml
so
that
bunch
of
the
project
we
have
on
boston,
keynes
and
jenkins
info.
B
A
B
One
two
three
okay
last
object
I
had
in
the
list
for
today
for
today
ci
jenkins
iu.
Since
one
week
we
have
maven
3.8.3
released
on
all
the
vm
agents
that
has
been
done
transparently
next
to
the
usual
git
updates
and
gdk
updates.
B
B
So
we
have
to
confirm
that,
though
I
haven't
spent
that
much
time
on
this,
but
the
change
applied
this
week
were
applied
successfully.
So
I
assumed
that
it
fixed
the
issue
which
is
really
cool.
B
And
finally,
not
to
thank
survey
for
from
for
noticing
that
some
of
the
labels
were
a
bit
shady,
such
as
the
wind
dock
label
for
the
agent,
which
is
hard
to
understand
for
newcomer,
so
yeah
in
as
part
of
the
imem
labels
changes.
B
C
So,
as
far
as
I
can
tell
the
tools
now,
the
so
java,
for
instance,
is
now
hard
located,
slash,
op,
slash,
jdk
dash
x
and
similarly
at
the
root
of
the
windows
file
system.
Thanks
very
much
no
more
tool,
installers,
no
more
downloading
100
megabyte
installer.
Every
time
we
need
an
agent
thanks
for
the.
B
We
we
still
have
kept
the
older
downloads,
and
I
think
that
would
be
good
to
keep
keep
them
as
a
fallback,
though,
and
the
pipeline
library
has
been
updated
to
use,
then
as
a
fallback.
So
if
there
is
no
java
installation
working,
it
should
be
there.
However,
the
recent
jenkins
core
issues
that
we
have
to
fix
on
the
pipeline
demonstrate
that
the
pipeline
library
still
has
a
long
way
to
be
improved
to
not
break
builds.
When
we
change
your
location,
there
is
still
a
hard
constraint
on
that
part.
B
C
A
A
C
B
Could
we
run
next
tuesday,
starting
next
tuesday,
since
we
will
have
the
invest,
ingenix
controller,
sure.
B
C
C
C
And
olivia,
I'm
in
my
calendar
now
are
you
okay?
If
I
just
do
the
change
right
away,
that's
perfect!
Okay!
So,
beginning
next
week
the
jenkins
infra
team
meeting
moves
to
say
it
again.
It
was
26th
of
october
at
2,
30
utc,
okay,
26
at
2
30,
so
30
minutes
later
than
the
current
time,
and
it
is
utc
we're
set
thanks.