►
From YouTube: 2022 07 05 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
So
today
we
have
your
services,
so
everybody
is
not
there.
Mark
might
or
might
not
be
Stefan.
A
No
basil,
no
team
Mark
just
arrived
and
we
have.
We
know.
A
Numeric,
okay,
so
for
attendees
today,
let's
get
started
first
of
all
weekly
released.
Today
the
release
is
currently
on
Old
As
far
as
I
know,
the
reason
is
that
regression
has
been
detected
and
right
now
there
is
a
tentative
to
fix
that
regression.
So
the
regression
is
mainly
a
his
menu
related
to
websockets.
That
seems
to
be
not
working.
Slash,
remove,
slash,
not
behaving
as
expected
with
the
latest
GT
upgrade
I.
Just
realized
I
forgot
to
share
the
link
to
the
notes.
So
let
me
do
that
right
now,.
A
So
it's
an
old
team
and
team
and
Daniel
back
are
aware
of
that.
They
have
blocked
the
pipeline.
The
release
pipeline
to
be
sure
that,
even
if
it's
triggered
automatically
no
risk
so
great
exercise
for
us
to
see,
oh,
we
could
handle
better
in
the
future
the
security
release
when
we
want
to
disable
the
weekly
release.
That
could
be
a
a
good,
let's
say,
manual,
test
nothing
expected
from
the
infra
team,
so
it
was
just
for
UI.
A
The
team
will
should
handle
that
if
they
ask-
and
if
you
run
there,
you
don't
state
to
help
them,
but
that
should
be
okay.
We
didn't
change
anything
on
the
infra
as
far
as
I
remember,.
A
So
let's
get
started
with
the
task
that
we
were
able
to
close
and
finish.
Last
week
we
had
free
GitHub
permission,
I
entered
one
specific
version
Mark,
but
the
other
were
under
laser
by
Morocco
team.
A
One
password
reset
thanks
Mark
for
doing
that
so
user
at
the
need
to
reset
the
password
on
a
constant
in
Sayo.
So
we
try
to
to
gain
enough
Trust
on
the
user,
with
different
proof
before
being
able
to
reset
to
be
sure
that
there
isn't
someone
taking
it
over.
B
So
on
that,
actually
I've
got
a
a
technique:
I've
been
using
there
that
I'm
not
sure
if
others
want
to
use
it
or
not,
or
if
I
should
document
it.
I've
typically
found
what
their
GitHub
account
was
by
by
guessing
reverse
engineering,
Etc
and
then
ask
them
to
clone
Fork
a
copy
of
a
Jenkins
repo
into
that
GitHub
account
so
that
I
can
see
the
fork
it's
their
way
of
proving
they
have
control
of
it
and
and
then
they
just
delete
the
fork.
The
idea
was
okay.
B
B
A
Attempt
to
folk
Jenkins.
A
So
no
action
expected
from
us
so
thanks
LV
and
thanks
and
all
for
that
help.
A
We
helped
Adriana
to
set
up
a
pipeline
for
the
repository
plugin
scoring,
which
is
a
Google
summer
of
code
project
at
audience.
Monitoring.
So
since,
like
is
happy,
isn't
it
was
quite
classical
generating
a
jar
file
on
Docker
container,
with
test
container
modules
from
Maven
directly,
so
we
gave
him
documentation.
We
gave
him
technical
link
and
we
pointed
some
technical
element
on
documentation
and
they
are
they
configured
the
repository
with
success
on
cigen
Sayo.
A
A
Finally,
the
first
big
one.
We
add
that
we
completed
Stefan
and
I
worked
on
redirecting
the
domains,
the
for
the
Legacy
domains,
packages,
Jenkins
ci.org
to
pkgenkins.io.
A
We
had
a
lot
and
a
lot
of
issues.
Last
Friday
we
had
some
outages
on
the
few
minutes.
We
were
able
to
fix
it.
So
the
summary
is
that
when
we
have
a
website
Beyond
fastly,
we
have
to
ensure
that
the
hosts,
the
host
Adder
of
the
request
that
firstly
sends
to
the
back
end,
is
the
same
as
the
domain
that
firstly
used
to
connect
in
HTTPS
for
the
same
back
end.
A
For
instance,
in
that
case,
end
user
were
reaching
fasti
with
speaker,
G
Jenkins
IO,
while,
firstly,
configure
which
host
that
service
is
caching
PKG
origin.jenkins.io.
So
by
keeping
the
same
header
from
the
original
user,
Apache
was
cutting
the
connection
ending
on
a
terrible
HTTP
421
error.
That's
the
root
cause.
There
has
been
a
chain
of
events
and
changes
that
we
did.
The
good
thing
is
that
now
Stefan
and
I
understand
way
better.
A
We
ended
up
it's
not
written
there,
but
one
of
the
consequences
there
is
that
we
successfully
enabled
the
vagrant
manual
at
this
acceptance
testing
for
the
puppet
roll.
It
was
using
virtualbox,
which
made
it
impossible
for
team
or
Stefan
to
use
them
on
the
irm
Mac,
and
it
was
also
impossible
to
run
virtualbox
machines
on
the
CI.
Now
it
was
vagrant
with
Docker,
which
means
we
have
a
lot
of
new
use
case.
It's
clearly
powerful
and
it
works
with
internal
diagram
flawlessly.
A
A
So
thanks
for
the
help,
because
I
wouldn't
have
I've
spent
only
one
day,
I
think
that
would,
without
your
help,
Stefan
I
would
have
spent
the
whole
weekend
on
that
tricky
one.
So
thanks
a
lot
yeah
first
either
an
scene
I
must
be
the
same,
allowed
us
to
improve
puppet
for
Grant
with
Docker
now.
A
A
C
A
Okay
are
done
post
mortem,
so
can
you
summarize
the
issue
we
had
the
main
issue.
C
A
And
so
as
your
file
is
like,
Amazon
is
free:
it's
not
a
block
device.
It's
a
files.
It's
a
file
bucket
there,
as
as
you
change
the
implementation
to
CSI,
and
the
thing
is
that,
despite
the
challenge
log
telling
us
that
it
should
be
transparent
each
time,
kubernetes
Mount,
these
buckets
kubernetes
generates
a
temporary
token,
its
name
SAS
token,
which
is
encrypted
with
a
private
SSH
private.
Key
that
token
change
on
each
Mount
remote.
A
A
So
that
created
a
one
hour
outage
on
the
ldap
and
on
the
mirror
download
system
Gadget
inside,
so
that
requires
quite
the
impact
and
so
need
to
migrate.
So
the
postmortem
takes
some
improvement
on
the
procedure
next
time,
so
the
we
can
close
the
tissue
once
the
upgrade
to
kubernetes
1.23
issues
will
be
written
by
Stefan
and
Darby,
based
on
the
previous
one,
the
Improvement,
the
changes
for
the
procedure,
because
some
we
need
some
enhancements
somewhere
and
some
things
outdated.
A
So
we
also
need
to
write
the
next
upgrade
issue
based
on
what
we
learned
and
finally,
with
the
postmortem
that
should
be
a
consequence
of
the
postmortem,
but
I
can
already
say
that
we
need
to
migrate
the
AKs
persistent
volumes
to
the
new
CSI
driver
yeah,
so
everybody
that
is
with
that
I
think
Stefan
Navan
Knight
a
global
idea.
So
that
was
the
last
big
task
that
we
need.
A
A
Next
one
consider
removing
embeddable
status
plugin,
so
that's
a
plugin
that
has
been
required
to
be
removed.
The
thing
is
that
it
might
broke
the
readme,
your
documentation
of
some
users,
of
some
brilliant
users.
I,
don't
remember
someone
checked
I,
think
Mark
checked
that
there
has
yeah.
We
have
169
plugins.
A
So
by
courtesy
to
these
users,
we
will
remove
that
one
from
cig
and
kinsayu
the
public
facing
website
ones,
who
will
have
opened
a
bunch
of
pull
requests
on
this
on
this
document
on
these
elements,
Airways
was
working
on
that
part
before
the
long
weekend,
so
he
found
a
tool
that
allow
us
to
batch
pull
request,
opening
to
a
given
repo
and
the
other
tool
that
does
some
kind
of
regex
but
simpler
search.
So
it's
a
kind
of
super
sad
but
easier
to
use.
So
now
he
has
to
assemble.
A
C
A
A
Still
ci.genkins
dot
only
CI
Jenkins
are
you
left.
Can
I
ask
you
to
add
the
link
of
the
next
issues,
please,
while
I'm
trying
to
take
notes?
Yes,.
A
A
A
As
a
dependency
on
administrator
on
the
Jenkins
organization,
so
I
think
we
will
ask
for
help
to
Tim
and
Danielle
to
see
if
they
can
start
this
with
the
help
of
gems,
because
I
understand
the
requirements
but
yeah
we
need
the
Girard
mean
and
the
Jenkins
admin
which
we
are
not.
For.
The
second
point.
A
A
A
Yes,
that
there
is
a
correlation
provide
both
Powershell
and
pwa
Sh
and
religion
templates,
it's
in
production
for
virtual
machines,
and
there
are
ways
to
do
it
on
the
docker
images.
A
Reminder
that
task
quest
to
be
sure
that
we
don't
end
user,
don't
have
to
choose
between
both
keywords
on
their
Pipeline
on
Windows
environment,
because
one
is
the
old
Powershell
the
old.
The
second
is
the
recent
Powershell.
Some
some
machine,
as
both
submission,
has
only
one
of
two.
So
the
goal
is
to
provide
an
alias
or
solution
on
each.
A
So
far,
no
one
complained
as
far
as
I
as
I
know
from
the
last
week,
release
that
is
the
first
one
that
dropped
gdka,
8
support,
or
maybe
people
who
didn't
read
the
change
log,
but
that's
not
there
is
there,
isn't
anything
we
can
do
about
that.
No
expectation
from
the
team
for
now,
let's
keep
an
eye
on
this
one,
so
sorry
which
one
required
Java
11
infrastructure,
okay,.
C
So
I
don't
put
that
to
the
next
Milestone
I
put
that
on
on
Alpha
Team
sync
Nest.
Next.
C
A
C
C
Oh,
that's:
that's
a
very
nice
one,
I'm
working
on
the
terraform
part
and
yesterday
and
today
I
was
bumping.
My
head
on
the
the
access
on
SSH
I
thought
that
was
a
firewall
problem
definition.
In
fact,
no
that
was
a
getaway
and
rule
for
the
getaway
problem.
C
It's
working
since,
like
an
hour
launching
spawning
the
the
VM
and
I
can
access
it
by
SSH.
We
still
need
to
clean
it
up
a
little
and
to
make
sure
we
got
all
the
good
users
to
use
within
the
VM.
But
it's
it's
going
forward,
not
easy,
but.
A
C
B
A
A
A
The
goal
was
a
full
autonomy
on
the
terraform
infra
Parts,
but
for
the
puppets
we
might
need
to
do
it
the
two
of
us
because
of
the
priority,
because
we
really
need
to
move
this
to
move
forward
on
those
topics.
No
problem.
B
A
I
can't
expect
you
to
be
a
terraform
expert
and
a
puppet
expert
under
local
expert
and
all
of
these
at
the
same
time,
so
no
problem,
it's
only
that's
that
one
is
required
because
of
the
cost.
No
problem.
A
Any
question:
no
okay,
next
topic,
Docker
Uber
rate
limiting
I,
didn't
have
time
to
do
anything
so
until.
A
Nothing
done
yet
replacing
oh
I
forgot
to
ask
Mark
statues,
so
we
move
it
automatically
I
ping,
the
mark,
since
after
last
week,
meeting
the
cpuc
agent
is
still
not
available.
It's
not
really
a
problem,
but.
B
A
A
Okay,
Mark
wait,
wait,
CI,
Jenkins,
IO
test
are
very
flacky,
so
we
need
to
start
working
on
this
one
along
with
502
proxy
01x,
simple
request
on
Jenkins
CIS
chain
kit.
So
both
issues
are
on
CID
and
kinsayo.
The
public
instance
the
big
one,
the
flakiness
of
Agents.
A
A
So
the
thing
is
that
these
problems
happened
either
during
the
kubernetes
upgrade.
We
have
a
new
kubernetes
version,
so
that
might
change
things
at
the
networks.
Part
and
also
we
add
the
updates
and
PKG
issues
so
that
my
that
could
have
been
a
cost.
However
Joseph
Patterson
just
edited
like
yesterday,
some
issue
opened
so
it
looks
like
we
have
agent
that
cut
the
connection.
All
these
agent
are
kubernetes,
so
we
might
need
some
help
on
that
area,
but
also
most
of
them
are
related
to
the
bum.
A
The
infamous
bomb
builds
which
spawn
100
of
80.
It
need
an
180
executors
and
we
only
have
150
elements.
So
I'm
gonna
try
to
write
on
different
elements
on
this
one,
but
right
now:
yes,
it's
quite
annoying.
So
what
solution
do
we
have
right
now?
First
of
all,
the
Jenkins
is
waiting
a
lot
trying
to
create
virtual
machines
that
as
a
public
IP,
but
we
reach
the
limits
due
to
Docker
rate
limiting.
A
A
Secondly,
we
need
to
start
again
the
metrics
and
traces
subject
on
cig
and
kinsayu.
So
I
will
need
someone
on
the
upcoming
weeks
to
take
back
the
try
to
restart
the
discussion
with
elastic,
so
we
can
create
an
instance
of
their
open,
Telemetry
SAS
system.
So
we
can
connect
the
agent
in
sayon.
We
will
have
traces
of
the
build,
so
we
can
see
what
could
happen
in
terms
of
timing.
C
A
Us
that
that's
different,
that's
a
different
topic.
We
need
open
Telemetry
data
could
do
open
Telemetry,
but
the
thing
is
that
we
have
elastic
proposing
to
sponsor
us
so
that
a
double
release
sponsor
us.
So
the
we
will
want
to
use
data
dog
for
the
private
instances
such
as
infrasia
or
release
CI.
So
we
could
get
traces
from
our
work
because
data
dog
is
by
default
private,
that's
only
our
access
and,
for
the
public
part
elastic,
provides
the
public
dashboard.
So
the
idea
is
to
split,
and
so
with
split
roads.
A
We
have
a
comparison
and
we
use
both
perfect.
But
yes,
that
log
also
has
a
service,
and
the
question
is
which
one
to
choose-
let's
say
both,
but
we
need
one.
A
A
A
More
container
and
capacity
in
digitalism,
so
with
all
these
tiny
elements
that
should
keep
us
for
the
next
week,
then
the
the
thing
is
that
if
we
aren't
able
to
solve
this
flakiness
because
it's
hard
to
understand
what's
going
on,
then
in
that
case
we
will
have
to
ask
some
for
help
from
Danielle
or
Bazil
or
any
experts
give
them
access
on
someone
that
a
developer
of
the
core
that
helped
us
going
on
that
direction.
A
A
So
we'll.
Let
me
have
an
answer
for
the
next
two
weeks
set
of
minor
changes
being
to
understand
what
is
going
on
because
I
don't
know
that
request
aborted
exception.
It's
like
I,
don't
even
know
we
need
better
observability
I.
A
I
have
no
idea
how
to
deal
with
that
thing.
I
mean
that
instance
is
almost
unmanageable.
I
will
strongly
suggest
creating
a
cig
and
kitayo
from
scratch
on
kubernetes,
because
we
will
benefit
from
Full
configuration
code,
improve
manageability
without
using
a
puppet
not
having
to
split
our
configuration
systems,
and
then
we
could
benefit
from
all
the
kubernetes
log
collection
and
all
these
opportunities
which
we
don't
have
today.
A
So,
let's
see,
maybe
we
can
have
a
boom.
C
Specific
controller,
which.
A
Is
yes
also,
since
we
have
weekly
that
could
be
a
way
to
move
around
that?
That's
a
good
point!
That's
a
good
idea!
That's
really
good
idea!.
A
So,
let's
see
we'll
try
to
discuss
that
on
the
upcoming
weeks.
So
let's
keep
all
an
eye
on
this,
but
yeah
CI
Jenkins
might
be
yeah
there
is
that
issue
we
haven't
been
able
to
work
on
it.
Yet
when
you
go
and
see
again
Sayo
to
the
Jenkins
score,
if
you
try
to
go
to
the
pull
request
tab,
you
end
on
the
502.,
because
it
takes
so
much
time
to
install
the
pull
request.
I.
B
A
Know
why
we
have
to
check
what
Daniel
checked,
but
we
reached
the
timeout
between
the
frontal
Apache
and
the
back
engine
kits.
If
you
need
to
see
that
as
an
administrator,
you
can
open
a
SSH
tunnel
to
the
CI
VM
and
then
you
can
see
it.
You
just
have
to
wait
longer.
A
B
A
C
A
That's
that
one
and
so
I'm
updating
the
notes
and
let's
go
go,
keep
forward.