►
From YouTube: 2021 02 16 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
Hi
everybody
welcome
for
this
new
jenkins
silver
meeting
today
to
the
agenda.
We
don't
have
many
different
topics.
We
just
did
the
new
weekly
release
of
the
version
2.208.
I
think
everything
went
well.
At
least
I
did
not
see
anybody
complaining
about
that
release.
Yet.
A
The
just
the
thing
that
I
want
to
highlight
here
with
the
weekly
releases
yesterday
I
was
correctly
notified
when
we
had
issues
during
the
ll
test
release.
I
think
that
was
alter
three,
so
that's
really
nice
that
we
can
now
detect
if
the
release
process
was
interrupted
for
some
reason.
A
A
From
my
point
of
view,
it
won't
be
a
big
deal,
because
the
the
long
term
goals
is
to
rely,
I
mean,
is
to
rely
on
kubernetes
anyway,
so
we
won't
be
using
azure
container
instances
anyway
to
me
that
that
date
seems
quite
far
compared
to
today.
So
I
wouldn't
I
mean
I
personally-
I'm
not.
I
don't
worry
about
that.
It
doesn't.
A
Yeah
and-
and
it's
not
like
nobody
else-
can
modify
that
code,
so
yeah,
if
you,
for
instance,
you
compare
that
to
amazon
amazon,
do
not
officially
support
the
ec2
plugin,
for
instance,
it's
maintained
by
the
community,
so
yeah
from
my
point
of
view.
It's
not
I'm
not
worried
about
that,
but
yeah.
The
the
the
main
topic
that
I
want
to
discuss
today
is
about
the
ca
certificate
used
to
sign
the
update
center.
So.
C
Before
you
go
on
from
that
one,
I'm
still
I'm
still
nervous.
We
spent
12
months
migrating
jira
and
ci
jenkins
that
I
was
a
lot
more
complicated
than
jira.
I
don't
think
we
need
to
do
anything
dramatically
different,
but
I
think
we
should
remind
ourselves
that
azure
is
probably
not
azure
and
particularly
aci
is
not
our
long-term
destination
right.
We,
we
really
do
just,
as
you
said,
long-term
want
to
be
on
kubernetes
and
we
want
to
be
more
portable
than
we
are
right
now,
so
we're
going.
A
So
on
that
specific
topic,
debian
demand
who's.
Not
there
right
now
is
looking
at
how
to
provision
agent
on
communities
so
a
provision,
an
amazon
cluster,
and
so
we
have
some.
I
mean
we
have
ongoing
work
there,
nothing
really
major
to
to
report
or
highlight,
but
I
mean.
C
A
So
right
now
we
are
planning
to
use
communities
to
replace
the
azure
container
instance.
That's
one
of
the
plugin.
We
could
also
use
the
same
approach
for
the
oracle
club,
whatever
community
sponsored,
we
have.
A
We
still
have
specific
integration
with
azure,
but
we
don't
have,
I
would
say,
strong
requirements
on
the
plugins.
I
mean
we
still
have
some
workarounds,
and
so
I
mean
right
now.
They
will
just
stop
officially
supporting
the
those
plugins
but
yeah.
We
still
have
options
and
I'm
not
really
concerned
about
those
plugin
anyway.
A
I
don't
think
they
will
stop
working
the
day
and
date
anyway.
So
so
I
proposed
to
continue
to
the
ca
certificate
so
basically
inside
jenkins,
core.
We
have
a
ca
so
basically
that
that
ca
is
used
by
jenkins
to
know
if
it
can
install.
So
let
let
me
explain
this
different
way,
so
the
update
centers
use
a
certificate
to
sign
the
package,
the
plugins
that
we
want
to
install
and
that's
yeah.
A
That's
that
certificate
is
expiring,
so
the
next
time
was
something
like
one
year
ago
I
generated
a
new
one,
but
but
the
problem
is
we
use.
We
use
an
old
ca
to
sign
that
certificate
and
that
all
ca
is
expiring
in
april
2021.
Basically,
so
we
need.
We
need
to
now
use
a
new
ca
that
was
introduced
in
jenkins
car
around
april
2018.
A
We
delayed
that
decision
served
from
months
ago
because
we
didn't
want
to
change
that
that
at
that
time,
but
I
think
it's
time
now
to
announce
that
we
will
renew
the
we
we
will
sign
will
sign
the
update
center
using
a
newer
ca.
Basically,
I'm
not
sure
if
we
just,
we
can
just
send
an
email
on
the
dev
mailing
list
or
if
we
have
to
send
a
blog
post.
I
don't
think
it
will
impact
the
community
because,
anyway,
the
version
2.117
is
really
old.
A
C
A
I
mean
I
can,
I
can
send
an
email
I
I
can
send
a
black
person
that
there
is
not
a
lot
of
things
to
say.
Just
we
are
rotating
the
root
ca
and-
and
basically
you
shouldn't
be
affected
by
that,
but
yeah.
B
Yeah,
I
don't
know
blog
post
is
really
needed.
That
version
is
ancient
they're
not
going
to
be
able
to
use,
so
they
won't
be
able
to
update
plugins
anyway.
So
it's
basically
impossible
from
the
community
update
center
anyway,
because
any
plugin
you
try,
the
only
plugins
you
better
install
are
plugins
with
an
old
baseline.
They
have
no
dependencies.
B
C
So
yeah-
and
I
think
I
understand
tim
yesterday
or
yesterday
during
doc's
office
hours,
we
did
a
development
exercise
using
a
plug-in
and
it
defaulted
to
running
2.176
and
immediately
started
offering
plug-in
downloads
that
couldn't
be
used
with
that
version.
So
you're
right
so
maybe
it
is.
It
is
pointless
to
talk
about
a
blog
post
because
because
it
was
already
unworkable
today
I
think
that's
what
you're
saying
right.
It's.
C
B
C
A
Sure
so
last
topic,
which
is
about
the
contributor
summits,
apparently
it's
next
week
right
so.
C
Next
next
tuesday
is
the
opening
session
of
the
contributor
summit.
It
will
be
from
3
to
5
pm
utc
and
in
that
we'll
have
five
to
seven
minutes
for
each
of
the
heads
of
special
interest
groups
for
each
of
the
officers.
So
tim
you'd
have
five
to
seven
minutes
on
the
presentation
to
share
the
progress
from
the
last
12
months
of
release,
work
and
what
you
think
should
be
coming
olivier.
Likewise,
you
can
go.
C
Yes,
seven
minutes
to
just
cover
all
the
things
that
we
did.
I
mean
it's
not
a
lot.
Well,
not
just
all
the
things
we
did
all
the
things
we
did
and
the
things
you
would
like
the
ideas
you
would
like
to
propose
for
the
coming
year
and
and
then
we
will
organize
ourselves
into
tracks
and
one
of
the
tracks,
I
think,
is
going
to
be
securing
the
delivery
pipeline
for
jenkins
components
for
jenkins,
plug-ins,
etc,
and
there
I
think,
infra
and
release
and
security
all
should
be
involved
in
that
single
track.
C
B
C
E
Yes,
thank
you
mark.
We,
the
google
summer
of
code,
application
as
an
org,
is
wrapping
up
and
what
we
really
need
from
you
all
if
you're,
if
you're
interested,
is
to
put
your
names
down
as
willing
to
be
mentors
for
the
different
listed
projects
on
the
gsoc
page.
We
have,
I
believe,
six
of
now
there
are
two
more
potential
ones
in
the
pipeline.
One
is
almost
certain
to
be
end,
so
there
is
a
bit
of
a
choice,
a
lot
of
very
interesting
ones.
E
Marcus
put
one
forth
and
there,
in
addition,
are
a
number
of
really
good
ones
on
on
cloud
native
topics.
Things
like
that.
So
if
you
are
interested
in
being
a
mentor,
you
will
not
be
the
only
mentor
on
any
of
these
projects.
You
will
always
be
paired
with
another
mentor.
That
is
our
goal.
E
Ideally,
we
would
even
have
up
to
three
or
more
mentors,
and
this
year's
gsoc
is
requiring
a
reduced
amount
of
hours
from
students
nearly
half
the
hour.
So
it's
only
175
hour
projects
over
the
10
weeks,
so
that
time
will
be
divided
up
in
different
ways
and
mentors
will
work
with
their
students
to
determine
what
works
best
for
the
mentors
and
the
students.
But
this
means
that
students
will
be
likely
writing
less
code.
E
I
can't
say
that
mentoring
will
be
cut
in
half,
but
it
will
in
all
likelihood
be
quite
reduce,
what's
required
of
you
as
a
mentor,
because,
what's
required
of
the
student
is
reduced,
so
hopefully
no
mentors
will
find
we'll
find
the
process
entirely
enjoyable
and
not
honor
us
and
not
feel
overwhelmed
by
it.
We
want
to
support
you
through
the
whole
process,
and
I
encourage
you
all
to
please
volunteer
as
mentors.
C
All
right,
so
that's
so
proposal
is
to
cancel
next
week's
meeting
in
favor
of
contributor
summit
any
objections.
This
sounds
great.
A
Thanks
then,
I
propose
to
stop
the
meeting
here.
I
mean
there
is
no
point
to
keep
it
for
30
minutes.
So
thanks
thanks
for
your
time
and
see
you
later
bye.