►
From YouTube: 2021 08 27 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
A
Okay,
so,
first
of
all,
right
now
we
are,
we
are
having
a
maintenance
of
the
repo
jenkinsci.org
repository,
so
that
is
a
shifrog
service,
so
they
sponsor
us
by
letting
using
that
artifactory
instance
in
their
cloud
and
since
the
past
two
or
three
weeks
we
were
facing
issues
for
the
downloads
sounds
like
front
issues.
A
Some
some
artifacts
were
not
being
able
to
download
temporary
failure
on
some
areas
of
the
world,
so
sounds
like
related
to
their
mirror
infrastructure,
and
so
they
are
migrating
the
version
of
whatever
tooling
they
are
using
and
migrating
the
database
as
well.
So
we
should
have
had
a
downtime
during
the
past
hours.
I
haven't
had
time
to
check,
but
for
sure
we
will,
let
you
know
everything
is
has
been
communicated
today
on
the
status
page
and
on
the
developer
month.
Mainly
list
so
we'll
send
a
hand
off
maintenance
email
to
close
that
afterwards.
A
We
had
weekly
and
lts
release
this
week,
so
that
was
pretty
packed.
A
bunch
of
issues
were
met
for
both
we
will
have
to
do
a
retrospective
to
improve
the
next
ones.
A
I
don't
have
so
much
information
on
that
part
except
something
related
to
the
s390xr
and
ppc
architectures.
I
will
speak
about
that
later,
but
we
we
were
able
to
release
it.
Just
it
took
longer
for
both
and
took
more
effort
but
yeah
room
for
improvement,
but
great
job.
Everyone
involved
in
this
release
because
we
were
able
to
deliver
and
that
worked
very
well.
A
We
switched
from
adopt
open
gdk
to
eclipse
tamarind.
I
think
it's
the
correct
product,
I'm
not
sure
it's
the
correct
pronunciation,
so
please
pardon
my
english.
So
eclipse
tamarind
is
the
new
home
for
the
adopt
open,
gdk
distribution
project.
A
The
positive
side
effect
is
that
we
gain
hundreds
of
megabytes
on
each
image
that
have
this
system.
So
that's
quite
nice.
We
are
still
having
issues
with
alpine
linux
because
we
had
to
use
jlipc,
which
is
not
a
good
practice
at
all.
One
should
not
use
gillipsie.
There
are
plenty
of
good
reason
because
it
uses
muscle,
but
it's
temporary
measure,
because
eclipse
tamarind
is
currently
working
with
alpine
linux
developers
to
have
a
native
supported
image.
A
Another
consequence
we're
not
sure
if
it's
directly
related
to
tamarind
or
if
it's
just
an
issue
that
has
been
been
made
visible.
We
had
to
suspend
the
build
on
distribution
of
the
ppc
and
s3
s390x
images,
because
the
bergon
chemist
the
emulator.
We
are
using
today
two
solutions
for
that
using
native
machines,
but
we
need
two
machines
for
each
one
for
ci
and
one
for
trusted
where
the
delivery
opened
and
team
was
able
to
track
the
issue
on
camus,
which
has
been
already
released.
So
we
are.
A
We
have
to
wait
to
that
release
to
be
updated
on
the
infrastructure
to
be
able
to
put
them
back.
So,
let's
say
next
weekly.
That
should
make
these
images
back.
Sorry
if
you
started
to
use
them,
but
these
two
images
were
not
official.
They
were
just
new
shadow
release,
so
not
so
much
impact
there.
But
we
are
deeply
sorry
if
you
are
testers
on
these
images
and
that
you
were
not
able
to
use
latest
release.
B
Well,
I
understand
all
this.
I
just
wanted
to
know
how
tamarind
is
better
than
open
gdk.
If
you
can
provide
some
pointers
on
that,
it
would
be.
I
guess.
A
Eclipse,
the
marine
is
adopt
open,
gdk,
it's
just
that
the
the
wall
infrastructure
for
building,
maintaining
and
distributing
adopt
open
gdk
is
moving
under
a
foundation
which
is
the
eclipse
foundation,
and
so
they
change
the
name
to
materialize
that
change.
But
it's
the
same
code.
It's
the
same
project,
it's
just
it's
under
the
foundation
management.
Now.
A
B
Starting
to
move,
and
now
they
are
like
right
now,
they
just
support
a
couple
of
images
like
these
operating
systems
and
then
like
when
they
finally
move.
Probably
there
might
be
more
coming
up
like
we
talked
about
that
in
a
conversation
with
alpine,
exactly.
A
There
are
long
discussion
without
absolute
answer
right
now
without
consensus
that
will
be
moving
part
of
that
specialized
per
distribution
work
on
the
package,
maintainer
meaning
if
you
are
maintainer
of
alma
linux.
That's
your
responsibility
to
provide
open,
gdk
under
packaging,
eclipse
team
marine
for
your
distribution
instead
of
having
an
upstream
build.
A
A
Honestly,
I
don't
know
what
are
the
supported
timeline
lts
for
opengdk,
I
feel
like
we
are
early
adopters.
That's
why
we
had
these
issues,
but
that
was
not
really
impacting
the
main
lines
of
our
images,
so
the
irm
and
intel
images
and
that's
already
a
safe
ground
to
test
these
things
before
it
comes
to
an
lts
or
something
like
that.
A
So
the
next
subject
is
the
switch
from
aci
to
kubernetes
agent,
so
on
ci
jenkins,
io
for
costs,
resiliency
and
technical
reasons.
We
started
to
add
kubernetes
agents
next
to
aci
and
we
completely
removed
the
aci
because
it
started
to
behave
erratically.
We
weren't
able
to
finish
a
single
pull
request
on
jenkins
score
two
weeks
ago
and
also
in
term
of
costs.
So
after
two
weeks
of
production
usage,
so
far
so
good,
we
have
removed
everything
related
to
the
docker
api
limit
and
secrets.
A
A
A
New
upcoming
change
that
we
will
have
to
study
carefully
nginx
ingress
1.0
has
been
released.
It's
the
nginx,
ingress
and
chart4.x
so
for
now
expect
a
pull
request
that
will
force
using
the
version
three
dot,
something
to
keep
the
old
version,
the
current
version
we
have
and
only
benefit
from
patches
and
security
updates.
A
We
have
to
check
before
there
are
breaking
changes,
especially
with
the
support
of
the
new
ingress
api,
which
is
mandatory
on
kubernetes
1.22,
but
we
need
to
be
on
kubernetes
1.20
to
fully
benefit
from
this
new
ingress.
So
we
have
to
check
of
what
is
the
behavior
of
nginx
ingress
1.0
on
our
current
versions,
but
that's
a
subject
to
keep
anyone
interested
or
with
enough
knowledge
on
that
part
is
welcome
to
help
us
on
that.
A
New
subject
that
I'm
raising
personally,
it's
a
proposal
for
a
weekly
task
that
will
be
30
minutes
each
week
of
mob
or
per
walk.
So
we
start
up
a
visual
everyone
connects
and
the
goal
during
this
30
minutes
will
be
to
bash
issues
on
the
jira
infratreker,
because
we
have
a
lot
of
issues
that
should
be
closed,
that
are
out
of
date
that
can
be
raised
or
bumped
again
or
try
aged.
A
So
the
goal
is
tackle
this
problem
down,
so
we
can
go
back
to
using
issues
as
support
for
the
actions
on
each
weekly
team
and
we
could
start
going
back
to
triage
a
proposal
that
has
to
be
confirmed
by
at
least
olivier
and
any
people
interested
next
wednesday
at
1
pm
utc,
so
that
will
be
3
p.m,
on
paris
or
9
a.m.
On
the
east
coast.
A
Packer
images
some
work
has
been
done
on
the
packer
images
repository.
The
goal
of
that
repository
is
to
provide
virtual
machines
templates
for
ci
jenkins
io,
so
we
are
on
the
process
of
update
we
bumped
git
and
some
dependencies
expect
a
bump
to
the
latest
maven
version
3.8.2,
which
is
a
patch
version.
We
are
currently
running
3.8.1
and
we
are
now
going
to
build
meis
and
all
virtual
machine
template
on
each
pull
request,
because
during
the
past
months,
when
a
contributor
raised
the
pull
request,
it
was
not
really
built.
A
So
when
it's
a
matter
of
downloading
a
new
version
of
a
package,
we
cannot
test
it
until
the
change
is
merged
on
master,
so
30
minutes
waiting
for
the
for
that
build
and
then
a
second
time
to
rebuild
when
it
failed.
It
was
more
than
one
hour
for
feedback,
so
our
goal
is
to
shrink
that
feedback,
but
the
cost
is
that
an
individual
pull
request
will
be
built
in
20
25
minutes
because
time
to
build
the
virtual
machines
and
test
everything
that
set
the
ground
for
auto
updating
these
images.
A
So
there
are
some
work
on
update
cli,
but
we're
almost
there
expect
before
end
of
september.
All
the
update
of
the
virtual
machine
will
be
automatically
next
step
will
be
migrating.
The
docker
inbound
agent
images
that
are
specific
to
the
infrastructure
inside
that
repository,
so
that
packer
will
build
the
same
environment
either
you
are
running
a
container
or
a
virtual
machine.
A
So
we
should
not
plan
anything
unless
olivier
is
available.
Next
big
topic
on
september
will
be
cost
management.
We
started
manual
cleaning
on
azure,
with
olivier
removing
all
the
untangling
resources,
and
now
we
are,
we
saw
some
quick
and
fast
improvement
on
the
costs.
So
this
month
we
are
decreased,
the
cost
of
azure,
but
the
costs
on
aws
are
increasing
each
month.
A
A
So
now
we
were
able
last
month
to
improve
drastically
the
time
between
an
idea
and
the
changes
deployed
to
our
production,
which
is
really
nice,
because
we
can
update
the
infrastructure
really
efficiently,
but
now
upgrading
to
a
recent
version
of
puppets,
tackling
down
cvs
and
providing
a
local
reproduction
and
integration
test.
All
these
topics
are
quite
sensitive
because
it
breaks
everything
and
we
might
have
to
rethink
the
way
we
use
and
test
modules.
A
I
wasn't
successful
after
three
days
of
full
work
on
that
one,
so
I
need
help
on
that
topic.
If
you
know
puppet,
you
are
welcome
to
help
for
me.
The
road,
if
I
don't
get
any
help,
we'll
be
rewriting
all
the
tests
for
them,
our
modules
puppet
modules
using
the
new
pdk.
That
means
starting
from
scratch
and
then
migrating
the
airspec
contents.
A
A
Thanks
so
then
I'm
gonna
close
the
meeting
and
pause
the
recording,
and
I
hope
that
next
week,
more
people
will
be
there
yeah
holidays
for
the
luckiest
one
good
for
them.
A
No,
the
I
will
that
will
be
the
only
day
I
will
be
present,
so
I
should
be
here
as
spectator,
okay,
yeah,
but
yeah.
This
is
under
the
time
limit,
but
I
will
be
working
only
the
free.
I
have
other
company
meetings
so
that
I
want
to
attend.