►
From YouTube: 2021 07 20 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
Okay,
hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting
today
to
the
agenda.
The
first
thing
that
I
want
to
announce
is
we
got
an
approvement
from
digital
ocean
to
sponsor
the
infrastructure,
so
damien
lead
that
effort
with
kevin
who's.
I
mean
gavin
is
a
digitization
employee
now,
so
maybe
that
helped,
but
yeah,
that's
really
great.
So
with
that
money,
we'll
use
it
to
add
a
mirror
to
to
our
mirror
infrastructure,
we
still
have
to
decide
where
we
deploy
that
mirror.
A
We
have
some
suggestions
to
deploy
it
in
india
or
somewhere
in
asia
to
improve
the
situation
over
there
but
yeah.
This
is
something
that
need
to
be
decided,
and
the
second
thing
is
we'll
have
the
ability
to
deploy
a
small
community's
cluster
and
we
are
planning
to
use
it
for
agent
for
rci
infrastructure
to
release
our
dependencies
on
azure.
A
So
if
you
are
interested
to
work
on
that
one,
I
just
created
the
digital
version
account,
and
so
this
is
a
very
new
project
that
we
are
starting
on,
so
that
thing
to
the
agenda
today
we
have
few
things,
so
the
first
one
is
last
monday.
So
yesterday
I
did
an
upgrade
of
the
puppet
version,
so
we
are
using
puppet
enterprise.
We
are
using
a
small
puppet
enterprise.
A
We
are
still
using
the
free
tier
right
now
the
motivation
to
do
that
upgrade
yesterday
was
we
so
we
have
to
go
back
to
the
rackspace
accounts
and
we
were
working
to
migrate
archive
to
jenkins
that
I
used
to
a
different
machine
and
we
wanted
to
test
the
oracle
cloud
with
the
harm
machine.
The
reason
for
that
is,
they
are
very
cheap,
it's
arm
and
we
have
one
gigabyte
of
network
bandwidth.
A
So
that's
the
I
mean
we
have
the
biggest
network
bandwidth
for
the
size
of
the
machine,
but
the
limitation
was
we
had
to
ramp
up
ubuntu
2004
and
we
had
to
to
be
on
the
puppet
version
at
20
19.8
after
a
quick
evaluation.
That
was
not
a
big
upgrade.
I
just
have
some
notes,
so
there
is
a
link
to
the
upgrade
node
that
was
pretty
trivial.
We
still
have
some.
I
collected
some.
In
the
note
I
collected
some
tasks
that
we
have
to
prove
to
do
for
the
next
major
upgrade,
but
we
are.
A
We
are
on
track
with
that
version,
which
is
great.
The
next
stable
version
is
puppet,
seven,
which
should
be
ready,
I
think
in
september.
So
we
are
not
too
far
in
the
past
with
our
puppet
code,
which
is
that's
nice,
so
right
now,
I'm
going
to
reorganize
the
notes.
So
what
what's
the
next
step?
So
we
are
almost
ready
to
deploy
to
move
archives
into
the
to
our
record
clouds.
A
We
still
have
minor
features,
minor
codes
that
I
would
like
to
bring
first,
so
the
first
one
is
there
were
some
manual
changes
apply
to
the
archive
touching
these
io
that
we
have
to
work
and
we
have
to
write
the
public
code
for
it.
That's
one
thing.
The
second
one
is
how
we
provision
the
data
on
archive.jso,
so
I
open
a
pr.
I
don't
know
if,
if
I
put
the
link
in
this
endnote
no,
but
I
can
put
the
link
later
on,
I'm
open
for
feedback.
A
So,
just
briefly
to
understand,
the
big
picture
is
right.
Now,
each
time
we
generate
new
packages,
we
push
everything
on
a
specific
machine
and
from
that
machine
we
push
artifact
to
different
locations.
Also,
assembly
house
our
character
gently
in
the
leo
and
then
so
on.
So
that's
that
central
machine
is
a
key
component
of
our
infrastructure
and
what
I'm
doing
here
is
instead
of
having
that
machine
that
push
artifact
to
different
location.
A
A
So
so
yeah,
I
I
hope
to
me
create
that
workspace
machine
by
the
end
of
the
week
or
at
last
next
week.
So
that's
the
target
for
me.
A
The
next
major
topic
that
I
want
to
briefly
talk
here
is
regarding
the
issues
we
had
with
artifactory
over
the
past
few
weeks.
So
last
week,
gfrock
upgraded.
Apparently
it
was.
The
issue
was
related
to
the
size
of
our
database.
So
just
for
just
for
the
context.
Several
weeks
ago,
g
frog
migrated
the
instance
that
we
were
using
from
somewhere.
A
I
have
no
idea
because
I
don't
have
access
and
they
moved
us
to
the
g4
clouds,
and
so
I
guess
they
undersized
a
few
components
such
as
the
database,
and
so
what
happened
is
they
increased
the
size
of
the
database,
and
now
we
were
able
to
finalize
the
security
release,
so
that
happened
last
week.
A
A
A
Next
topic
is
about
docker
images
and
that
one,
I
think
they
mean
it's
better
than
me
to
do.
A
quick
update.
B
B
B
The
main
challenge
is
being
able
to
move
all
the
listing
of
images
inside
the
centralized
file
instead
of
duplicating
that
information
on
pipeline
build
and
test
steps,
it
involved.
Alas,
a
lot
of
make
and
shell
scripting
and
the
docker
buildix
tooling,
is
still
a
bit
young
or
missing
features.
So
we
are,
we
might
want
to
give
them
feedbacks.
B
We
are
working
on
that.
I
expect
something
in
the
upcoming
days
and
on
the
other
way,
thanks
to
to
tim
and
jesse
glick.
Now
the
gnlp
agent
images
for
windows
java
are
using
maven
3.8.1
on
aci
for
ci
junk
inside
so
right
now
the
virtual
machines
and
the
container
build
and
ci
are
now
using
the
same
maven
version
about
that
topic.
That's
the
topic
I
want
to
raise.
I
can
do
it
right
now
or
a
bit
later.
B
B
The
reason
is
that
we
don't
want
it's
really
an
issue
when
a
developer,
a
contributor
has
different
environment
where
you
don't
have
the
same
java
or
the
same
maven
or
the
same
code,
the
same
shell
or
powershell
version.
So
the
idea
is
in
that
case,
instead
of
using
docker
build
or
buildix
or
specific
docker
stuff
we
let
packer
handle
these
builds.
B
A
B
If
we
have
such
use
case,
then
we
we
will
keep
using
specific
images
with
specific
scope.
However,
most
of
the
aci
builds
are
should
be
the
same
as
the
virtual
machines.
Most
of
the
time
we
use
aci,
it's
it's
container
used
as
a
virtual
machine
because
we
have
java
and
ssh
and
powershell
and
a
bunch
it's
a
kitchen
sync
images.
B
So
my
proposal
is
that
ensuring
we
have
by
default
always
the
same
base,
because
we
can
test
the
output
on
packer.
That's
the
same,
when
we
update
the
maven,
we
update
it
on
a
single
place
same
for
whatever
dependency
we
have
and
we
keep
the
specific
images
like
the
one
we
have
on
the
infrastructure,
specific
for
terraform
specific
for
packer.
B
A
A
B
Yeah
here
I'm
not
I'm
not
stating
we
should
duplicate.
The
images.
Sorry
maybe
duplicating
is
a
is
not
the
correct
meaning
here.
It's
we
stop
using
agent
using
with
these
images.
B
A
No,
I'm
not
saying
that
we
have
tests,
I'm
just
saying
that
we
identify
issues
and
we
try
to
solve
those
issues,
and
so,
if
we
want
to
do
something
else,
my
point
is
just
like.
It
should
be
clear
why.
B
Okay,
something
just
something
important
to
have
in
mind
that
it's
still
building
docker
images
and
packer
is
able
to
push
these
images
on
a
registration.
B
B
A
Example,
thanks
damian
any
other
topic.
You
want
to
bring
damian
marco
audita
here
regarding
the
jenkins
infrastructure
project,
so
I
I
still
have
one
open,
you're
freezing
for
me,
so
I'm
not
sure
if
it's
on
my
side
or
not,
is
it
working
for
you.
A
A
A
Meeting,
okay
right,
so
I'm
counting
two
up
to
five
in
my
head
and,
if
he's
not
coming
back,
then
I
propose
to
stop
the
meeting
here,
one
two!
A
Okay!
So
so
that's!
Okay!
That's
answer
my
question!
Then.
I
think
that
we
don't
have
another
topic
so
feel
free.
If
you,
if
anything,
comes
to
your
mind,
we'll
have
another
information
next
week
and
there
is
a
link
to
this
document
and
to
the
one
for
next
week
feel
free
to
add
any
topic.
You
want
to
cover
there
and
yeah
thanks
for
your
time,
see
you
in
rc
goodbye
thank.