►
From YouTube: 2021 10 15 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
Hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting
so
yeah
in
terms
of
activity.
It
was
a
pretty
calm
week.
So
the
first
topic
that
I
want
to
cover
is
the
amazon
account
that
we
are
using
in
the
jenkins
project.
As
a
reminder,
we
have
two
main
costs.
There
are
the
machine
package
searching
kinsaleo
and
the
second
one
is
the
ci
environment
for
the
agent
for
ci,
the
jenkins
leio,
with
the
work
that
damien
has
been
doing
on
ci
dodge
installation.
A
We,
we
transfer
part
of
the
cost
from
the
azure
account
to
to
amazon,
and
we
are
now
investigating
ways
to
reduce
the
cost,
because
the
last
month
was
50,
50
000
dollar
for
the
for
this
month,
and
obviously
we
have
to
put
down
that
that
that
invoice.
So
we
are
currently
looking
for
ways
to
reduce
the
costs
and
yeah.
Basically
that
that's
it.
If
you
have
ideas,
want
to
contribute,
we.
B
C
An
increase
on
ci
junk
inside
io,
mainly
since
the
beginning
of
the
summer,
the
issue
infra
1397,
has
a
bunch
of
details,
have
extracted
a
lot
of
the
costs
to
cover
difference.
There
are
different
rules
proposed
to
go.
It's
just
an
information
if
you're
interested.
If
you
want
details
that
should
be
a
specific
topic,
but
it
means
that,
on
top
priority,
the
the
issues
associated
to
date
to
that
epic
will
be
taken
on
the
most
prior
item
for
the
three
upcoming
weeks,
the
goal
being
trying
to
decrease
the
cost
as
soon
as
possible.
Okay,.
A
B
A
Okay,
yeah
exactly
so
we,
as
I
mentioned
most
of
the
cost,
is
related
to
ci.
The
jenkins
that
I
o,
because
we
are
using
the
amazon
accounts
to
run
jobs
there,
and
we
are
now
trying
to
investigate
the
best
way
to
reduce
the
cost,
either
reducing
costs
for
other
services,
such
as
package.
Touching
things
like
you
are
better
use
agents,
and
so
that's
really
the
beginning
of
the
the.
B
C
C
And
a
special
thanks
for
jc
glick
to
help
us,
he
gave
us
reminders,
ideas
and
the
double
you
tend
to
double
check.
Most
of
the
changes
we
do
on
the
ci
port.
So
that's
really
cool.
A
A
While
we
are
last
question
regarding
the
costs,
so
while
we
are
discussing
an
amazon
cost,
I
would
like
to
continue
the
discussion
of
about
package.
I
think
that
are
your
machine,
because
yeah,
because
that's
a
package
of
jenkins
leo,
is
the
machine
which
hosts
the
service
updates,
touching
things
that
are
your
package
touching
the
leo
and
behold
jenkins
here.,
which
is
deprecated
as
a
reminder.
This
machine
is
not
synchronized
with
puppet
anymore,
so
it
became
a
snowflake
and
because
we
are
looking
at
the
cost
on
amazon.
A
C
At
sorry,
the
costs,
the
cost
of
the
machine
is
not
that
much.
The
cost
of
the
outbound
transfer
from
that
machine
is
a
lot
that
machine
emits
50
terabyte.
A
So
it
does
not
represent
the
major
cost
in
the
amazon
accounts,
but
the
cost
is
significant
to
find
a
better
solution
for
that
service.
So
we
started
looking
at
it
with
damien
sorry,
yeah.
A
That's
one
of
the
ideas:
okay,
that's
one
of
the
idea.
The
reason
for
that
is
because
that
machine
is
really
critical
for
the
jenkins
project,
because
that's
where
we
package
artifacts,
we
are
currently
maintaining
mostly
by
hands,
which
is
I
mean,
that's
really
comfortable
and
it
represents
the
cost
so
just
to
give
an
idea
because
of
the
because
of
the
network.
Bandwidth,
that's
happened
on
that
machine.
We
have
to
use
a
pretty
big
machine
like
62
64
gigabyte
of
ram.
A
I
can't
remember,
but
in
the
end
it's
many
an
apache
machine,
so
the
machine
is
just
way
oversized
for
what
it's
doing,
except
that's
the
the
network
bandwidth.
So
we
definitely
have
some
optimization
to
do
there
on
top
of
yeah
better
managing
it.
So
that's
something
that
will
start
looking
in
the
coming
weeks
or
to
see
how
we
can
improve
but
yeah.
It's
always
it's
all
related
to
the
amazon
costs.
A
Next
topic
that
I
think
damien
put
in
the
agenda,
which
is
a
traffic
ingress
controller,
so
we
had
some
recent
activities
on
github,
where
jsf
peterson
was
interested
to
contribute
to
the
increased
resources
that
we
use
on
the
jenkins
infrastructure
project,
as
daemon
mentioned.
I
think
it
would
be
better
to
start
with
a
private
ingress
controller.
A
I
think
it's
it's
something
that
would
be
nice
because
we
have
to
update
ingress
resources
anyway
for
the
next
major
communities
upgrades
they
mean
tell
me
if
I'm
wrong,
but
so
yeah,
that's
something
that
you
have
to
do
now,
because
it's
it's
mandatory
for
the
next
I
mean-
maybe
not
yet
for
the
moment,
it's
not
yet
mandatory,
but
it
will
be
needed
to
for
the
communities
version
1.22,
which
is
coming.
C
That's
a
topic
that
have
been
proposed
by
olivia
joseph
at
the
beginning
of
the
year,
but
since
joseph
had
a
lot
of
a
lot
of
bandwidth
already
taken
and
because
that
change
does
not
map
to
direct
feature
to
end
users,
it
will
be
more
it's
a
kind
of
investment
in
the
future
to
make
us
more
portable
in
kubernetes
area,
because
traffic
has
less
specific
annotation.
Even
with
the
new
ingress
model,
you
still
have
specific
items
by
using
traffic,
we'll
have
something
that
cost
less
in
terms
of
resources.
C
C
But
if
joseph
is
willing
to
work
on
that,
that
could
be
a
cool
contribution,
and
so
the
idea
is,
let
him
walk
and
see
if
we
have
a
nice
outcome
and
if
we
are
able
to
switch
from
engineering
to
traffic,
at
least
for
the
private
ingress,
meaning
every
service
is
behind
the
vpn.
For
us,
that
will
be
the
next
milestone
and
we
can
do
a
retrospective
once
we
are.
There.
A
So
as
a
reminder,
I
just
want
to
show
what
what
we
mean
by
updating
the
engine,
the
ingress
resources.
So
let's
say:
let's
take
this
one.
I
think
we
have
an
us
template
here
and
ingress
so
yeah,
it's
not
really
useful,
not
as
much
as
I
wanted
to
show
you,
but
we
are
so
yeah
it's
just.
We
are
still
using
the
old
annotation
for
the
ingress
resource
and
we
have
to
update
to
the
new
one
anyway,
so
we
can
take
that
opportunity
to
switch
to
traffic.
A
That's
the
idea.
We
are
currently
running
kubernetes
1.19.
We
have
an
upgrade
to
1.20
coming
pretty
soon.
The
thing
is
the
this
annotation
this
this
structure,
this
ingress
resource,
is
deprecated
in
version
1.22.
C
A
A
A
Next
topic
that
I
put
due
to
the
agenda,
I'm
not
sure
if
it's
something
that
should
be
discussed
here
or
during
the
governance
meeting,
but
considering
the
recent
priority
change.
I'm
just
wondering
if
we
should
just
update
the
roadmap
to
highlight
the
work
that
we
need
to
do
on
the
amazon
accounts.
A
And
also
something
that
we
totally
forgot
that
I
forgot
to
mention
regarding
the
amazon
accounts.
We
need
to
reduce
the
cost,
that's
one
of
those
things
that
we
need
to
do,
but
there
is
a
second
thing
which
is
transfer
that
amazon
account
to
the
cdf,
because
right
now,
that
account
is
maintained
by
club
b's.
So
cloud
b
is
paying
the
bill,
which
means
that,
in
order
to
access
that
account,
you
need
to
be
a
cloud-based
employee.
A
So
it's
not
really
convenient
to
collaborate
with
non-cloud-based
employees
on
that
account
and
cloudbase
is
interested
to
not
be
responsible
for
that
account
anymore
as
well.
So
that's
why
it
will
become
a
priority
for
us.
C
A
Next
topic
is
about
trading
issues,
so
we
have
quite
a
lot
of
issues
in
the
jira
projects
we
started
this
week.
I
mean
we
started
several
weeks
ago,
but
more
this
week,
closing
all
tickets.
So
if
you
have
some
time,
that's
really
useful
to
just
go
to
the
open
ticket
and
just
close
those
that
are
not
relevant
anymore
are.
A
We
are
closing
as
much
as
we
can,
but
we
still
have
a
lot
of
a
lot
to
do
and
still
on
the
issue
topic,
we
got
access
to
the
github
issues,
so
we
have
access
to
the
beta
gw
shoes,
so
we
can
now
have
a
project
across
every
kitchen
repositories.
I
mean
that
that
was
already
a
case
in
the
past,
but
we
just
have
access
to
more
feature.
A
I'm
not
really
familiar
with
the
new
the
new,
the
new
feature,
so
I
still
have
to
play
it
a
bit
with
that
but
yeah.
If,
if
you
are
comfortable
with
with
it,
some
some
feedback
would
be
greatly
appreciated.
C
And
also
under
issue
3h,
something
that
olivier
v
and
I
discussed
this
morning-
is
that
we
saw
we
had
we
use
and
we
still
have
a
lot
of
support
like
issue
from
end
user.
That
ends
up
on
the
infra
project
in
jira,
mostly
because
we
don't
really
provide
anjira
to
a
user
opening
a
new
issue,
an
easy
path.
That's
that's
clearly
underlined
that
infra
project
is
only
aimed
at
the
jenkins
infrastructure.
C
C
So
if
anyone
has
the
skills
or
knowledge
on
jira
to
help
us
on
something,
we
could
do
on
that.
That
will
help
a
lot
the
issue
triage
and
that
will
help
a
lot
people
opening
issues,
because
most
of
the
time
we
they
have
to
wait
for
us
to
pick
the
issue
and
see
so
there
could
be
an
improvement
there.
For
our
end
users
that
report
issues
there.
A
Yeah,
most
of
the
time
we
have
a
lot
of
people
opening
issues
that
are
not
I
mean,
which
are
that
have
nothing
to
do
with
infra
and
and
from
time
to
time.
We
we
see
someone
who's,
I
mean
not
knowledgeable
about
the
champions
project
and
still
open
issues
in
the
wrong
project.
So
that's
why
we
are
thinking
that,
maybe
it's
not.
I
mean
clear
enough.
A
The
last
topic
that
I
have
to
the
agenda
so,
which
is,
I
see
a
lot
of
discussions
about
algolia
and
doc
search.
There
is
something
that
I
don't
understand,
because
algolia
is
sponsoring
the
jenkins
project
for
plug-ins
such
a
kids
layout.
So
we
have
like
1
000
credits
that
we
can
use
and
it's
used
in
the
previous
bringing
the
gentlemen's
video.
B
So
they're
two
very
different
approaches
and
for
for
very
for
what
I
think
are
valid
reasons
that
they
are
different.
Algolia
offers
a
pro
a
product
to
open
source
projects
called
doc
search
and
that
product
will
index
a
site
and
then
all
the
open
source
project
does
is
inserts
a
javascript
snippet
into
their
pages,
and
that
makes
the
search
accessible.
B
B
What
we
did
today
was
open
a
support
ticket
to
see
if
they're
willing
to
extend
what
it
could,
what
it,
what
it
indexes.
Okay,
that
makes
sense
now
plugins.jenkins.io,
is
different
and
they
recommended
actually
that
it
remained
different.
They
recommended
it
be
different,
because
plugins.jenkin.io
is
largely
data-driven
and
because
it's
data-driven,
a
text-based
indexing
system
isn't
as
effective.
B
C
B
B
A
Awesome
thanks
for
your
time,
then
I
propose
to
stop
the
meeting
here
have
a
great
weekend.
Goodbye.