►
From YouTube: 2021 06 08 Jenkins Infra Meeting
Description
Jenkins infrastructure meeting June 8, 2021.
A
Hi
everybody
and
welcome
for
this
new
jenkins
infrastructure
meeting.
We
had
a
quite
busy
week
so
we
have.
We
have
a
few
things
on
us.
The
first
one
is.
We
are
planning
to
upgrade
the
committees
cluster
that
we
are
running.
We
won't
upgrade
from
version
1.18
to
1.19,
we'll
work
on
it
on
friday
to
first
identify
potential
issues,
and
if
it's
depending
on
the
situation,
we
may
also
jump
directly
to
1.20.
A
So
that's
that's
the
current
state.
We
just
want
to
be
conservative,
as
we
don't
want
to
break
too
many
things.
We
have
the
jenkins
contributor
submit
in
three
weeks,
so
we
don't
want.
We
want
to
be
sure
that
we
don't
introduce
potential
issues
before
the
event.
So
that's
why
we
are
starting
now.
So
the
plan
is
we
work
and
we
prepare
it
on
friday
and
then,
depending
on
the
outcome,
we
do
the
upgrade
next
week
more
to
come
in
terms
of
event,
what
happens?
We
had
several
issues
in
the
abundance,
but
still
several
issues.
A
It
appears
that
it
appeared
that
g
frog
who's,
maintaining
that
service
did
an
upgrade
and
the
ips
changed
and
we
needed
to
unload
so
those
ips
in
our
adapt
configuration
in
order
to
authenticate,
so
we
needed
to
identify
which
ips
needed
to
be
added
and
then
now
it's
working
correctly.
So
I'm
currently
writing
a
postmortem.
If
you
want
to
have
more
details,
I'll
publish
apartment
past
more
time
on
chickens
infrastructure
document,
documentation
repository.
A
The
second
thing
that
I
want
to
mention
is
recent
changes.
Recent
change
to
the
service
to
the
mirror
infrastructure
get
the
jenkins
that
I
o,
so
I
I
had
to
I
had
to
configure
archive
to
jenkins
in
order
to
be
available
on
our
air
sync
in
rhythm
modes,
before
adding
it
to
mirror
beats,
which
is
the
case
now
so
now,
if
you
do
whatever
request
to
get
the
jenkins
that
I
o,
you
are
always
redirected
to
rbr,
which
is
pretty
important
so
now.
The
next
step
is
to
first
add
more
mirror.
A
And
we
also
identify
a
few
ways
to
improve
the
performance
of
the
of
the
service,
but
at
least
now
it's
working
correctly,
which
is
great
next
topic,
is
about
the
various
issues
we
had
with
ci2,
so
we
discovered,
I
mean
we
had
two
main
outages
with
sei,
so
we
are
using
azure
containers
container
instances
to
run
some
some
jobs,
so
basically
jenkins
provision,
those
containers
run
and
build,
and
test
plugins,
for
instance,
and
for
some
reason
we
were
not
able
to
use
those
those
ci.
So
maybe
demand
can
provide
more
feedback
here.
B
Yes,
so
two
kind
of
issues,
the
most
frequent
one
is
related
to
aci.
We
had
two
intervention
in
eight
days:
that's
not
the
first
time.
So
there
is
a
bunch
of
issues
related
to
the
azure
plugin
that
are
fixed
by
team
yakum
thanks
for
that
on
the
go
which
helps,
but
still
we
are
seeing
a
lot
of
azure
api
issues.
So
the
idea
is
that
we
should
not
depend
only
on
aci
because
when
it
work,
it's
really
efficient,
because
the
agents
start
very
fast
and
provide
good
performances.
B
B
B
It
seems
that
in
the
past
it
was
related
to
pure
infrastructure
issues,
time
desynchronization
between
controller
and
agents,
a
disk
which
is
full
not
enough
memory
for
the
gvm.
None
of
these
symptoms
were
present
during
the
past
days.
We
controlled
that
and
still
there
are
still
happen.
One
of
the
direction
here
and
short
point
action
will
be
to
switch
to
web
socket
agents,
but
this
needs
some
work
to
be
done
on
cig
inside
your
reverse
proxy.
So
that
might
not
be
a
short
term
improvement
right
now.
A
Thank
you.
Damien
made
some
effort
to
write
the
post
martem,
so
there
are
two
places
where
you
can
find
them
so
either
we
consider
a
postmortemous
archive
which
means
that
we're
not
expecting
any
modification,
then
those
fourth
muslim,
post
mortem
or
publishing
jenkins
infrastructure
documentation
under
the
directory
postmortem
and
there
you
can
see
only
two,
because
that's
only
the
beginning
of
that
procedure,
and
so
we
try
to
fill
out
a
template.
So
we
have
a
timeline.
A
So
it's
loading
and
so,
for
instance,
those
are
the
post
martin
that
you
are
currently
working
on
sorry,
and
so
you
can
see
specific
one
for
repo
jenkinsia.org,
aci
agent
and
so
on.
So
the
way
it
works
is,
if
you
want
to
provide
some
feedbacks
review,
you
just
have
you
need
to
be
able
to
have
you
need
the
link,
but
there
are
there.
Are
everybody
should
be
able
to
read
them?
And
if
it's
not
the
case,
then
you
should.
A
Then
it
means
that
we
have
things
to
improve,
but
we
usually,
as
I
was
saying,
we
usually
follow.
So
we
specify
chronology.
What's
the
the?
What
was
what
what
was
impact
of
the
issues
and
what
went
wrong
and
so
on,
and
so
we
started
doing
this,
and
so
once
the
document
is
ready.
We
push
the
document
on
the
on
the
on
the
key
repository.
So
that's
the
way
we
are
working
at
the
moment.
It's
just
easier
to
explain.
Technical
issues
feel
free
to
provide
any
feedback
to
that
workflow.
A
A
A
A
Sounds
like
my
machine
is
just
very
slow,
but
you
can
build
the
status
page
from
here.
We
work
with
pull
requests
and
so
on.
So
that's
where
it
works.
So
if
we
have
an
incident,
we
start
first,
we
publish
the
incident
on
the
status
page
once
the
incident
is
closed.
We
write
a
postmortem.
We
usually
communicate
on
the
mailing
list
as
well
and
once
we'll
be
more
confident,
we
may
start
using
this
course,
but
yeah.
Those
are
just
improvements.
If
you
have
any
money,
you
want
to
bring
feel
free
to
to
share
them
with
us.
A
So
it
sounds
like
we
are
good.
We
just
have
some
cleanup
to
do
in
the
notes,
but
it
sounds
like
we
are
good.
So
we
have.
I
identify
three
main
action
point.
The
first
one
is
to
communicate
about
the
communities
upgrades
that
will
happen
next
week.
Again,
we'll
start
working
on
that
upgrade
by
the
end
of
the
week.
I
would
like
to
write
a
blog
post
on
the
mirror
infrastructure
that
we
have
now
it's
relatively
stable.
A
A
So
in
this
case,
in
my
case,
it's
pretty
obvious
because
I'm
quite
far
from
that
yellow,
but
I
ran
some
exercise
from
a
proxy
located
in
the
us,
and
I
got
confirmation
that
if
another
mirror
is
available,
then
you're
always
redirect
to
that
one
and
what
I
used
to
confirm.
My
thoughts
was
looking
at
the
stats,
so
we
have
access
to
stats
for
every
house,
those
that
are
reset
every
day
and
so
for
every
mi
house.
You
have
two
lines.
So
let's
say
it's
mission.
You
have
the
first
nine,
the
dark
blue.
A
You
can
see
the
number
of
downloads
that
happen
on
that
specific
mirror
and
then
the
second
light
in
the
line,
the
light
blue.
It
shows
you
how
many
data
were
transferred
on
that
specific
ground.
So
in
this
case
it's
two
terabytes,
then
net
was
almost
one
terabyte
and
and
so
on,
and
so
what
I
want
to
be
sure
is
archive
the
junkies
that
I
remain
not
used.
So
this
time
it's
700
gigabytes,
which
is
acceptable,
I
think
but
yeah.
A
This
is
something
that
we'll
have
to
monitor
in
the
future,
but
I
would
like
to
write
blog
posts
on
this
topic
and
damian
will
keep
working
and
stabilize
ci
the
jenkins
that
I
use
to
to
use
communities,
agents
on
top
of
aci
agents.
Any
last
topic.
The
main!
Do
you
want?
Do
you
have
anything
else
you
want
to
bring
here.
B
Advice
or
if
you
have
a
ci
jenkins,
you
are
your
user
and
you
see
issues,
don't
hesitate
to
report
them
as
soon
as
possible
on
irc
and
don't
stay
to
propose,
help
or
ideas.
If
what
we
provide
does
not
fit
your
needs
or
if
you
see
too
much
issues,
we
are
there
to
improve
the
service,
so
don't
say
to
give
feedback.