►
From YouTube: 2020 12 08 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
Okay,
olivia
george
hi
everybody
welcome
for
this
new
jenkins
infrastructure
meeting.
Today's
we
are
going
to
talk
about
the
releases,
few
change
coming
for
the
jenkins
releases
and
we
also
have
topics
regarding
jira
fixes,
jira
configuration
the
account
app
and
many
other.
So
what
I
propose
is
we
start
directly
for
jenkins
3d.
So
today
we
did
jenkins
weekly
release.
A
Most
of
the
things
were
correct,
accepted
that
we
are
having
issues
to
build
the
docker
image
for
the
latest
version.
We
are
currently
investigating.
Why
so
very
brief
very
quickly,
we
are
running
bats,
to
run
some
tests
on
the
docker
images
and
for
some
reasons
the
tests
are
not
passing
it's
kind
of
the
it
works
on
my
machine,
but
in
this
case
it
doesn't
work
on
the
ci
environment,
so
we
are
still
investigating
specifically
for
that
any
question.
A
Anything
to
add
hello,
no
hi
tim.
The
next
topic
also
that
I
want
to
mention
with
the
jenkins
release.
So
basically
it's
specific
it's
regarding
the
azure
file
storage
issue
we
had
several
weeks
ago,
so
microsoft
came
back
to
me
over
the
weekend
to
say
basically
nothing
really
new.
They
explained
that
there
is
a
limit
on
the
number
of
files
we
can
open.
At
the
same
time,
that
limit
is
two
thousand.
A
I
wasn't
able.
I
mean
I'm,
I
I
clean
up
that
that
mean
that
limit,
because
they
have
instructions
about
cleaning
that
limits.
So
I
have
the
feeling
that
they
weren't
able
to
identify
the
root
cause
of
the
issue
right
now.
The
thing
is,
at
least
for
the
moment.
The
azure
file
storage
has
been
working
for
two
weeks
or
three
weeks.
I'm
not
I'm
not
sure.
A
A
I'll
probably
do
that
tomorrow,
I'll
have
some
time
to
finish
this
I
didn't
want.
I
didn't
want
to
to
to
too
much
the
prs
related
to
that,
because
I
wanted
to
be
sure
that
the
release
last
week
was
was
okay
and
weekly
today
as
well,
but
now
we
should
be
ready
to
roll
back
everything
to
the
previous
situation.
B
Olivier
good
question
regarding
the
docker
image
issue,
I
mean
the
windows,
images
are
published
and
the
problem
is
just
the
linux
images
and
that
says
command
not
found.
Is
that
not
straightforward?.
C
It
is
straightforward,
but
there
is
a
pr
open
to
resolve
that.
That's
it's
a
typo
by
me.
Unfortunately,
you
can't
we
don't
test
any
of
that
part
as
part
of
the
pr.
So
when
a
pr
was
merged
to
debug
something
else,
it
broke
the
release
part,
but
we're
struggling
to
get
the
pr
to
fix
it
through
the
build
system
because
all
of
the
bats
things
are
failing.
B
C
C
We
were
just
trying
to
understand
whether
something
else
had
been
introduced
in
sort
of
inadvertently,
because
everything
was
failing.
A
Thanks
for
that
explanation
also,
this
reminds
me
we
are
now
monitoring
each
time
we
do
release.
So,
each
time
we
published
a
new
version
to
the
maven
repository,
we
have
metering
in
place
that
detects
if
debian,
redat,
ceos
and
windows
packages
are
available,
but
we
are
not
monitoring
if
the
docker
image
are
available,
so
that
was
the
first
step
to
be
able
to
measure
the
fact
that
when
we
do
release,
we
try
to
have
that
that
moment
very
short
between
the
moment
we
publish
the
release
and
the
problem.
A
The
moment
we
generate
the
different
artifacts.
We
still
have
some
ongoing
work
on
that
we
should
come
in
the
coming
weeks.
A
If
another
question
I'm
going
to
move
to
the
next
quest
to
the
next
topic,
so
we
we
noticed
that
when
we
migrated
jira
to
the
linux
foundation
for
some
reason
the
account
app
stopped
creating
users
in
jira,
so
instead
of
relying
on
the
account
app
to
create
the
user.
I
made
few
changes
this
morning.
A
Basically
now,
when
someone
try
to
login
on
jira,
if
the
user
does
not
exist,
it
imports
the
user
directly
from
ldap,
so
it
create
a
new
user
locally
on
jira
from
based
on
ldap,
then
we
can
modify
the
display
name
and
the
email
from
jram.
I
mean
this
is
not
ideal,
obviously,
but
we
just
realized
that
multiple
people
were
modifying
the
display
name
in
the
email.
So
for
now
that's
the
current
situation.
A
Everything
is
back
to
normal
now,
so
the
good
thing
is,
we
should
be
able
to
remove
the
account
up
to
replace
it
by
kick
lock.
I
still
have
to
to
review
the
account
app
code
to
be
sure
that
there
are
not
other
specificities
done
on
the
icon,
app.
B
So
one
thing
I
just
noticed:
I
I
realized
that
we
discussed
this
yesterday
when
there
was
a
problem.
This
basically
now
means
that
the
security
team
is
in
the
situation
where
I
always
was
against
a
user
account
migration,
because
now
there
can
be
plugin
maintainers
that
do
not
have
a
jira
account.
E
You
know
the
security
team
daniel,
I'm
not
sure,
I'm
capturing
the
the
concept
correctly.
So
there
is
a
user
account,
but
it
only
you
use
the
jira
user
account
to
ping
someone
with
a
security
issue,
but
that
jira
user
account
does
not
exist
until
the
user
has
logged
into
jira.
Did
I
say
it
correctly.
A
Yes,
yeah,
so
that's
the
difference
so
previously
on
the
accounts
app
when
you,
when
we
created
a
user,
we
automatically
inject
that
user
in
the
jira
database,
which
is
not
the
case
anymore
in
the
current
situation.
So
in
this
case
that's
the
jira.
We
import
the
user,
but
only
when
the
user
try
to
login
so
yeah
again,
it's
an
imitation
for
for
danielle.
I
don't
have
a
good
answer
right
now
for
that
contract.
B
Well,
the
yeah,
the
one
who's,
the
one
who's
asking
for
the
hosting
request,
but
if
you
take
over
a
dormant
plug-in,
you
may
have
never
accessed
jira,
especially
if
you
track
issues
for
github
so
yeah.
I
I
acknowledge
that
it's
not
the
default
flow,
but
there
is
a
valid.
B
B
A
Okay,
no!
No!
That's
a
good!
That's
a
good
remark!
I'm
going
to
check
if
the
ldap
configuration
doesn't
allow
me
to
synchronize
user
on
a
regular
basis,
let's
say
once
a
once
a
day
or
something
like
that.
A
Yeah
thanks.
I
put
studio
agenda
the
next
topic,
which
is
windows,
windows,
docker
image,
but
I
don't
think
anything
changed
on
that
topic.
Garrett.
A
Perfect
before
we
talk
about
seattle
jenkins
that
I
o,
I
also
want
to
to
remind
people
that
I
deploy
a
service
named
status,
touching
kenzario,
so
the
idea
of
the
service
is
just
to
provide
feedback
to
the
people,
so
it
worked
in
two
ways:
the
first
one
is.
We
just
write
a
markdown
that
we
publish
like
each
repository
and
that
mark
don't
provide
information
about
a
coming
maintenance,
a
current
issue
or
whatever
the
idea
just
provide
a
central
place
where
people
could
be
notified
about
ongoing
work.
A
Then
also,
I
started
creating
basic
data
docs,
so
I
insert
datadog
http,
so
I
just
want
to
provide
basic
information.
If
the
service
is
really
running
or
not,
I
mean
it
does
not
mean
that
the
service
is
running
correctly.
It
just
means
that
just
basic
information
right
now,
I
didn't
spend
a
lot
of
time
on
it.
So
that's
a
really
good
time
to
provide
feedback
on
that
service.
A
The
only
thing
that
I
would
like
to
work
on
it
if
we
decide
to
stick
to
it
is,
I
would
like
to
provide
more
basic
monitoring,
so
so
provide
monitoring
for
the
other
services.
So
right
now
we
only
provide
for
get
the
jenkins
alio
updates
the
jenkins
leo
and
package
touching
kids.
Are
you
but
yeah,
just
embedding
more
iframes
any
suggestions
here.
B
A
quick
question
I
may
have
asked
this
before:
isn't
the
usual
approach
to
put
a
status
page
on
a
separate
domain,
so
that
even
dns
issues
would
not
affect
the
status
page.
I
I
know
nothing
about
this,
but
that
seemed
the
the
motivation
for
some
of,
like
I
don't
know,
cloud
copy
status,
github
status.
A
A
I
think
we
used
to
have
more
jenkins
domains,
but
I
don't
have
access
to
them.
So
I
think
it's
it's
kind
of
okay.
I
think
it's
an
accidental
solution
to
have
it's
running
on
the
same
domain,
then
checking
that
I
o.
D
B
E
A
Was
it
so?
The
reason
why
I
put
the
iframe
is
because
we
don't
have
public
monitoring
and
the
thing
is
I
regularly
have
requests
from
people
saying:
is
it
me
or
that
website
is
down,
and
so
that
that
that
was
the
motivation,
so
yeah
in
this
case
I'm
just
providing
the
information
over
the
last
week.
So
you
can
easily
guess
if
something
is
wrong.
A
So
if
you
don't
have
any
data
since
one
day,
let's
say
you
know
that
something
wrong
is
happening
since
one
day
and
if
the
status
page
say
says
that
everything
is
up
and
running,
because
nobody
provided
informed
that
that
information,
everybody
can
open
a
pr
and
say
there
is
something
wrong.
Let's
say,
with
a
link
to
the
to
the
mailing
list
or
turning
to
any
information
that
could
be
useful
to
the
other
people.
So
I
did.
A
I
did
some
quick
experiment
based
on
the
atlassian
status
page
and
this
one
ccstates
the
dot
lesson
status
page.
We
could
have
it
part
of
the
open
source
sponsoring
program,
it's
more
advanced.
A
We
have
better
notification
and
so
on,
but
it
will
remain
an
application
where
you
have
to
log
login
provide
a
password
and
only
privileged
people
can
modify
the
information.
What
I
like
with
cst
is
everybody
can
open
a
pr.
Everybody
can
say
there
is
something
wrong
with
that
service.
Everybody
can
provide,
link
to
let's
say
twitter,
reddit
or
or
whatever
the
information
you
want
to
provide,
and
then
other
people
can
catch
up.
So
it's
not
only
the
infrastructure
team
providing
information
if
the
service
is
up
or
not
and
providing
the
default
monitoring
to
say.
A
Okay,
that
service
is
responding.
It's
already
a
good
information
for
the
person
who
want
to
open
a
pr
because
yeah
that,
if
the,
if
we
don't
have
any
response
time,
then
then
something
wrong
is
definitely
happening,
and
if
nobody
is
talking
about
that
on
the
mailing
list
or
on
rsc,
there
is
definitely
something
wrong
here.
A
So
that
was
the
motivation.
I
think
it
could
be
really
useful
if
we
also
plan
to
notice
in
advance
when
we
do
maintenance.
So
if
you
look
right
now
on
the
status
page,
you
see
that
I
sent.
I
sent
a
notification
saying
that
we
are
going
to
update
a
community's
cluster.
This
was
a
test,
I
think,
for
instance,
the
next
time
we
do
activities
cluster
upgrade.
Even
if
even
if
we
are
not
expecting
any
downtime,
it
could
be
useful
to
just
notify
people
one
week
in
advance
to
know
that
they
may
have.
E
A
So
yeah
the
thing
is
delta
thinks
the
first
one
is
you
can
if
you
know
that
the
maintenance
window
will
be,
let's
say
one
hour,
you
can
open
a
ticket,
you
can
publish
that
markdown
fine
and
you
can
say
there
is
a
windows,
maintenance
and
the
service
will
be
done
for
one
hour,
so
you
don't
have
to
to
eject
more
information
once
your
maintenance
windows
is
done,
I'm
not
sure
if
we
have
to
create
an
incident
when
the
service
is
done
for
a
few
minutes,
but
if
we
know
that
the
service
will
be
done
for
let's
say
20
or
30
minutes,
maybe
that
would
be
nice
to
add
some
information
there
and
I
think
when
we
do,
let's
say
a
cigarette
version
update
that
could
be
useful
to
put
information
there,
because
I
think
last
week
I
saw
people
asking
if
the
service
was
done
or
just
maintenance,
and
it
was
just
the
maintenance
but
yeah.
B
I
I
just
wanted
to
add.
I
really
like
the
graphs,
because
an
experience
that
I
had
several
times
over
the
last
few
months
with
github
is
I'm
basically
on
github
all
day
and
something
starts
feeling
broken
slow
or
not
right
and
I
look
at
on
github
status
and
there's
nothing
and
I
look
at
github
status.
10
minutes
later
and
I
noticed
10
minutes
before
they
did.
A
Okay
thanks,
I
proposed
to
move
to
another
topic,
so
I
want
to
to
say
that
we
are
starting
to
investigate
how
we
can
improve
the
stability
of
ci
dodging
that
io
and
we
are
looking
at
ways
to
run
seattle
jk,
that
is
to
cooperative.
So
in
order
to
move
most
of
the
agent
on
kubernetes,
this
would
be
a
quite
major
refactoring,
because,
right
now
we
both
use
containers
and
virtual
machine
running
docker,
docker
login
and
the
jenkins
file
would
not
be
compatible.
A
So
we
are
still
at
the
beginning
of
the
process
to
see
how
we
can
improve
seattle
jenkins
audio,
to
be
sure
that
it's
reliable
and
yeah
we
are.
We
are
trying
to
identify
the
different,
the
different
areas
that
need
to
be
improved.
We
really
would
like
to
see
like
the
best
showcase
about
the
best
way
to
run
shankins
on
communities,
which
is
something
that
interests
a
lot
of
people
today
so
yeah.
If
you
are
interested
to
provide
feedback,
this
is
a
project
that
we
are
starting
now.
A
Sponsoring
so
not
not
only
our
record
at
once
so
before
we
we
talk
about
the
horrible
sponsoring.
I
had
a
look
to
the
to
the
state
of
the
infrastructure
sponsoring
from
ios
and
we
are
almost
running
out
of
credits,
so
I
think
we
still
have
one
month
in
front
of
us,
so
I
would
like
to
re-engage
with
amazon
folks
to
see
if
they
are
interested
to
continue
the
sponsoring
or
you
know.
Basically,
what
was
the
current
state
there.
G
Does
it
does
it
correlates
to
the
previous
topic?
I
mean
if
we
start
moving
some
workload
of
ci
jenkins
io
this
this.
E
But
actually
isn't
it
isn't
a
move
to
kubernetes
a
good
thing,
because
if
we
needed
to
move
to
some
other
hosting
to
google
or
to
to
ibm
cloud
or
oracle,
whoever
donates
to
us
kubernetes
is
likely
much
more
portable
than
our
current
than
our
current
azure
based
infrastructure
right.
So
so.
For
me,
it
feels
like
kubernetes
is
a
good
thing,
no
matter
whether
we
stay
with
aws
or
not,.
A
So
yeah
so
you're
right,
you're
right,
but
what
I
want
to
add
today
and
I'm
concerned
the
reason.
The
reason
why
we
decided
also
to
move
to
communities
was
to
have
a
better
portability
right
now.
Each
time
we
I
mean
we
moved
from
azure
to
amazon.
We
moved
from
amazon
to
azure
azure
to
amazon,
and
so
we
had
compatibility
issues
and
it
forced
us
to
to
fix
small
issues.
The
idea
here
is
would
be
to
use
kubernetes
agents
so
wherever
we
run
the
service,
it's
fine.
The
main
difference
is
one
of
the
limitations.
A
Until
two
days
to
use
amazon
to
run
communities
was
the
amazon
is
still
owned
by
club
b,
so
only
cloud
these
employees
could
can
work
on
it.
So
damien
started
deploying
inquiries
cluster
on
amazon,
so
we
could
provide
them
as
a
cluster
and
then
we
could
work
on
citing
the
io
the
same
way
well,
managing
the
other
services
so
using
harm
charts.
A
If
we
don't
have
sponsoring
on
amazon,
we
may
have
to
look
for
other
solutions
for
the
infrastructure
I
mean
for
for,
for
where
we
run
the
communities
cluster,
but
the
work
to
run
champions
on
kubernetes
to
the
work
to
identify
how
we
monitor
efficiently,
to
see
either
jenkins.
That
is
how
we
run
how
we
write
a
jenkins
file
to
run
on
kubernetes
the
january.
A
C
In
a
kind
of
related
note,
has
anyone
looked
at
the
kind
of
docker
deprecation
from
kubernetes
and
the
potential
impact
that
that
might
have.
G
For
us
yes
to
be,
to
be
quite
honest,
there
is
nothing
to
worry
about,
at
least
for
the
use
case
of
agents
running
on
kubernetes.
G
Because,
in
fact,
it's
it's
only,
let's
say
black
box
how
kubernetes
interact
with
the
container
engine.
The
container
engine
by
default
is
container
d,
which
is
the
same
as
docker.
G
G
However,
I
will
say
this
will
be
tackled
on
by
the
security
part,
because
kubernetes
is
theoretically
able
to
run
docker
engine
as
rootless
container,
so
that
will
be
basically
part
of
defining
a
jenkins
file
that
say
on
that
board.
I
have
a
container
with
a
docker
engine,
which
is
only
mine,
no
shared
dependency,
and
if
we
can
ensure
that
this
run
with
the
security
constant
we
could
have
on
such
a
cluster,
then
we
don't
have
to
care
about
the
outer
container
engine,
which
is
managed
by
kubernetes
without
us.
Knowing
anything.
B
E
D
So
it
makes
the
eye
more
complicated.
We
are
using
it
for
ci,
so
it's
things
like
services
that
use
things
like
test
containers
and
want
to
spin
up
like
integration,
test
databases
and
that
sort
of
thing
I
don't
think
it
would
affect
us
directly.
D
I
don't
know
of
any
places
right
now
isn't
in
the
current
state,
where
we
mount
the
docker
software,
but
it
certainly
affects
people
who
use
jenkins
as
a
ci
service
and
runs
their
jobs
in
pods,
because
it's
fairly
common
to
mount
the
docker
sockets
so
that
you
can
run
at
least
containers,
if
not
other
things.
G
Yeah,
the
the
thing
is
that
it's
really
risky
in
term
of
mounting
the
docker
circuit
is
something
risky,
so
we.
G
Cluster
yeah,
basically,
you
have
access
to
the
docker
socket.
You
are
super
user
of
the
underlying
host,
unless
that
docker
socket
is
restricted
with
a
containerized
and
isolated
docker
engine
which
runs
as
rootless,
but
this
depends
on
the
kernel
of
the
host
you
are
running
in
order
to
to
have
docker
inside
docker
nested
containerization
with
the
right
level
of
isolation.
That's
why
most
of
the
time
the
ci
pattern
is
when
you
need
such
case
like
running
test
container
that
will
run
docker
run
stuff.
G
G
D
D
A
I
just
proposed
to
we
stay
focused
to
the
because
we
are
almost
running
late,
so
we
are,
I
mean
we
are
running
late
now,
so
what
I
propose
is
to
quickly
cover
the
last
topic,
which
is
about
sponsoring
her.
By
do
you
have
some
inputs
here.
E
I
I
A
Cost-Saving,
while
we're
also
talking
about
sponsoring
there
is
something
that
I
forgot,
we
are
paying
for
the
jenkins
silver
project,
github
accounts.
So
it's
something
like
300
per
year
and
now
github
changed
several
months
ago
to
provide
up
to
10
private
git
repositories,
so
we
could
switch
to
the
free
plan.
Now
I
don't
know
if
you
have
any
inputs
there,
or
maybe
I
should
contact
gtap
support.
I
know
that
we'll
have
to
pay,
I
mean
by
the
end
of
the
month,
so
I
just
want
to
be
sure
that.
D
A
B
The
jenkins
ci
organization
is
a
free
organization.
We
have
no
private
reports
there,
it's
completely
open
source.
However,
the
jenkins
ci
cert
organization
has
a
sponsorship
that
tyler
organized
we
currently
have
like
300
private
repositories
there
and
it
we
basically
have
a
hundred
percent
of
forever
coupon.
D
A
Okay
thanks,
I
proposed
to
to
close
the
meeting
here.
We
are
already
four
minutes
after
the
line,
so
I
propose
to
continue
the
discussion
on
our
team
and
on
the
meetings.
Thank
you
for
your
time
and
see
you
later
bye.