►
From YouTube: 2022 06 14 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
Putting
okay
first
thing:
first
announcement:
the
weekly
process
went
well
this
week.
A
That
means
that
all
the
the
work
that
basil
and
the
team
did
last
week
is
reused.
So
good
thing,
I
assume
that
the
there
is
a
checklist
that
should
be
run
later
today.
A
A
A
A
As
always,
we
have
contacted
them,
maybe
a
bit
late.
This
time
yesterday
we
decided
to
it
was
just
punk
tool,
it
wasn't
blocked
or
it
was
usable
today
it
isn't
so
we
contacted
them
today
as
soon
as
we
so
that
it
started
to
be
honest,
thanks
stefano
rv,
for
opening
the
statues
to
communicating
on
the
users
about
that.
A
A
Possible,
where
some
usual-
let's
say
day-to-day
maintenance
tasks,
basil
has
been
removed
from
some
plugins
that
he
doesn't
maintain
anymore.
So,
thanks
tim
for
that,
we
were
able
to
install
the
latest
version
of
the
kubernetes
plugin
on
ci
jenkins
io,
which
features
the
fix
for
when
suddenly
you
have
to
spawn
a
lot
of
pods
at
the
same
time
that
was
creating
some
locks
and
some
unwas
slowing
down
or
sometimes
locking
completely
the
cluster.
A
A
C
That
correct
that's
correct.
As
far
as
I
know,
I've
submitted
one
more
pull
request.
This
one
to
jenkins
to
www.jenkins.io
that
replaces
jenkins.
is
the
way.io
with
stories.jenkins.io
for
each
resolvable
url.
That
way,
the
only
remaining
broken
urls
are
jenkins
is
the
way
dot
io
and
I'm
working
with
elissa
tong
and
gavin
mogan
to
try
to
find
the
content
that
is
missing
that
would
resolve
those
links.
C
A
Make
sense
so
many
thanks
mark
for
managing
that
during
the
conference,
thanks
rv
for
the
work
you
put
that
and
also
thanks,
tim
and
alisa
for
also
the
all
the
tasks
you
did
on
that
issue
about
last
weekly
last
week,
weekly
release
that
failed.
We
had
to
burn
two
numbers,
so
it's
more
an
audit
of
the
issues
that
we
met.
A
A
You
need
a
way
to
retrieve
the
gigabyte
of
files
already
present
on
production,
have
them
accessible
locally
run
the
hud
on
that
one
and
then
copy
back
these
files?
It's
not
that
much
a
problem.
We
could
have
a
caching
file
system
on
the
release,
environment
and
everything
on
one
side
and
then
airsync
on
the
other
side,
but
we
have
to
do
this
in
order
to
decouple
the
release
process
from
that
machine.
C
A
Correct
by
default,
the
release
process
has
a
dummy
key,
a
gpg
key
that
everyone
can
get
access
to
which
allows
to
sign,
but
it's
not
recognized
by
the
usual
certificate
provider
for
the
packages.
A
A
What
could
we
do
about
that?
That
means
being
able
to
either
do
it
on
as
part
of
the
release
process.
So
there
are
solutions
on
that
area.
Tim
is
aware
of
that,
but
no
action
required
for
us
for
now,
because
we
focus
on
moving
update
center
out
of
that
machine
somewhere
else,
and
then
we
can
start
discussing
the
future
of
that
machine.
C
C
A
There
is
one
to
the
2.332
line
and
there
is
the
twin
sister
to
the
to
the
next
lts.
That
should
happen
in
september,
so
the
it's
okay
for
the
other
as
expected,
because
that
is
from
the
same
weekly
and
if
I'm
correct
the
not
that
line,
but
the
other
line
should
be,
should
drop
java
8
by
default.
C
A
B
A
Dot
four
already,
okay,
and
so
in
order
to
have
the
security
release,
we
have
to
backboard
to
roll
back
some
changes.
We
fixed
the
image
to
the
latest
that
still
contain
both
chideka
8
and
gdeka
11,
which
in
turn,
we
need
to
add
back
that
path,
because
ddk8
is
the
default
on
that
machine.
So
the
pod,
the
pods
that
are
starting
that
trigger
the
release.
A
A
C
A
A
Okay,
thanks
survey
for
dropping
the
dependency
of
rmg,
so
now
we
use
a
fully
fledged
docker
machines
everywhere,
instead
of
img,
so
no
more.
Maintaining
that
part
great
job
that
wasn't
the
easiest.
One
thanks,
stefan
for
working
on
bootstrapping,
a
new
terraform
project
for
the
oracle
cloud
maintenance,
while
I'm
there.
A
So
we
have
now
two
child
tasks,
one
which
we
will
see
later.
There
is
one
that
I
want
to
take.
Will
that
will
import
the
existing
resources
mark?
We
saw
with
stefan
that
we
have
free
machines.
We
have
archives.
There
is
one
with
your
name
that
I
assume
you
are
using
for
testing
jenkins
on
iremember
system.
A
Okay,
because
do
you
mind
stopping
it
and
deleting
it
if
it's
not
used
anymore,
or
at
least
stopping
it,
to
not
consume
credits,
because
with
the
update
center
that
should
migrate
on
that
area,
we
will
start
to
be
on
an
area
where
yeah
not
too
much
machine.
At
the
same
time,
I
won't
say:
okay,
yes,
unless
you
have
a
use
case
on.
C
A
A
Oh,
yes,
that's
a
minor
challenge.
We
did
under
release,
but
template
you
can
look
at
it.
That's
really
minor.
I
memorized
failed
to
come
online,
so
thanks
alex
for
opening
that
there
were
issue
10
days
ago
last
week
about
the
imemory
virtual
machines
that
are
ephemeral,
agent
and
ci
gen
kim,
say
mostly
used
for
testorness
of
jenkins
car,
usually
and
some
bills.
A
This
machine
were
completely
blocked
and
locked,
so
tim
did
a
revert
of
a
recent
feature
on
the
azure
vm
plugins,
and
also
we
were
able
to
fine-tune
the
configuration
of
the
plugin
on
all
our
instances
so
that
the
azure
machines
are
immediately
thrown
away
through
the
way
once
the
build
have
used
them.
That
was
already
the
case
for
ec2,
but
not
for
azure.
A
A
A
One
issue
has
been
closed
as
not
done.
I
don't
remember
why
the
sign
off
on
web-based
commits
irva.
Can
you
remind
yeah.
E
A
A
Thanks
no
question:
okay
last
done
tasks,
gsoc
plug-in
ill-scoring
system,
so
as
part
of
the
gsoc
project,
there
is
one
of
the
project
this
year.
That
adrian
is
monitoring.
A
E
A
In
pair,
but
driven
by
stefan,
we
are
working
on
migrating
update
center
to
another
cloud,
ht
oracle
cloud,
which
involves
creating
a
new
machine
with
terraform
and
the
neutron
terraform
project.
With
the
data
volume,
we
are
working
on
how
to
convert
the
kind
of
machines
and
then
that
machine
will
be
added,
and
then
we
will
do
a.
We
will
split
the
traffic
once
ready
between
both
after
top
full
and
if
everything
goes,
we
can
absolutely
move
everything
to
oracle.
A
A
We
are
trying
to
dig
the
terraform
oracle
provider,
which
is
not
the
easiest.
One
thanks.
Stefan
for
the
work
on
that
part,
so
is
that
okay
to
continue
for
next
iteration
for
that
task?
Stephan,
yes,
of
course,
that
maps
with
the
priority
given
the
need
for
here
we
have
for
money,
digitalocean
irvine!
I
have
should
meet
later
today,
the
team
we
have
created
a
note
on
akmd
for
that
topic.
A
A
The
goal
is
we
cover
different
options,
how
much
if
we
keep
the
same
burn
rate
that
we
had,
that
should
be
1k
per
month,
so
that
means
asking
for
if
it's
a
sponsory
ship
for
one
year,
that
will
mean
12k
to
to
use
on
their
cloud.
A
We
considered
also
other
alternatives
instead
of
the
kubernetes
cluster,
so
either
we
could
put
limit
on
the
cluster
to
reduce
the
amounts
we
want
to
discuss
with
them.
The
fact
that
we
could
gain
almost
400k
per
month
if
we
were
able
to
have
a
scale
up
scaled
down
to
zero,
which
is
not
the
case
technically
speaking.
So
that's
topic.
We
want
to
bring
to
them
and
then
based
on
the
amount
of
money
they
are
prepared
to
give.
A
We
could
also
set
up
mirrors
for
jenkins
managed
by
ourselves,
because
they
have
data
centers
in
singapore
and
india
in
bangalore
and
that
that
wouldn't
cost
too
much.
That
will
be
a
way
even
with
the
bandwidth
and
also
we
could
use
dynamic,
ephemeral,
virtual
machines.
They
only
support
linux
out
of
the
box,
but
still
we
could
use
all
the
docker
builds
on
frasier
or
the
machine
for
trusted
ci.
We
could
use
totally
different
setups
or
clouds
than
sea
h
and
king
cio
to
split
the
cost.
A
So
we
have
different
options
with
different
level
of
cost
measurements,
we'll
see
how
they
feel
about
continuing.
The
proposal
is
to
ask
the
same
the
same
sponsorship
burn
rate
aka
1k
per
month.
That's
already
a
lot
in
a
sponsor,
it's
a
bit
more
than
what
they
propose.
Initially,
it's
an
increase
for
them,
so
we
might
want
to
then
prepare
to
write
more
blog
posts
or
things
about
their
setups.
A
Docubrate,
limiting,
I
should
have
asked
an
answer.
I
didn't
so.
I'm
gonna
send
an
email
to
the
open
source
program.
The
person
in
charge
of
that
program
looks
like
they
are
really
really
busy
and
also
sending
an
official
email
on
the
mailing
will.
Allow
me
to
share
most
of
the
information
with
the
rest
of
the
team
etu.
So
we
will
have
something
written
that
we
could
use
in
the
future,
so
that
should
be
same
next
iteration
upgrade
to
kubernetes
1.20.
Stefan,
what
is
the
status?
A
Are
you
sure
I
think
we
merged
something
on
terraform?
Oh
okay,
okay,.
D
A
Can
you
take
care
of
chatting
that
issue?
Let
me
ask,
and
are
you
going
to
work
on
that
topic
on
the
next
iteration
on
one
of
the
other
clusters
or
yes,
I
hope
so.
Okay,.
A
A
E
E
A
Okay,
I
think
we
should
raise
an
issue
on
the
plugin
in
charge
of
implementing
powershell
step,
because
as
for
today,
there
are
two
keywords
on
windows:
you
have
pwsh
and
powershell
and,
as
I
said,
that
could
be
a
really
a
great
help
to
the
end
user.
If
jenkins
could
be
able
to
detect
the
one
to
check
because
either
you
have
one
or
the
other
and
pwsh
is
for
smaller
distros
or
older.
E
On
everything
I
don't
know,
I'm
not
sure,
but
I
think
I
think
it's
more-
the
commercial
cars
and
the
windows
powershell
version.
E
A
Okay,
so
clearly
definitively
a
topic
to
open
on
the
community,
because
that's
a
feature
on
the
pipeline
plugin
really
important
for
that
there
isn't
any
action
required
for
infrastructure.
A
E
Much
problem,
but
in
our
chat
applying
library
we
are
always
calling
with
powershell
command.
Okay,.
A
A
Okay,
so
it's
working
today,
so
it's
available
that
might
disappear.
If
I
understand
your
explanation,
but
that
issue
it
was
about
on
the
a
the
docker
windows
image
using
aci.
E
E
A
The
initial
problem
that
raised
that
issue-
that
was
something
that
jc
and
james
nord,
were
blocked
on
and
they
use
b80
instead
of
powershell
that
solved
their
issue.
A
C
D
A
Another
topic
last
one
currently
work
in
progress,
evaluate
hit
high
to
improve
the
stability
of
the
builds
so.
C
A
The
use
case
is
for
spot
instances
when
we
have
a
spot
virtual
machine,
it
can
be
reclaimed
in
less
than
one
minute
and
the
agent
machine
is
stopped
and
removed,
which
means
there
is
no
way
to
keep
this
to
risk
to
have
the
same
state.
So
the
pipeline
have
to
know
the
reason
of
why
it
failed,
and
when
we
detect
such
error,
then
it
should
be
retried
automatically
one
two
eventually
free,
because
you
don't
want
developer
having
to
watch.
If,
oh
my
build
failed,
the
reason
is
because
of
the
agent.
A
E
A
They
failed
to
continue
restarts
because
of
the
reason
so
jesse
is
working
on
that
that's
an
open
source
work
and
we
have
started
and
deployed
that
work
to
infrastray
this
morning
earlier.
The
goal
is
to
try
more
and
more
use
cases,
so
we'll
check
with
chassis
that
will
continue
next
week.
The
target
is
ci
jenkins
io,
but
we
don't
want
to
release
this
pipeline
because
that
these
are
the
pipeline
plugins.
So
if
we
release
that
and
it
break,
it
can
be
sensitive,
so
we
propose
the
help
to
gc.
So
we
start
on
afroci.
C
A
We
need
real-life
use
case.
We
cannot
test
on
some
isolated
environments
that
just
run
a
kind
of
ephemeral
pipeline
that
does
not
map
the
reality
of
end
users.
So
that's
why
we
still
have
to
go
to
production
really
soon
and
we
will
install
the
pipeline
plugins
in
incremental,
build
meaning
from
a
pull
request,
not
released
yet
on
ci
jenkins
at
a
moment
on
time,
because
we
need
feedbacks
on
that
core
behavior,
because
that
could
impact
a
lot
of
users.
A
A
B
A
E
A
A
A
First
one
maven
386
upgrade
campaign
thanks
survey
for
and
basil
for,
raising
that
one.
A
A
However,
we
had
danielle
that
asked
for
waiting
before
the
staging
of
the
security
release.
So
that's
why
I
did
quickly
a
comment
yesterday.
However,
I'm
sorry
for
blocking
that,
because
otherwise
you
did
good
and
we
should
have
proceed
as
soon
as
possible.
There
is
no
emergency
on
doing
that,
but
still
it's
important
to
do
it
soon.
A
C
A
A
A
So
we
are
condemned
to
use
the
old
method
with
a
technical,
github
user
that
has
the
right
to
write
everywhere.
That's
not
ideal
in
term
of
security,
but
we
don't
have
any
solution
and,
as
tim
said,
we
should
have
a
dedicated
jira
user,
because
it
was
the
jenkins
in
robot
or
years
before
or
jenkins,
but
and
it
was
shared
with
other
usages.
A
So
not
only
we
were
able
to
raise
quickly
to
get
the
limits.
So
that's
why
teams
suggest
to
have
a
dedicated
account
just
for
that
integration,
so
it
only
use
the
right
limit
only
for
jira
and
github.
A
A
E
Shira
for
jenkins
core
is
still
a
requirement
and
will
stay
action.
A
E
C
A
Produce
I
don't
mean
to
to
hurt
feelings
and
to
fight
between
jira
and
github
stuff.
It's
just.
I
didn't
realize
that
they
were
using
jira
and
the
core
and
plugins.
That's
all
the
takeaway
is
that
there
are
two
or
many
more
different
use
cases
and
jira.
Github
issue
alone
cannot
fulfill
all
the
use
cases,
so
two
tools
for
different
cases
and
we
need
both.
That's
what
ends
the
integration
request.
A
Mark
you
opened
an
issue
about
the
cpu
z
agent.
That
was.
C
That
that
one
you
can
assign
to
me
damian
if
you're
welcome,
if
you're
willing
to
or
I'll
assign
it
to
me,
because
I
think
it's
one-
I
need
to
get
the
run
book
updated
so
that
we
can
do
it.
There
is
no
reason
for
us
to
to
to
put
it
on
anybody
else.
There
I,
inter
interact
with
ibm.
I
just
need
to
be
sure
that
I
describe
how
this
works
and
okay.
Then
we
can
consider
your
suggestion,
I'm
not
a
puppet
expert.
I
know
you'd
suggested
gee.
A
The
the
thing
is
that,
once
you
have
an
initial
access
as
a
one
human,
the
advantage
is
that
then,
by
having
puppets
that
will
be
able
to
make
auditable
if
we
need
to
install
some
change
at
large
scale.
If
we
want
to
configure
maven
java
following
the
rest
of
our
updates
and
also
it
will
avoid
everyone
on
the
team
to
be
able
to
maintain
that
machine
in
the
future.
If
we
need
it
so
that
that's
the
reason
so
yeah,
if
you
want,
we
can
try.
A
A
Thanks
for
raising
the
issue,
I've
started
the
ubuntu
2204
upgrade
campaign.
As
a
reaction
of
last
week,
weekly
release.
A
That
means
we
will
have
some
consequences
in
particular
openssl
current
software
updated,
which
means
we
might
have
issues
on
some
of
our
missions,
so
we
have
to
keep
track
of
that.
That
should
be
interesting
on
some
machines,
but
yeah
be
careful.
So
my
proposal
is
that
we
don't
start
working
on
that.
Yet
we
have
kubernetes.
We
have
update
center
to
migrate
on
kubernetes
to
finish
migrating
or
terraform
managing.
A
C
A
A
A
Any
question
things
unclear
topics
you
will
want
to
br
to
bring
the
repair
of
tata
dog
that
we
just
broke
is
oh
good
point
outside
of
that.
Yes,
so
that's
why
I
used
an
announcement
about
the
outage
right
after
that
meeting.
We
will
open
an
issue,
because
the
outage
yesterday
did
not
justify
an
issue.
It
was
controlled
today
it
justifies
so
we'll
do
it.
A
Stefan
and
I
tried
to
disable
pagerduty
since
the
system
was
done,
and
there
is
nothing
we
can
do
about
so
paging.
The
person
in
page
of
duty
made
no
sense
and
while
trying
to
disable
the
what
we
understood
would
have
been
the
correct
agent
element
now
pagerduty
is
alerting
us
with
more
alerts,
so
we
have
to
better
understand
how
it
works
and
fix
it.
A
A
A
I
think
we
all
forgot
to
create
one
quite
regularly.
So
that's
not
I'm
not
pointing
finger,
and
I
don't
say
it's
a
bad
thing.
It's
just
I'm
just
saying
we
we
could
improve
in
the
future,
because
we
would
have
an
audit
log
and
we
won't
forget
elements
such
as
this
one.
Like
stefan
reminded
us,
can
you
do
something
to
have
a
help
desk
issue
that,
with
the
correct
label,
will
trigger
automatically
a
new
status
dot
io
dodge
instead
io
issue.
E
Yeah,
you
have
something
like
that
planned
better.
It
could
be
awesome
so.
A
Stefan,
can
you
open
the
nail
best
issue
describing
what
you
want
and
I
will
have
a
label
status
check
just
describe
the
future
requests.
Just
please
write
this
down.
Writing
things
down,
allows
us
to
share
the
knowledge,
because
there
are
people
that
cannot
attend
or
who
don't
want
to
attend.
They
can
still
contribute.
C
So
so
damian
that
brings
a
question
for
me.
This
system
390
thing.
Should
I
flag
that
somehow
on
status.jenkins.io
and
likewise
the
powerpc?
That's
currently
the
agent
is
offline.
Should
this
be
in
status.jenkins.I,
or
is
this
too
too
too
too
questionable
relevance
to
bother
people
with
it
on
status.jenkins.io?