►
From YouTube: 2021 08 10 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).
B
Hello,
everyone
welcome
to
the
weekly
infrastructure
meeting
team
so
for
the
8th
of
august
2021.
So
let's
start
by
announcement,
so
we
have
been
able
to
release
jenkins
2.306.
So
congratulations
to
everyone
involved
in
that
weekly
release.
The
checklist
is
complete
mark.
You
might
have
a
word
about
the
docker
image
on
that
topic.
A
Oh
yes,
so
the
docker
image
definitions
add
some
new
tags.
Previously
the
tags
were
latest
slim
alpine.
A
Now
there
are
additional
tags.
Latest
jdk8
slim
dash
jdk
8
alpine
jdk.
Now
they
are
redundant
at
the
moment
because
jdk8
is
what's
currently
delivered
in
latest
and
in
slim
and
in
alpine
but
beginning
with
next
week's
release.
Our
intention
is
to
switch
at
2.307,
so
that
latest
will
become
jdk,
11
and
slim
will
become
jdk
11
and
people
who
need
jdk
8
will
need
to
use
latest
jdk8.
B
So
the
activity
is
quite
was
quite
slow
this
weekend
in
upcoming
week,
it's
a
middle
of
the
summer.
So
let's
start
it's
been
a
numerous
time
that
team
jacom
was
unable
to
to
join
us.
So
it
sounds
like
that.
The
time
of
the
meeting
is
not
the
best
slot
for
him,
so
the
idea
is
to
create
a
poll
to
find
a
new
meeting
time
that
will
allow
team
and
every
usual
contributor
and
attendees
to
to
see
the
meeting
mark.
Do
we
have
a
poll
we
use,
pull
tool
that
we
use
to
work?
A
B
So,
let's
try
this
course
to
see
if
we
are
able
to
do
that
so
gavin.
If
you
see
that
recording
we
we're
going
to
ping
you
on
for
some
help,
maybe
on
irc,
but
I
think
this
course
might
have
some
kind
of
plugin
like
this
one.
Otherwise,
let's
switch
to
the
dollar
good
good
suggestion:
okay,
okay,
so
mark
you
taking
the
action
cool.
B
Nice
on
my
side,
I'm
working
on
ci,
jenkins,
io,
so
work
in
progress
for
aci
and
kubernetes,
so
the
goal
is
to
still
to
move
some
workload.
B
I
did
not
worked
a
lot
on
that
part
right
now.
I
was
more
focusing
on
the
puppets
puppet
code,
so
I
took
some
trainings
to
master
a
bit.
The
reason
is.
The
second
point
is
because
I
will
want
to
implement
as
soon
as
possible
an
automatic
update
of
the
agent
template.
B
So
right
now
it's
doable
quite
easily
with
update
cli
for
the
azure
templates.
However,
for
the
mei
there
might
be
some
work
to
be
done
there,
so
I
need
a
bunch
of
update
cli
contribution
and
a
puppet
code,
so
I
was
working
on
that
part
experimenting.
B
B
Right
now,
I've
worked
on
the
aws
as
a
test,
but
I've
been
blocked
and
I
stopped
at
that
part.
I
realized
that
before
going
to
1.0,
I
need
to
update
all
the
terraform
modules
we
are
using.
So
that's
work
in
progress,
and
once
we
have
the
latest
version,
then
I
should
be
able
to
switch
there
from
1.2.
B
The
reason
of
that
change
as
a
reminder,
it's
because
we'll
have
to
start
resources
on
digital
ocean
and
scale
away
our
new
sponsors
and
also
eventually
on
oracle
cloud
as
well,
because
it
worked
with
terraform.
So
the
goal
is
to
have
an
unified
and
long-term
support
for
managing
infrastructure.
As
cut
there.
A
So
so
the
progress
on
ci.jenkins.io
is
tied
right
now
to
puppet
and
getting
getting
automation
there
and
you're.
Still
this,
the
concept
is
still
that
I'll
be
able
to
continue
using
labels
to
describe,
and
we
will
have
kubernetes
agents
that
provide
the
same
labels
and
limit
the
amount
of
the
number
of
them
they
allocate.
So
so
we'll
be
able
to
watch
those
agents,
see
that
they're,
healthy,
etc.
B
Exactly
initially,
I
was
I
wanted
to
work
with
team
on
that
topic
because
he
saw
some
build
of
the
bomb
that
are
quite
complex
builds.
The
thing
is
that
we
are
too
asynchronous
to
these
days,
so
I
am,
I'm
gonna
start
by
switching
all
the
the
job,
the
ci
junk
inside
your
job
for
jenkins
puppet
code.
That
one
is
using
the
aci
aci
containers
with
the
ruby
agent.
I
think
we
are
almost
the
same
to
use
this,
so
I'm
gonna
switch
that
project
fully
to
the
new
one.
A
A
Some
users
will
be
switching
to
run
that
their
agents
will
run
with
jdk8,
rather
than
with
jdk
11.,
as
the
hosted
or
as
the
8
java
version
running
that
agent.
B
Sorry
I
was
speaking
completely
muted,
so
so
yeah,
that's
that's
all
for
me.
I
don't
have
an
other
topic.
Do
you
have
other
topic
on
your
side.