►
From YouTube: 2021 01 26 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
I
have
everybody
welcome
for
this
new
jenkins
surfer
meeting
the
first
topic
to
the
agenda,
which
is
the
state
of
silvarion
starvieron.com,
so
servers
in
our
infrastructure.
It
has
been
done
for
almost
months
and
last
week.
I
think
that
was
last
week.
We
we
put
it
back
in
our
infrastructure,
but
we
still
have
one
remaining
issue
with
it,
which
is
the
ip
so
based
on
the
ip
mirror
bits,
but
basically
geoip
assign
it
to
the
united
states.
A
I
assume
I
think
it's
okay.
For
now
I
I
have
a
draft
of
a
blog
bus
to
communicate
about
recent
change
on
the
mirah
infrastructure.
A
A
B
A
On
that,
on
that
specific
release,
garrett
made
a
small
golang
script
to
detect
the
latest
version
of
jenkins
and
so
right
now.
The
script
that
you
have
is
a
python
script
that
they
take
the
latest
weekly
version,
but
do
not
handle
very
well
the
latest
table
version,
and
so
the
thing
is
because
it's
a
python
script.
It
also
rely
on
python.
A
The
the
the
thing
that
garrett
did
was
to
have
a
small
binary
that
we
could
add
to
the
docker
image
that
we
used
to
the
release,
and
so
it
correctly
fetched
the
latest
stable
release
as
well.
So
in
this
case
it
would
be
2.263.3.
A
I
mean
we
are
still
testing
it,
but
I
think
it
will
it
will.
It
will
simplify
the
the
release
checklist,
at
least
for
stable
releases.
C
Yeah,
I
added
a
few,
but
I
added
a
few
little
things.
Let's
let
if
you
pass
in
like
lts
as
the
version
identifier,
it
will
actually
pull
out
the
lt
latest
lts
version,
so
just
filters
them
all
out,
which
I
think
is
what
you
were
describing
the
behavior
that
you
wanted
to
do.
So
I
I
put
on
the
chat
there,
the
link
to
the
repo
it's
being
built
as
binaries
and
yeah.
C
There's
a
docker
image
there,
I'm
just
playing
with
the
docker
multi-arch
support,
see
if
I
can
get
it
to
actually
compile
inside
there.
A
But
basically
the
way
it's
working
is
it
reads
the
maven
repository,
so
the
metadata
xml
file
and
so
for
the
weekly.
It's
fairly,
it's
easy
because
it's
fetch
for
the
latest
release,
but
for
the
stable
it's
a
little
bit
more
complicated,
because
we
have
many
different
kind
of
releases
we
have
releases
with
which
have
characters
inside
and
so
yeah
there
are.
I
mean
that
was
not
as
simple
to
pass
every
release
into
so
so
guaranteed
the
last
mile
to
to
have
it
working
for
the
test,
which
is
nice
so
so,
and.
B
A
So
garrett
should
should
I
will
I'll
work
with
garrett
that
med
garage
should
open
a
pull
request
on
the
release,
repository
so
jenkins
for
a
slash
release
to
and
and
maybe
yeah
on,
that
release
to
to
use
that
script
instead
of
python,
one
and
otherwise
inside.
So
we
have
a
docker
image
that
we
call
jenkins
infrared
packaging
that
contain
a
lot
of
things,
basically
all
the
tooling
needed
to
do
the
release
and
the
packaging.
A
So
it's
a
quite
big
image
like
one
gigabyte
of
this
space,
and
so
we
should
also
put
that
small
binary
there
I'll
put
the
link
okay.
A
B
Yeah,
sorry,
I'm
being
vocal
this
time,
so
debian
stretch
has
reached
the
end
of
its
life.
This
that's
debian,
9
official
end
of
support
was
july
of
2020.
It's
now
in
the
long
term
support
mode,
but
that's
the
base
for
our
default
docker
images
for
jenkins,
slash
jenkins,
colin
lts
and
for
jenkins
jenkins,
colon
latest.
B
A
Considering
that
there
are
other
efforts
on
cleaning
up
the
docker
image
that
we
have,
should
we
do
a
short
blog
post
on
all
the
changes
that
we
want
to
do
on
the
docker
images.
So
we
have.
Obviously
we
have
this
change
coming
from
from
debian,
but
cara
is
also
working
with
debian
to
to
duplicate
some
old
images
and
to
also
switch
image.
A
So
we
are,
we
provide
inbound
agent
with
tools
like
maven,
byte
and
ruby
and
so
on,
and
those
rely
on
the
default
docker
image
which
most
of
the
time
run
as
roots,
and
so
we
are
currently
changing
that
behavior
to
use
a
jenkins
user
by
default.
So
we
are
just
adding
the
jenkins
user
to
those
images,
and
so
the
idea
is
to
replace
those
that
we
have
right
now.
A
The
problem
is
it's
a
breaking
change,
because
all
the
people
who
rely
on
those
images
will
soon
move
from
using
the
root
user
to
the
jenkins
user.
So
we
want
to.
We
want
to
to
notify
people
enough
in
advance
about
that
breaking
change.
I
mean
it's
not
a
big
deal
in
a
way
that
the
root
user
will
still
be
there.
If
people
really
want
to
use
a
the
root
user,
but
yeah
that
is
just
too
communicate
about.
B
A
And
that's
one
of
the
thing
and
which
is
regarding
the
inbound
agent
and
another
one
I've
been
thinking
would
be
to
clean
up
old
jenkins
image
that
we
do
not
recommend
our
user
to
use
again.
So
the
one
that
I
have
in
mind,
I
think,
is
jenkins,
ci,
slash
jenkins,
the
pollution
image
and
stuff
like
that.
B
B
On
this
topic,
I
at
least
for
me
that
sounds
great.
I
I
like
that.
We
should
plan
that
together,
our
damian
olivier
work
together,
good
good
insight,
thanks.
A
The
last
peak,
so
no,
I
have
two
last.
I
have
one
last
piece
that
I
would
like
to
to
talk
before
we
we
mentioned
the
contributor
summit,
so
in
around
two
weeks
in
around
two
weeks,
we'll
have
the
first
them
so
we'll
have
a
virtual
booth
at
first
them,
and
I'm
just
wondering
if
we
should
not
have
like
some,
maybe
short
demo
about
how
we
manage
our
infrastructure.
A
Let's
say
how
we
deploy
jenkins
in
the
jenkins
project,
so
maybe
we
can
prepare
some
demos
that
we
would
do
on
saturday
morning
or
saturday
afternoon
I
mean
with
whoever
is
interested,
so
we
we
could
showcase
how
we
deploy
that
same
threaded,
ci
or
really
the
ci.
A
And
so,
which
brings
me
to
the
last
topic,
which
is
also
run
for
them,
the
contributor
submits
mark.
I
think
you
wanted
to
to
bring
this
one
so.
B
Yeah,
so
so
before
we
go
away
from
this
fosdem
stand
olivia
did
you
want
to
share
further
on
what
you're
envisioning
there?
I
think
that
sounds
like
a
great
idea.
So
the
demonstration
are
you
envisioning
that
live
or
is
it
playing
a
recording
of
a
demo.
A
What
the
uses,
so
I
don't
we
won't-
have
access
to
to
recording.
So
basically
what
fosdem
provides
us,
they
provides
us
a
website
available
to
people
who
visit
the
first
them.
They
provide
us
a
matrix
server,
so
we
would
have
access
to
a
room
which
will
be
something
like
stand
dash
jenkins,
something
like
that,
and
it
would
be
nice
to
to
put
a
small
agenda
there
and
we'll
also
be
able
to
use
chitsy
if
we
want
to
stream
an
information.
So
I
was
more
thinking
to
let's
say:
yeah.
A
D
A
I'm
not
working
on
that,
so
I
have
I
mean
okay,
I
will
personally,
I
have
no
idea.
Okay,.
B
So
I
thought
that
alyssa
tong
was
working,
that
if
she's
not
propose
it
to
her
in
advocacy
and
outreach
because
I'd
be
happy
to
be
there
as
an
ask
me
anything
session
on
a
particular
plugin,
I'm
confident
tim
is
willing
to
be
there
as
well
on
some
other
plugins.
Aren't
you
tim
configuration
is
code.
I
could
just
ask
me
anything.
Configures
code.
E
B
A
Yes,
regarding
the
last
topic
for
today,
which
is
a
contributor
summit,
so
the
contributor
summit
is
a
nice
moment
where
we
can
look
at
what
we
did
in
the
jenkins
infra
project.
I
like
highlight
major
changes
and
also
discuss
about
what's
coming
for
at
least
six
months
or
coming
for
the
year,
and
so
that's
also
a
really
good
opportunity
for
every
committee
members
to
maybe
to
to,
I
would
say,
encourage
to
follow
a
specific
path.
So
if
you
have
any
ideas,
I
think
that's
the
right
time.
A
B
As
talking
about
hey,
what
does
it
mean
to
in
heighten
the
security
of
the
process
we
use
to
release
code,
including
plugins,
etc,
and
so
so
it's
I
was
thinking
with
tim
as
release
officer
and
olivia
you,
as
as
infrastructure
officer.
We
may
want
to
to
have
some
conversations
with
daniel
and
say
all
right.
Are
there
things
where
we
might
consider?
B
The
way
I've
been
the
way
I've
been
hoping
was
that
people
would
make
comments
in
this,
this
agenda
document
and
suggest
tracks
that
they
think
would
work.
So
I'd
started
this
security
track
as
as
an
idea
and
and
as
I
look
at
security
track,
I
thought
oh,
it
may
be
that
we
need
olivier
there
and
we'd
gareth
there,
and
we
need
tim
there
to
have
conversations
about
those
topics.
A
A
A
Okay,
I'll
try
I'll
try
to
look
at
it,
but
yeah.
Definitely
the
contributor
submit
is,
I
think,
really
important
and
in
the
past
we
got
many
great
feedback,
so
yeah
I'll
try
to
take
the
time
to
look
at
it
correctly.
D
I'll
just
jump
in
and
and
say
the
cdf
has
a
security
sig,
so
it's
not
fosdem
or
contributor
summit
related.
But
on
that
on
that
idea
of
security
there
there
is
this
quite
interesting.
Sig,
that's
going
on
on
security
and
those
who
are
involved
with
that
with
the
jenkins
project
may
want
to
start
attending
it.
I
can
put
the
link
in
the
meeting
next
actually
I'll.
Stick
it
here
as
well.
B
I
was
assuming
we
would.
It
was
more
thinking
about
gaps
than
about
audit,
but
audit
for
me
was
going
to
be
a
if
if
we
do
an
audit
and
for
instance,
the
docsig
will
do
an
audit
of
doc
content
as
prep
for
this
summit
and
then
we'll
discuss
the
results
of
that
audit
in
the
in
the
summit
itself.
But
but
my
thought
was
that
that's
audit
is
a
prep
rather
than
a
an
outcome
of
this.
A
Suggestion
all
right,
then
I
think
we
are
done
thanks
for
your
time
and
see
you
later
bye-bye.