►
From YouTube: 2021 01 05 Jenkins Infra Meeting
Description
Jenkins infrastructure meeting January 5, 2021 with topics including an overview of the infrastructure results from 2020, a discussion of Infrastructure docker image generation improvements, and a review of progress generating LTS release candidates from release.ci.jenkins.io
A
A
Can
you
see
my
screen
so
basically,
yep
perfect
sounds
good,
so
so
what
I
wanted
to
to
remind
to
remind
us-
and
what
to
look
at
we
did
over
the
last
year-
is
to
keep
in
mind
that
the
jenkins
infra
project
is
an
open,
infra
project
where
everybody
is
invited
to
participate
to
contribute
to
learn,
and
so
I
wanted
to
look
at
what
are
the
things
that
we
did
that
improve
that
over
the
last
few
years.
So
the
first
thing
that
we
did
was
the
way
we
organized
this
meeting.
A
A
I
had
a
look
this
morning
and
we
wrote
65
pages
of
notes,
which
is
quite
impressive,
and
a
year
ago
we
did
another
milestone,
which
was
to
record
this
meeting,
so
other
people
could
follow
what
we
were
doing
here,
which
is
I
was
I
mean
I
was
really
happy,
and
I
wasn't
expecting
that
when
I
started
working
on
on
these
projects.
Another
thing
that
I
looked
at
was:
what
are
the
stats
that
kids
can
tell
us,
so
everything
is
public.
Most
of
our
code
is
on
the
kits
on
the
jenkinson
for
organization.
A
A
So,
while
people
initially
started
contributing
to
the
jenkins
infra
project
from
the
united
states,
when
you
see
under
the
craft
that
I
have
here,
we
start
to
see
more
people
on
the
european
time
zone,
which
kind
of
makes
sense,
with
teams
team,
jacob
leigh,
and
I
so
yeah
that
was.
I
was
really
happy
to
see
that,
because
it
accelerates
the
feedback
loop
and
when
we
look
at
the
top
kick
repositories
we
can
also.
I
don't
know
if
you
can
see
the
the
the
information
I
know.
A
A
Another
thing
that
I
wanted
to
share
with
you
is
the
way
we
we
financed
the
jenkins
infra
project
and
how
big
that
infrastructure
is.
So
we
don't
receive
money,
so
everything
is
running
based
on
sponsoring.
We
have
many
different
kind
of
sponsors.
Some
provide
monthly
budgets
that
is
renew
every
month.
Other
provide
a
big
amount
of
money.
A
Let's
say
for
a
year,
and
some
sponsor
just
says
you
can
use
whatever
you
want
on
our
platform
and
just
it's
it's
free
for
you
at
least
what
I
was
able
to
monetize
is
we
spent
more
than
two
thousand
dollar
on
the
infrastructure
over
the
last
year.
Obviously
I
mean
it's
more
because
stuff
like,
for
instance,
tata
dog,
is
free,
so
we
have
no
visibility
on
how
much
we
would
have
to
pay,
for
they
said
datadog,
chief
frog
or
ibm,
so
it
just.
A
A
Another
major
website
that
I
did
not
consider
is
here
is
the
update
center,
because
I
don't
I
mean
we,
we
use
google
analytics
and
we
use
google
search
console
on
the
main
website
and
plugins,
but
we
don't
really
have
easy
ways
to
collect
stats
on
the
update
center,
so
I've
voluntarily
avoided
to
spend
too
much
time
here.
So
the
first
one
is
the
main
website.
A
When
we
look
at
the
google
analytics
information
that
we
have
here,
we
can
see
that
the
number
of
people-
the
number
of
visitors
over
the
last
year
was
more
than
6
million
of
user
visitors,
which
increased
by
almost
30
percent
compared
to
the
year
before,
and
when
we
look
at
where
those
people
are
coming
from,
we
I
mean
it's
not
a
major
surprise
here,
north
of
america,
western
europe,
eastern
asia.
Those
are
the
continents
where
most
of
the
visitors
are
coming.
A
We
started
so
they
started
sponsoring
us
in
march
last
year,
and
so
the
kind
of
information
that
we
have
there
is
in
terms
of
network
bandwidth,
what
we
are
using
there
and
what
is
interesting
here
is
it's
an
average
by
day.
So,
since
june,
we
had
by
an
average
1.3
million
of
requests
done
on
the
main
website
per
day,
and
we
had
almost
30
gigabyte
of
transfer
the
network
transfer
per
day
on
related
to
the
main
website,
which
is
quite
impressive
for
a
project.
C
A
A
We
also
have
pipeline
docker
by
applying
jkins
file.
What
you
can
see
here
that
you
have
to
keep
in
mind
is
we
started,
I
think,
in
september,
we're
starting
to
use
www.jenkins.edu
by
default,
so
we
still
have
some
stats
only
for
the
top
domain,
which
is
which
was
I
mean,
which
is
checking
that
I
o.
A
When
we
look
at
the
stats
for
the
plugin
site.
We
don't
have
google
analytics
on
the
plugin
site,
but
we
still
have.
We
could
still
look
at
fastly
and
what
fastly
tell
us
is.
We
also
have
quite
a
lot
of
traffic
per
day,
so
we
have
17
gigabytes
of
by
transfer
every
day
on
average
since
june,
almost
700
000
requests
done
on
the
plugin
side,
which
is
really
impressive,
especially
for
them
for
that
website.
That
was
a
refactor
a
little
bit
more
than
a
year
ago,
and
it's
really
nice
to
see
it.
A
If
you
use
today,
another
information
that
we
can
look
is
the
google
search
console
for
the
plugin
site,
and
specifically
here
is
we
can
know
how
many
time
people
are
looking
for
information,
let's
say
for
the
pipeline,
maven
plugins
or
the
kits
plug-in
or
the
docker
plugin.
So
when
we
see
at
the
number
of
clicks
here-
and
we
see
that
the
top
one
is
the
plug-in
search
engine-
slash
key
plugin
and
yeah,
we
can
we
can.
We
can
create
many
information
there,
so
yeah.
C
C
A
A
C
C
D
D
A
So
we
put
a
few
things
to
the
agenda
today,
so
the
first
one
that
I
want
to
to
highlight
is
the
github
organization
for
the
jenkins
infra
has
been
switched
to
the
free
tier.
So
this
is
something
that
we
discussed
several
weeks
ago.
We
were
paying
300
dollars
per
year,
and
now
the
free
tier
offer
everything
that
was
included
in
the
previous
plan.
So
that's
one
of
the
thing.
The
second
one
is.
A
We
had
an
ldap
incident
over
the
christmas
period,
apparently,
apparently,
the
ldap
container
was
in
the
broken
state
and
marquis
had
to
jump
in
and
just
restart
the
container.
I
look
at
that.
We
didn't
lose
any
data
and
we
still
have
backups.
So
everything
is
fine
there
considering
the
low
traffic
we
had
on
the
infrastructure
during
the
pre
the
christmas
period.
I
don't
think
it's
a
big
deal.
A
C
So
olivier,
when
I
look
at
my
okay,
I'm
doing
a
different
status
check,
but
it's
been
off
socket
timeout
for
oh,
no,
it's
ridge,
relatively
recent,
okay,
it
just
there
was
a
period
a
week
or
two
ago
where
it
was
offline,
and
now
it
looks
like
it
had
been
on
online
recently
again
and
just
offline
okay.
So
so
it
does
look
like
it's
a
performance
thing.
Previously
it
was
a
simply
offline.
Could
you
help
me
understand?
Who
should
we
contact
when
it
goes
offline?
I
thought
that
was
hosted
by
osu
os,
no.
A
I
mean
right
before
taking
my
of
some
vacation
and
the
machine
was
not
reliable,
so
I
could
not
ssh
and
it's
when
I
look
at
the
rackspace
console.
Nothing
tell
me
that
the
machine
was
overloaded,
so
I
couldn't
connect
on
it
and
then
suddenly
I
was
able
to
go
to
ssh
on
the
machine.
I
looked
at
the
logs
and
I
couldn't
find
anything
it's
just
like
the
the
uptime
was.
The
machine
was
running
for
a
really
long
time.
A
A
We
moved
back
to
the
jfl
storage
for
the
full
back
me
too
me
too.
It's
just
a
guess
here
and
norm.
Normally
we
we
are
using-
and
this
is
something
that
I
also
would
like
to
work
on
in
the
coming
weeks,
because
the
problem
here
is,
we
use
the
fallback.
The
default
bikes
use
the
same
azure
file
storage
than
bits,
which
means
that
if
something
goes
wrong
with
mirror
beats,
the
same
issue
happened
with
the
fallback
in
the
current
state.
So
we
should.
C
A
A
On
that
full
copy,
and
then
the
politics,
the
policy
and
the
different
mirrors
depend
on
the
on
basically
some
remove
after
a
year
of
that
time.
They'll
just
keep
so
it
really
depends
on
your
house,
but
the
full
copy
of
archive
is
right
now
is
into
two
different
locations,
so
it's
not
critical,
but
yeah.
That
would
be
nice
to
have
another
backup.
A
Another
issue
that
I
highlighted
right
before
taking
vacation,
which
was
the
silverian
mirror,
was
not
down
really
slow,
but
because
it
was
really
slow.
We
still
a
lot
of
time
out
issues.
I
was
easily
affected
by
severion
around
the
17th
of
december,
because
because
the
way
the
jenkins,
where
we
deployed
jenkins,
are
infrastructure,
so
the
way
we
configure
our
hem
chart
is
to
install
the
plugin
when
the
container
starts,
and
so
I
had
for
one
reason
I
had
to
restart
the
container
on
release.
A
That's
the
idea
jenkins
I
o
and
the
container
would
not
start
because
he
couldn't
install
the
plugins
because
he
tried
to
download
the
plugins
from
sarah
varian,
which
was
timeout
at
time
timeout
at
that
time.
So
it
took
me
a
while
to
understand
that,
but
basically
what
happened
is
some
of
the
plugins
were
not
installed,
so
the
container
was
restart,
so
it
tried
to
reinstall
every
plugins
and
the
loop
was
over
and
over
and
over
and
over.
So
it
took
me
a
while
to
identify
that.
A
C
A
Is
not
current,
so
I
just
so
two
thing
here.
I
really
are
re-enabled
it
today,
so
it's
not
included
yeah.
So
that
was
quite
recent,
but
because
of
the
because
of
the
fact
that
we
don't
control
your
house,
we
don't
know
how
often
that
machine
is
synchronized
with
our
own
mirrors.
So
that's
why
we
cannot
realize
that.
I
mean
that's
how
mirrors
are
working
so
as
long
as
another
house
has
the
data,
that's
fine.
C
A
So
right
now
mirror
bits
is
configured
manually
because
we
don't
have
many
mirrors,
so
we
are
run
like
around
10
comments
and
those
comments
are
documented
on
the
mirror
bits
hand
charts.
So
if
you
look
at
the
documentation,
you
see
that
we
provide
the
mirror
the
after
the
fft,
sorry
earthing,
endpoint,
actually
person
point
and
an
email
of
contacts.
A
A
E
No
problem,
so
the
the
wall
context
is
improving
how
we
build
operational,
docker
images
in
order
to
execute
operation
on
the
infrastructure,
for
instance
in
the
process
of
working
around
terraform.
We
want
to
also
add
some
testing
and
linting,
so
we
need
a
reproducible
way
or
a
reproducible
environment
to
execute
these
steps.
E
E
E
To
avoid
any
malicious
docker
file
that
can
that
could
come
from
a
malicious
source
or
any
change
to
the
docker
file.
We
would
not
want
this
to
break
out
for
building
docker
image.
Img
or
kaniko
are
already
solving
that
issue
somehow
or
at
least
provide
a
useful
security,
and
it's
already
how
we
do
it.
The
challenge
here
is
testing,
because
we
need
to
test
such
an
image,
for
instance
for
terraform.
We
want
a
specific
version
of
terraform
for
our
infrastructure
or
it
will
break
the
future
usages
of
terraform.
E
E
E
So
the
question
is:
oh,
a
contributor
could
be
able
to
run
the
same
step
as
the
build
process
without
sacrificing
the
security
I
mean.
I
don't
want
any
untrusted
workload
to
run
on
the
infrasier
jenkins,
so
the
work
we
are
doing
with
garrett
and
cara
is
starting
to
work
with
that.
As
a
part
of
the
knowledge
sharing,
we
try
to
make
that
work
as
much
public
as
possible.
E
The
idea
is
to
define
first
make
file
that
will
say:
okay
to
build
the
image.
That's
make
build,
make
test
and
make
deploy
to
hold
all
the
logic
that
make
file
should
be
trusted
as
well
as
a
jenkins
file.
So
it
should
end
inside
the
shared
library
as
a
static
resource,
and
the
goal
is
to
improve
the
pipeline
library
of
jenkins
infra
project
to
provide
a
docker,
build
docker
test,
docker,
publish
and
combination
of
both
so
four
functions
that
provide
these
specific
features,
relying
on
a
make
file
which
is
located
near
this
chart.
E
E
A
A
D
Three
go
ahead.
Tim.
That's
me
just
getting
annoyed
because
it's
the
single
most
annoying
thing
I
hit
with
the
jenkins
infrastructure
right
now
is
the
suggestions
dying
randomly
and
it'd
be
great
to
spend
some
time
investigating
that
I
did.
I
did
try,
but
I
just
don't
really
have
access,
because
it's
on
the
aws
agents-
and
I
can't
see
anything
there-
I
tried
to
get
into
them,
but
I
couldn't
find
the
credentials
properly
and.
C
D
C
Well,
and
and
olivia
it's
an
interesting
one.
Certainly
our
costs
are
increased
as
a
result
of
running
builds
a
second
time
because
the
agent
was
disconnected
on
the
first
time,
and
so
there's
there's
an
element
of
this
where
it's
actually
would
be
a
cost
savings.
I
just.
I
can't
predict
how
much
of
a
cost
saving.
So.
Yes,
it's
an
issue.
Unfortunately
yeah
I'm
not,
I,
I
don't
think
I'm
gonna
have
time
to
investigate
in
any
any
recent
any
any
upcoming
time.
Real
soon
tim.
I
apologize.
A
C
A
A
We
are
two
minutes
over
the
limit
of
the
meeting,
so
I
propose
to
stop
here
unless
you
have
one
last
element
that
you
want
to
bring
for
the
next
meeting
so
again
feel
free
to
to
add
your
comments
for
the
future.
For
the
next
meeting
in
one
week
add
any
topic
that
you
want
to
discuss
and
meanwhile
we
all
will
all
be
in
rse
anyway,
so
see
you
there.