►
From YouTube: 2022 05 10 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
Okay,
welcome
everyone
to
the
jenkins
infrastructure,
public
weekly
meeting.
Today
we
are
tuesday
10th
of
may
2022
as
usual,
I'm
adding
the
collaborative
notes
that
will
be
published
in
community
jenkins,
iowa
and
github.
This
session
is
recorded
as
well,
so
I've
just
added
on
the
zoom
link
and
an
irc
link
to
the
collaborative
notes.
A
Let's
get
started
with
the
announcement
first
of
all.
Last
week
the
weekly
release
was
failing
to
be
released
because
we
had
the
credential
and
azure.
That
was
expired,
so
that
has
been
fixed
thanks
mark
for
already
triggering
the
second
time.
The
release
and
the
release
was
successful.
A
few
hours
after
for
information
that
credential
is
now
is
now
under
the
management
of
infrastructure
as
code,
so
everyone
here
is,
should
be
able
and
has
the
right
to
update
it
in
the
future.
A
However,
we
have
created
a
new
issue
on
help
desk
to
think
and
walk
around
something
that
will
watch
the
exploration
for
different
kind
of
credentials
from
certificates
to
api
tokens.
That's
not
the
subject
there,
but
we
have
that
issue.
So
if
you
have
ideas
or
if
you
want
to
review
it,
the
link
has
been
added
on
the
notes.
B
I
haven't
checked
the
status
mark.
I
did
check
the
status.
It
was
by
a
restart
of
the
jenkins
controller
and
was
waiting
to
resume
so
there's
some
bug
in
the
declaration
in
the
pipeline.
That's
causing
it
not
to
correctly
resume,
so
I
just
stopped
it
and
restarted
it.
It
was
about
10
minutes
ago
that
it
started
so
roughly
two
hours
from
now.
It
will
have
completed
the
build
phase
and
start
the
packaging
phase.
B
A
About
that
or
I
will
do
it
at
the
end,
but
we
need
an
issue
to
track
that
element.
B
Is
a
help
desk
issue?
Okay
or
what
would
you
like.
B
A
Okay,
so
we'll
monitor
the
image.
Is
there
anything
else
about
the
past
or
current
weekly
mark
or
the
others.
B
A
Okay,
next
announcement
next
week,
there
will
be
there
will
be
a
security
advisory.
So
please
don't
merge
anything.
I
I
I'm
looking
at
you
damian.
A
Nope,
okay,
so,
let's
start,
let's
start
with
the
work
did
on
during
the
past
weekly
iteration,
we
had
an
issue
with
repo
jenkins
sayo
that
has
been
fixed.
That
was
an
issue
on
google
compute
cloud.
A
A
I
don't
have
anything
else,
despite
the
fact
that
we
are
not
able
to
have
status
jenkins,
io
being
automatically
updated
when
there
is
an
issue
on
g
frog,
so
we
have
to
still
to
rely
on
the
good
faith
of
any
contributor
that
time
it
was
team.
So
thanks
for
that,
that
issue
was
not
caused
by
the
year,
also
by
g
frog,
and
it
spent
a
few
hours
before
the
platform
was
back.
A
A
A
No
issue
whatsoever:
almost
everything
was
done
automatically
when
the
issue
was
opened
by
alex
so
good
for
our
automated
system
we
granted
access
to
bethel
to
some
ali
to
some
part
of
the
infrastructure.
The
goal
is
to
give
him
enough
fields
and
access
and
privileges,
so
he
can
help
us
on
diagnosing
the
issue
on
cig
insayo
from
the
president,
past
outages.
A
We
added
something
with
the
postmortem
that
I
still
have
to
publish
basil
will
need
access
to
the
eks
amazon,
the
amazon
cluster,
in
order
to
be
able
to
diagnose.
So
we
have
to
cre
to
check
with
him
if
he
can
access
the
aws
cloud
base
account,
which
is
the
actual
account
running
all
our
machine,
so
we'll
take
care
of
that
part.
That's
why
I
haven't
created
a
public
issue,
because
it's
still
the
cloud
biz
account.
So
it's
another
process,
not
the
usual.
A
And
finally,
they
were
I'm
not
sure
but
missing
permission.
I
I
forgot.
Oh
okay,
tim
you
fixed
that
one
okay,
so
alex
had
to
be
a
load
on
the
correct
group
to
access
fleet
ci
to
perform
the
lts
release.
Last
wednesday,
thanks
tim
for
fixing,
that
seems
like
the
key
cloak
was
terribly
slow,
which
was.
A
Still
not
sure
if
it's
related
to
ldap,
which
is
om,
killed
a
lot
okay.
Did
we
created
an
issue
yeah
it's
on
key
cloak:
okay,
thanks
tim
for
handling
that
and
having
the
patience
and
handling
the
frustration
created
by
a
slow
key
clock
that
can
be
terrible.
A
A
Pollution,
replacing
blue
sun
in
default,
display
url,
so
we
tried
to
merge
it
after
asking
questions
on
the
tickets
on
email,
thanks
for
everyone
who
answered,
but
as
cooked
by
some
users
the
when
you
enable
the
classic
ui,
it
seems
like
that.
It's
not
using
the
redirect
endpoint
on
jenkins
controller,
which
means
that
it
changes
the
permalink
of
on
the
github
check
generated,
which
means
you
cannot
ask
a
user
to
set
its
preference
to
classic
user
or
promotion,
and
you
cannot
have
something
that
is
warranted
to
work
in
the
future.
A
C
A
So
that
means
it's:
it's
exiting
our
scope
as
in
for
our
people,
we
need
that.
I'm
I'm
not
sure
what
is
the
usual
process.
Should
we
yeah?
We
might
have
want
to
open
an
issue
on
the
plugin
tracker
right.
C
A
A
So
I
propose
that
we
move
that
tickets
outside
of
the
milestone
until
something
new
come
sounds
okay
for
everyone,
because
I
don't
see
any
other
action
that
we
could
do.
Yes,.
A
Next
one,
there
are
still
two
open
tasks
about
ci
jenkins
io.
There
has
been
two
outage
two
weeks
ago.
We
ran
a
postmortem
last
friday
with
basil.
I
have
to
finish
the
notes
and
publish
them.
Basil
has
everything
that
he
needs
except
the
eks
cluster
and
is
walking
around
the
summary.
Is
there
isn't
any
action
expected
from
the
infra
team
basil
will
open
the
issues
on
the
desk
when
you
will
need
so
we
have
to
wait
from
him.
A
A
So
we
are
waiting
for
basil,
no
eta,
because
he
has
a
lot
of
other
stuff
to
do.
The
thing
is:
if
he
needs
something,
we
have
to
provide
him
as
much
as
quick
as
possible
to
unblock
him.
That's
the
only
takeaway.
A
A
I
got
news
from
docker
that
now
jenkins
is
part,
and
this
tag
has
open
source
program
for
them.
So
it's
the
dockercon
that
week
so
they
are.
They
have
in
mind
that
we
need
that
they
should
be
able
to
add
our
accounts
and
open
with
an
almost
unlimited
api
rank
limit
in
the
upcoming
days
or
eventually
weeks.
A
A
A
As
with
a
tip
as
brother
with
a
type
browser,
so
we
have
right
so
we
have
to
recreate
these
probes
change
them
to
the
types
that
stephan
selected
and
tested
on
a
single
one,
and
we
might
also
have
a
campaign
of
migrating
some
of
the
probes
that
are
run
by
the
docker
datadog
container
on
our
kubernetes
cluster
back
to
the
api.
Still
not
sure.
Why
do
we
run
such
tests?
A
A
A
It
can
be
fine,
my
graduating
jenkins
io
to
azure,
so
the
shift
to
kubernetes
went
very
well
great
job.
Stefan,
the
only
two
items
to
close
that
issue.
Are
we
clean
the
virtual
machine
on
aws,
but
we
still
have
to
clean
the
old
database
manage
database
on
amazon
and
documentation
updates.
So
almost
there
we
are
at
90
percent,
but
still
some
cleanup
tasks
before
being
able
to
finish.
A
We
still
have
the
mirror
in
singapore
requests,
so
we
are
in
a
worker
both
have
an
eye
to
finish
collecting.
What
what
do
we?
We,
we
weren't
able
to.
We
failed
to
find
a
documentation
about
what
to
tell
and
ask
the
people
proposing
a
mirror
how
much
space
do
they
need
what
they
need.
Where
are
the
instructions
for
them
to
start
mirroring?
A
A
That's
that
that's
the
the
idea,
so
thanks
for
continuing
for
confirming
tim
that
we
are
in
the
correct
direction,
so
the
status
of
that
task
for
the
upcoming
iteration
is
irv
and
I
are
going
to
search
mailing
lists
repositories.
We
are
going
to
write
a
run
book
with
the
information
and
then
we
can
contact
back
on
the
initial
email
thread
to
tell
them.
Okay,
you
need
that
you
have
to
do
that
and
and
let's
proceed.
C
A
Thanks
a
lot
airways
work
work
in
progress
for
building
our
own
windows,
image
windows,
docker
image
on
infrasi,
so
it's
mainly
two
two
areas:
providing
a
windows:
virtual
machine
image
with
all
the
tooling,
with
the
same
feature
set
as
we
have
on
linux,
to
link
the
docker
file
to
build
the
docker
file
and
publish
them,
and
it's
on
the
backer
image.
Templates.
A
A
A
We,
the
goal,
is
to
track
all
the
usages
that
we
could
have
of
the
former
mirrors
the
jenkins
data
domain,
I'm
working
on
a
blog
post
that
I
would
expect
be
published
end
of
week
if
it's
okay,
to
tell
that
mirror
and
quincy
will
be
forced
to
https
and
explaining
that
we
will
consolidate
all
the
mirror
infrastructure
using
the
new
one.
So
everything
has
been
tested
on
kubernetes.
A
A
No
because
we
also
serve
the
update
center
on
that
machine
and
it's
used
for
packaging.
I
mean.
A
A
C
A
C
A
Exactly
I've
tried
different
things
during
the
weekend
because
it
seems
like
it
is
going
worse
and
worse
in
terms
of
response
time
for
the
update
center.
We
need
to
do
something
about
that.
That
will
be
the
priority
for
the
upcoming
weeks
as
well,
but
still
I
did
some
cleanup
during
the
weekend.
A
Most
of
the
issues
are
related
to
that
error.
Message
about
the
scoreboard
for
apache
server,
because
apache
server
due
to
mirror
brain
is
configured
to
mpm
event,
which
is
a
set
of
dynamic
workers
to
handle
the
incoming
request,
and
it
seems
like
that.
The
setup
for
apache
is
not
correctly
done
on
that
instance,
but
is
since
olivia
and
I
decreased
the
site
of
the
machine.
We
went
from
16
cpu
to
8
a
few
months
ago.
A
I
bet
that
change.
We
didn't
correctly
updated
the
apache
server.
Fine-Tuning
that
might
have
an
impact
which
resulted
in
a
lot
of
hanging,
workers
that
fill
the
queue,
and
so
apache
starts
to
answer
slower
and
slower.
Most
of
the
time,
a
reload
or
a
restart
of
apache
helps,
but
still
it's
an
issue.
A
That's
an
old
way
of
configuring
apache
and
there
are
issues
with
apache
2.4
with
the
mpm
event
configuration.
So
as
the
goal
is
to
try
to
deprecate,
mirror
wine
as
soon
as
possible.
So
we
can
go
back
to
mpm
prefork,
where
apache
work
like
nginx,
with
a
set
of
static
child
processes,
always
the
same
cell,
it's
more
deterministic
and
you
can
pin
them
per
core.
So
it's
clearly
easier
to
scale
it
up.
A
So
they
can
start
publishing
on
both
rw
aws
and
the
new
oracle
machine
on
the
first
time
that
machine
should
not
be
available
right
now
and
as
soon
as
we
have
the
same
feature
set
on
both
machine,
we
can
switch
the
dns
in
a
few
weeks
on
that
new
machine.
That
will
also
allows
us
to
decrease
the
aws
bill
of
3k.
A
So
that's
an
important
one
harvey
you
mentioned
that
you
are
interested
in
starting
working
on
the
terraform
area.
B
A
So
the
first
step
right
now
is
to
prepare
the
foundation,
so
we
need
an
oracle
terraform
project
and
that
would
be
better
to
start
importing
the
existing
two
virtual
machines,
but
that
second
part
is
optional.
We
can
do
it
in
parallel,
but
we
need
a
foundational
terraform
project
to
manage
us
code
and
then
you
will
have
to
start
to
create
a
mesh
virtual
machine
with
terraform
and
integrate
it
with
puppet
and
you
plan
to
use
the
run
rubbing
in
dns
to
use
both
of
them
for
a
while.
A
A
A
So
that
one
we
keep
it
for
a
next
iteration,
the
new
monitoring
probe
so
work
in
progress.
As
we
said,
that's
on
your
area,
stephan.
I
propose.
D
A
Installer
ngd,
an
old
jenkins
controller,
that's
a
minor
task,
but
still
a
good
exercise
for
stefan
to
get
autonomous
on
puppets.
So
that's
a
low
priority
task.
That's
the
first
step
of
what
bazel
reported.
The
goal
is
to
install
that
package
to
improve
the
usage
of
random
number
generations.
A
So
the
first
step
is,
it
doesn't
cost
anything
and
it's
an
improvement
to
have
that
package
installed
on
all
the
virtual
machine,
managed
by
puppet
that
won't
fix
the
world
issue.
We
still
need
to
check
how
does
it
work
and
integrate
with
docker
container
for
the
virtual
machines
and
same
question
on
the
kubernetes
area,
because
it
depends
on
the
underlying
host
operating
system
and
how
the
container
engine
is
using
dev,
random
and
random,
but
first
step.
First,
installing
the
package
on
the
virtual
machine
is
the
good
first
step
so
work
in
progress.
D
D
A
So
you
will
need
some
some.
A
Okay,
yes,
so
we
keep
it
on
next
milestone.
Finally,
digitalocean
sponsorship.
I've
stopped
the
cluster
because
it's
my
payment
card
that
is
configured
on
digital.
B
A
A
A
A
Mail,
the
press
mail
issue
because
we
had
an
answer
from
kosuke:
it's
not
on
back
burner.
D
A
A
A
A
B
So
so
this
is,
your
question
is
from
linux
foundation.
Who
do
we
ask
for
help
on
the
cdf
story?.
A
B
B
A
We
have
a
new
ticket
that
I
want
to
put
on
top
rv,
as
I
mentioned
last
week,
created
an
issue
to
specify
how
to
have
two
azure
terraform
project,
one
for
the
azure
network,
including
the
dns,
the
virtual
network
and
the
other
for
the
azure,
like
what
we
worked
on
with
writing
the
ci
jenkins,
your
virtual
machine
and
other
pieces
of
infrastructure.
A
The
goal
is
that
by
splitting
into
projects,
we
should
limit
the
risk
of
us
breaking
down
the
entire
infrastructure
like
olivia
and
tyler,
and
issues
in
the
past.
That's
the
reason
why
they
stopped
automating
the
azure
infrastructure
management
with
terraform
and,
most
of
the
time,
it's
dns
and
sometimes
its
virtual
network.
Hence
the
need
to
have
two
separated
projects,
so
we
can
upgrade
infrastructure
as
code
under
azure
area
with
confidence,
whatever
the
whatever
kind
of
contributor
we
have
whatever
skills,
and
we
can
do
it
quite
often
without
being
slowed
down
by
fear.
A
There
is
already
a
lot
of
tasks
available.
Are
you
okay?
If
we
keep
that
one
on
top
of
the
back
burner?
But
we
start
once
you
will
have
worked
on
the
oracle
parts
which
mean
if
you
are
quick
enough
this
week
and
you
are
able
to
fulfill
all
the
tasks.
Don't
hesitate
to
take
that
task
additionally,
but
only
if
you
were
able
to
fix
the
current
milestone
is
that
okay
for
everyone.
A
A
D
C
D
D
I
had
another
questions
about
crodin.
Will
it
also
means
it
will,
will
the
current
translate
plugin
will
be
deprecated
or
uninstalled.
B
Not
not
really
because
they
are,
they
are
separate
and
independent
things.
So
you
can.
You
can
still
use
the
translate
plug-in
if
you
wish
it.
I
think
crowding
is
much
easier,
but
but
we,
what
we
hope
is
that
crowdin
will
become
the
de
facto
preferred
way
of
doing
translations,
because
it's
so
much
easier
for
translators
and
for
proofreaders.
D
I've
noticed
some
issue
on
it
like
it's
completely
unreadable
when
you
are
in
dark
mode
or
something
like
that,
but
it's
minor
or
the
translate
plugin:
okay,
so
yeah
yeah,
okay
and
for
the
crowding
yeah
I've.
I
have
just
have
some
suggestion
pending
on
it
on
his
pull
request,
I'd
like
to
add
a
localization
in
the
title,
holding
localization
project
or
something.
So
it's
a
little
bit
more
clear.
What.
A
B
A
Able
to
have
a
folder
with
specific
multi-branch
jobs
or
a
github
organization
scanning
on
update
on
infrasti
that
will
only
handle
the
update,
cli
pipelines,
as
per
suggestion
of
daniel
back,
we
could
use.
I
forgot
the
name
of
that
plugin,
where
you
define
one
jenkins
file
and
every
repository
with
a
token
file
will
use
that
jenkins
file
so
that
in
intermediate
between
github
organization
scanning,
where
you
need
to
define
a
jenkins
file
each
time
you
want
it
to
be
built
and
a
full
shared
library.
A
D
A
Was
working
a
few
hours
ago
and
it
was
mentioning
dev
optics
on
the
left
menu
which
confirm
it's
a
cloud
base
manage
something.
So
it's
not
under
our
area.
However,
the
docker
image
for
blue
shine.
We
might
need
your
help
mark
on
that
area.
I
remember
that
image
also
being
used
on
the
jenkins
dio
documentation
at
some
point
in
time,
not.