►
From YouTube: INFRA Weekly Meeting 2020 05 05
Description
Jenkins Infrastructure Project Meeting - 2020-05-05
Notes - http://bit.ly/2T0oZ9v
A
We
don't
have
a
lot
of
topics
to
the
agenda,
so
yeah
we'll
just
do
a
quick
recap
of
thing
that
happened
over
the
last
week,
so
the
first
one
is
I
spent
some
time
to
fixed
potato
Jenkins
arriving
machines.
So
basically,
what
happened
is
when
years
ago
went
your
grid
from
whooping
to
14
to
18
we
had
to
bring
multiple
packages
and
mohab
grain,
which
is
the
tool
that
we
use
well
on.
A
Yours
was
the
package
full
moon,
218,
so
Tyler
made
a
specific
package
until
we
were
missing
some
dependencies,
and
so
the
open
source
project
is
also
made
any
specific
Ubuntu
repository,
but
for
all
playing
and
so
I
just
upgraded
to
the
latest
version
available
on
that.
On
that
repository,
a
great
PostgreSQL
I
made
some
improvement
on
the
database
and
Apache
to
increase
the
number
of
connections.
So
now
everything
seems
to
be
stable
and
the
response
time
of
the
blade,
Center
and
packaging
keys.
A
So
it
means
that
I
mean
it's
not
as
much.
It's
not
anymore,
as
if
you're
a
surgeon
to
work
on
that
machine,
as
it
was
last
week,
so
I'm
going
to
leave
it
in
the
state.
For
now.
The
other
major
thing
that
I
did
was
regarding
adapt
to
touching
concern.
I
do
so.
We
were
using
a
certificate
provided
by
named
chip
that
certificate
expired
last
Thursday
and
so
I
switched
the
certificate
to
let's
encrypt.
A
The
major
change
here
is
that
the
LDAP
will
have
to
read.
I
will
read
the
certificate
every
three
months,
I'm,
not
sure,
yet
that
the
current
configuration
supports
how
to
reload,
so
we
probably
have
to
reload
to
restart
the
container
every
three
months.
For
now
I
mean
this
is
the
current
yeah
just
a
cron
job.
C
A
A
But
at
least
for
now
yeah
means
that
we
switch
to
him
to
alert
encrypt
I
did
I,
did
a
bunch
of
tests
generally
places
were
that
connect
at
the
plan
was
broken,
was
an
account
up,
I
think
but
accepted
that
everything
seems
to
be
working
fine.
So
that's
good
any
question
so
far,
no,
and
so
the
the
the
last
pitch
was,
which
is
the
last
topic
that
I
want
to
talk.
A
Another
limitation
is
that
we
need
to
be
able
to
to
merge
the
code,
but
not
between
forth,
but
between
different
gates
repository
because
they
are
using
a
specific
private
git
repository
for
the
security
work,
and
so
we
need
we
also
have.
We
need
to
have
some
kind
of
this,
get
promotion
with
git
repositories
and
so
yeah.
So
do
too
many
thing
that
you
have
to
implement
are
basically
promotion
between
a
specific
release
to
the
security
one.
The
good
thing
is:
we
have
until
June
I
think
around
June
to
finish
that
work
so
yeah.
A
A
So
yeah,
so
that
that's
that
was
pretty
also
the
last
the
last
thing
that
also
moved
on
the
infrastructure-
and
this
is
more
related.
This
move
some
work
done
by
Alex
and
Marc,
so
they
also
added
the
s/390
architecture
and
the
PPC
64
to
see
either
gingka
value,
which
means
that
we
can
also
start
working
on
those
procedure
and
build
on
those.
A
B
C
E
Asure
only
something
that
I
can
give
you
like
this
and
Olivier
I'm,
preparing
I
might
have.
One
of
my
goals
for
this
week
is
to
submit
the
changes
that
are
the
tests
that
I
had
written
for
Pat
automated
release,
packaging
checks
as
part
of
us.
The
standard
build
but
I
can't
see
the
definition
of
the
build
process.
Are
we
building
off
the
master
branch
or
off
the
infra
9:10
branch
when
we
do
a
release
build
for.
A
A
weekly
so
right
now
we
are
using
the
the
branch,
so
we
are
not
using
the
master
branch.
The
main
reason
to
this
is
because
Kisuke
still
rely
on
the
master
branch
to
release
a
stable.
So
that's
why?
So,
basically
we
merge
all
the
changes
to
the
master
branch
once
we
are
fully
managing
all
releases.
A
A
That's
all
otherwise,
so
yeah
I
will
look
for
your
permission.
You
should
have
access
anyway,
so
maybe
I
did
something
wrong
after
limiting
and
otherwise
yeah.
If
you
don't
have
any
thing
that
you
want,
I
mean
that
that
you
want
to
discuss
here.
I
propose
to
go
back
to
our
scene
and
in
closed
meeting
here,
thanks
for
your
time,
all
right,
right,
yeah.