►
From YouTube: 2021 10 01 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
Clothes
hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting.
So
before
we
we
we
we
cover
the
main
topics.
I
just
want
to
remind
two
things
for
next
week:
we'll
have
jira
maintenance
next
wednesday.
So
if
you
go
to
status.js
you'll
see
the
announcements
there,
the
it
shouldn't
be
too
long.
I
mean
maybe
one
hour,
maybe
two
yeah.
In
fact,
it's
a
bit
long,
but
yeah
it's
needed.
So
everything
is
explained
and.
A
Second,
one
is,
as
you
mentioned,
security
release
next
week.
We're
gonna
have
a
security
release.
That
means
that
we
try
to
not
modify
jenkins
instances
related
to
the
release
environment,
so
just
pay
attention
if
you're
planning
to
to
apply
any
changes.
A
A
A
Maintenance,
theorem
yep,
that's
it!
So
what
are
the
main
activities
happening
in
the
infrastructure
project?
So,
like
a
lot
of
other
open
source
organizations,
we
will
participate
to
the
octoberfest
events,
so
it's
officially
starting
today.
So
if
you
are
interested
to
contribute
to
the
project
feel
free
to
register
for
the
oktoberfest,
we
prepared
some
issues
that
we
named
friend
issues.
Those
issues
are
located
on
the
jira,
the
jenkins
chira
instance.
A
We
try
to
identify
either
issues
that
do
not
require
strong
knowledge
on
specific
technology
or
do
not
require
strong
knowledge
about
how
touching
kids
infrastructure
work.
So
it
should
be
pretty
simple
but
anyway,
if
it's
not
feel
free
to
ask
questions,
and
we
are
there
to
help
you
and
if
you
have
some
time
to
help
us
review
prs,
that's
also
a
different
way
to
contribute
to
the
jenkins
and
to
the
octoberfest
this
month.
A
Next
topic
is
about
infrastructure
calendar,
so
you
may
have
seen
that
on
community.jenkins
that
I
o
this
week.
So
basically
I
created
a
new
a
new
calendar.
The
purpose
of
that
calendar
is
to
keep
track
of
important
deadlines
that
affect
the
jenkins
project.
The
jenkins
infrastructure
project,
such
as
certificates,
expiring,
yeah,
major
event,
whatever
that
canada
is
not
supposed
to
be
public,
we
don't
have.
I
mean
we
don't
have
critical
information
there,
but
we
want
to
be
able
to
put
important
information
there.
A
So
if
you
want
to
participate-
and
if
you
are,
if
you
already
contributed
to
the
jenkins
safra
project,
it
won't
be
an
issue
we
just
by
default,
don't
want
it
to
be
public,
that's
it.
A
So
the
challenge
that
we
are
facing
now
is
we
have
a
lot
of
data
that
wasn't
and
we
don't
want
to
lose
that
data,
and
so
we
are
looking
at
how
we
can
convert
those
information
to
let's
say
jenkins,
website
or
others.
So
the
first
thing
that
I
did
was
to
export
every
pages
to
html,
so
those
information
I
uploaded
them
on
a
new
git
repository,
which
I
named
jenkinson
for
a
slash
conference
data.
At
this
stage,
the
repository
is
private
same.
A
So,
if
you
are
interested
to
help,
I
would
be
glad
to
grant
you
access
to
the
repository.
A
I
don't
think
there
are
any
private
information
there,
but
because
the
content
of
confidence
I
mean
exist
since
before
I
joined
the
project,
I
can't
tell
it
for
sure
so
yeah,
that's
why
I
prefer
to
keep
private
for
now,
but
yeah.
So
if
you
want
to
contribute,
if
you
want
to
help
migrating,
the
information
from
there
to
a
better
location
feel
free
to
manifest
the
next
step.
A
One
of
them
would
just
be
to
deploy
a
simple
web
service
like
with
nginx
or
apache,
and
we
try
to
be
sure
that
we
can
that
we
can
match
that
you
can
map
existing
url
with
what
is
behind
the
nginx.
A
If
I
can
share
the
only
thing,
if
I
can
just
share
go
here,
so
you
can
see
what
that
looks
like
at
the
moment,
because
that's
the
annoying
part,
let
me
see
if
I
connected
on
github
with
this
account
yeah
perfect.
So
there
I
mean
yeah,
those
are
just
the
different
name
spaces
under
some
ecosystem
infrastructure
and
so
on.
A
So
if
I
let's
say
open
in
the
infrastructure,
you
can
see
that
for
every
pages
we
have
a
random
checksum
at
the
end
of
the
name,
we
have
a
random
checksum
at
the
end
of
the
name,
and
then
we
have
the
extension.html.
A
The
challenge
that
we
have
is
because
of
that
those
two
information.
We
cannot
directly
map
an
existing
endpoint
with
the
html,
and
the
second
thing
that
I
noticed
when
I
exported
the
information
is
sometime.
It
converts
a
close
character
to
an
underscore
and
sometimes
to
a
dash
to
dash.
So
it's
not
really
easy
to
to
identify
how
how
to
map
those
files
with
existing
with
existing
url.
So
that's
that's
the
next
challenge
that
we
have
to
face
now.
C
If
not,
do
you
want
to
try
a
folder
or
another
name,
and
then
you
can
add
a
fallback
like
okay,
if
not
the
case,
then
send
it
back
to
an
upstream
tomcat
php
whatever,
so
we
could
use
at
least
that
part.
So
that
means
using
a
specific
nginx
container
that
will
act
as
a
back
end
of
apache,
because
we
already
have
apache
viost
with
a
bunch
of
rules
already
made,
but
the
goal
of
the
nginx
container
is
that
it
could
be
standalone
and
we
could
try
this
locally.
C
That
would
be
only
a
back-end
service
and
it
provides
also
a
bunch
of
regex
on
the
virtual
hosting
matching
pattern
like
that.
She's
doing,
but
I
don't
know
if
apache
allows
the
same
thing
as
the
tri
files,
and
I
really
like
that
one,
because
it
will
be
okay.
Let's
try
that
url
with
the
plus.
If
it
doesn't
exist,
then
let's
try
that
url
with
the
menus,
otherwise
fall
back
to
a
default
page
that
say:
hey
no,
we
haven't
found.
Maybe
there
is
an
issue
or
go
to
the
listing
or
whatever.
B
C
A
Yeah
that
that
could
make
sense
that
would
be
nice
so
the
way
so
I
just
want
to
look
at
so
the
first
thing
to
keep
in
mind
is
we
could
just
reuse
that
massive
vote,
that
we
have,
that
we
have
on
the
conference
machine
that
really
writes
urls
to
a
different
location.
So
that's
one
of
the
things
that
we
need
to
to
implement,
so
we
could
just
have
yeah
a
docker
file
at
the
root
of
this
conference.
Data
repository
with
the
nginx
configuration
a
copy
of
the
vhost
and
so
on
and
see.
A
If
you
want
to
look
to
see
what
it
looks
like
right
now,
so
obviously
we
lost
the
css
and
if
we
want
to
navigate
it's
just
those
are
just
directories.
So,
for
example,
jenkins
it
will
list
all
the
files
and
then
you
can
just
open
one
of
them.
A
C
C
C
If
we
build
whatever
image
with
whatever
apache
engineering,
whatever
application,
then
these
urls
should
exist
on
the
build
image,
but
every
time
we
rebuild
it
and
that
list
of
links
could
be
a
great
start
for
any
contributor,
newbies
or
experienced,
and
it
should
help
also
as
a
self
documentation
to
track,
which
pages
still
need
to
be
migrated,
because
we
have
that
list
of
migration
paths
for
the
plugins.
I
don't
know
if
we
have
one
for
the
other
pages
of
the
confluence.
Wiki.
A
You
were
mentioning
that
we
can
work
with
that
with
other
people.
The
question
that
I
have
in
this
case
is
how
do
we
validate
that?
It
doesn't
contain
sensitive
information,
because
I
quickly
try
to
get
information
there
so
so
far,
security
contained
nothing
interesting
because
they
are
all
linked
to
jenkins
at
your
webpage.
C
That's
a
good,
that's
a
good
question.
I
think
we
should
ask
a
bit
broadly.
The
three
of
us
are
not
enough
to
answer
that
question.
I
think
that
might
be
blocked
to
the.
What
do
you
think
about
bringing
that
to
the
advisory
board
and
or
at
least
the
security
team,
just
to
be
sure,
because
there
is
a
bunch
of
content?
So
it's
really
hard
to
know
if
there
are
sensitive
data,
but
most
of
these
pages
were
public
that
that's.
Why.
D
A
For
the
security
part,
that's
what
I
noticed
does
not
I
mean
everything
is
gone.
B
Yeah
I
either
look
through
like
not
exhaustively,
but
I
couldn't
see
anything
and-
and
I
just
did
a
quick
scan
as
well
looking
for
through
the
copy
I've
got
locally
and
and
didn't,
and
daniel
had
asserted
that
he
hadn't
stored
anything
sensitive
there
and
the
last
time
he
ever
considered
storing
anything
sensitive
was
years
ago,
and
he
stopped
it
very
quickly
and
deleted
it.
So
yeah
he
told
me
the
same
thing.
B
Yeah
any
objection
mark
none
from
me.
I
think
at
least
for
me
it
would
be
a
great
help
for
hacktoberfest
if
it
were
public,
because
there
are
things
that
the
wiki
exporter
did
not
handle
correctly,
that
people
will
have
to
reconstruct
from
these
html
pages,
even
for
plugin
documentation.
I
found
that
with
the
ansible
plugin,
the
wiki
exporter
did
not
handle
the
table
export
correctly,
and
so
now
now
someone
has
to
reconstruct
those
those
tables
in
cases
where
there
was
a
table
inside
the
the
documentation.
A
Okay
sounds
good,
then
I
guess
the
next
step
for
me
just
to
turn,
but
put
it
I'll,
do
it
I'll?
Do
it.
A
I
don't
have
any
other
topic,
the
last
one
that
I
just
went.
Yep
sorry.
A
C
So
that's
related
to
that's
related
to
my
the
topic
I
want
to
bring
so
thanks
to
to
mark
feedbacks
from
yesterday.
It
seemed
we
have
issues
on
some
of
the
agents,
so
there
are
so
on
ci
jenkins,
I
o
so
first
of
all
the
ruby
agent,
but
only
us
the
infrastructure
timer
is
using
it
for
delivering.
So
it's
not
really
doesn't
have
a
lot
of
impact
for
the
rest
of
the
real
users.
However,
the
maven
11
windows,
aci
container,
are
not
allocated.
C
C
D
C
C
C
C
I've
realized
that
the
past
few
days,
each
time
after
a
cask
reconfiguration,
we
had
to
either
restart
the
controller
or
manually
use
the
uis
and
click
on
save,
so
that
one
will
be
written
on
the
one
book
for
if
we
have
an
issue
in
the
upcoming
days,
but
yeah
there
is
something
weird
like.
I
cannot.
B
Get
the
data
so
so
I've
had
I've
had
that
condition
repeatedly
on
my
my
jenkins
instance,
just
as
a
natural
thing
that
I
had
the
one
you
just
described
of
after
I've
reloaded
cask,
I
need
to
visit
an
agent
to
save
it
in
order
to
get
the
labels
to
apply
correctly.
I've
just
you've
been
using
as
a
standard
workaround,
but
that
was
just
me
assuming.
D
C
Okay,
so
we'll
try
this
one,
maybe
that
that
will
be
the
root
cause.
So
then
it
means
that
we
will
have
to
check
the
cask
export
once
it
work
for
sums
to
the
current
configuration
generated.
Okay,.
C
I've
tried
and
validated
that
I
see
that
it
cannot
schedule.
My
assumption
is
because
four
cpu
should
be
terrifically
two
pods,
but
it
sounds
like
that.
Kubernetes
is
allocating
it's
counting
one
cpu
for
itself
or
for
another
board
on
each
machine,
which
means
you
only
have
seven
cpus
available
on
each
worker
node.
So
only
one
pod,
the
maximum
scale
was
25.
C
So
that's
also
no
story,
50
50
machines,
so
that
will
count.
My
proposal
is
to
increase
the
size
of
each
worker
node
and
with
the
octoberfest,
to
close
the
subject
increase
for
this
month.
The
maximum
size
of
the
autoscaling
cluster,
then,
to
validate
that,
I
plan
to
run
a
bom
pull
request
bill.
One
of
these,
which
failed
past
week
just
to
validate
that
it's
able
to
quickly
handle
the
scaling.
A
I
have
one
last
pitch,
so
we
have
we
have.
We
are
three
minutes
before
the
end
of
the
meeting,
so
there
is
just
one
that
I
want
to
briefly
cover,
so
we
faced
a
bunch
of
issues
this
week
with
the
accounts
app
so
with
accounts
touching
things
that
I
owe
so.
A
I
won't
go
back
to
all
the
issues
that
we
faced
that
we
fixed
this
week,
but
I
also
want
I
I
just
want
to
take
some
time
to
to
remind
why
we
are
not
able
to
jump
on
beta
that
I
can't
search
in
the
lego,
and
the
only
reason
for
that
is
because
we
run
extra
validation
in
the
account
app,
and
so
we
would
need
to
implement
those
validation
on
piclock,
based
on
the
document
on
keyclock
documentation.
It
shouldn't
be
too
difficult
to
to
overwrite
the
class
that
implement
the
registration
but
yeah.
A
We
just
need
someone
to
jump
into
that
topic
and
try
to
confirm
the
rules
that
we
have
on
accounts
of
thinking
that
io
and
what's
needed
on
beta.accounts
searching
value.
A
That's
the
only
reason
why
we
are
still
using
accounts
searching
kinsale,
so
it's
to
avoid
situations
such
as
someone
creating
an
account
using
dash
admin,
for
instance,
so
yeah
we
have
a
bunch
of
rules
that
need
to
be
applied
in
and
we
we
also
register
some
specific
account
that
we
want
to
be
sure
that
nobody
used
that
specific
name
as
a
user
account
so
yeah,
I'm
just
inviting
someone
who
wants
to
play
with
the
cloak
and
override
it
for
configuration.
A
That's
it
for
me
in
the
last
topic
sounds
like
we
can
stop
the
meeting
two
minutes
before
the
end.
Us
thanks.
Everybody
have
a
great
weekend
goodbye.