►
From YouTube: 2023 06 29 Docs Office Hours
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
Club
welcome
it's
the
29th
of
June
2023.
This
is
documentation,
office
hours,
topics
for
today,
Google
summer
of
code,
administering
Jenkins
on
kubernetes,
and
if
those
were
the
only
two
things
we
got
to
I
would
be
fine
with
that
I
think
the
other
topics
I
have
to
forewarn
I'll
be
out
and
out
of
the
office
topic.
Others
I
think
can
wait
anything
that
you
need
to
add
Bruno.
No!
A
B
Yes,
we're
almost
done
with
Java
Maven
tutorial
and
I.
Don't
want
to
sound
too
enthusiastic,
but
it
should
be.
The
tutorial
should
be
much
much
smaller
than
the
existing
one
and
much
simpler
without
Docker
in
docker,
which
is
a
good
thing
for
various
reasons.
We'll
see
that
on
next
Thursday
I
hope
the
demo
goes
well
and
I'm
even
trying
to
run
it
onto
Raspberry
Pi
I'll.
Let
you
know
if
ever
that
works,
but
yes,
I
know
it
doesn't
work
for
Windows
users
yet,
but
we'll
think
of
Windows
users.
A
B
Yeah
tutorial
I
should
merge
it
later
today
or
maybe
tomorrow,
but
I've
just
edited
it
with
gitpod
a
few
minutes
ago,
and
it
was
working
for
me.
There
are
still
some
hiccups
here
and
there
it's
not
perfectly
Polished,
but
it's
doing
good
work.
Nonetheless,
I
may
have
gone
a
little
too
far
with
automation,
but
we'll
see
you
know,
I
thought
that
it
was
too
difficult
to
add
to
the
end
user
to
go
to
GitHub
for
repo
and
then
clone
it
locally.
B
B
B
Here,
yes,
it's
Joseph,
Jenkins,
init.sh
and
Maven,
and
it
just
works,
but
I
know
we're
excluding
Windows
user,
which
is
bad.
So
in
the
end,
what
I
end
up?
What
we
will
end
up,
hopefully,
is
just
Docker
compose
up
minus
minus
build
for
just
every
platform
and
it
should
work.
A
A
A
Excellent,
all
right,
so
the
docker
compose
project
making
great
progress
anything
else
you
want
to
share
on
that
project.
No!
Thank
you!
Mark,
okay.
So
next
topic
was
one
where
I
think
it's
it's
a
a
group
exercise
for
us
to
review
this
tanu
Sharma
submitted
a
very
solid
pull
request
a
month
or
two
ago
to
the
documentation
and
is
now
proposing
a
new
pull
request.
This
one
is
a
much
bigger.
How
do
we
do
administering
Jenkins
on
kubernetes?
So
what
he
notes
is
that
hey
Jenkins
on
kubernetes
has
no
content.
A
If
I
remember
correctly
right,
so
administering
Jenkins
on
kubernetes
is
empty
and
and
well
it
just
means
nobody's
written
that
that
page
right,
and
so
what
Anuj
is
proposing,
is
here's
the
high
level
overview
that
he
thinks
should
be
added
and
I.
Think,
let's
so
he
asked
three
days
ago:
hey
we've
got.
We
know
that
ervay
and
Stefan
and
Damien
are
the
kubernetes
experts
in
in
the
Jenkins
infra
team.
And
so
what
he's
suggesting
is
here
is
his
outline.
A
A
So
if
we
go
to
documentation-
and
this
was
administering
Jenkins-
so
it's
a
part
of
sysadmin
okay
system
administration
this.
So
this
is
what
he
was
envisioning,
oh
okay,
and
for
me
this
looking
at
it
this
way
is
a
lot
easier
than
looking
at
the
ASCII
doc,
so
introduction
and
overview
all
right.
We
don't
need
the
trailing
colon,
so
I
can
guide
him
on
that
architecture
and
components,
installation
and
configuration
scalability,
okay
and
there
isn't
a
high
availability
solution,
so
fault,
tolerance
that
that's
that's
a
possible
security
and
access
control.
A
B
Yeah
I
would
have
liked
to
help,
but
for
the
time
being,
I
can
help
with
you
know,
getting
more
content,
but
I'd
be
happy
to
test
it
whenever
something
is
ready.
B
A
Oh,
oh,
wait:
a
sec
okay,
so
this
is
a
mistake.
Okay,
there's
there
are
a
number
of
mistakes
here
that
I
can
correct
good.
We
don't
use
three
levels
of
indentation.
We
use
one
or
two
in
this
case
two,
not
one
so
that
and
we
needed
to
okay
so
separately,
not
not
as
part
of
doing
that
live
here.
There's
there's
more
to
it
than
that,
but
this
is
an
easy
one
for
us
to
be
involved
in
at
least
as
readers
I'm
not
skilled
enough
to
be
a
reviewer,
but
the
structure
looks
really
good.
B
A
A
A
One
of
them
has
merged
this
one
is
already
in
the
documentation
now
merged
and
and
visible,
and
this
one
is
a
best
practices
document
that
needs
more
content
and
and
I'm
really
I'm,
not
ready
to
merge
it
yet
because
there,
if,
if
I'm
going
to
be
so
bold
as
the
claim
that
we
should
have
such
a
thing
as
best
practices,
I
want
them
to
be
reviewed
by
people
who
agree.
Yes,
that
that
makes
sense
as
calling
it
a
best
best
practice.
A
B
No
I
know
that
these
tedious
work,
but
you
know
I,
would
just
review
the
second
one
whenever
I
have
time
and
thanks
for
Jeffrey
to
be
so
consistent
with
the
effort.
Great.
A
A
B
No
I
haven't
progressed
yet
I
was
waiting
for
the
next
version
of
update
till
I
was
supposed
to
correct
thumb,
Burger
the
head
with
the
Ruby
releases,
which
is
now
the
case,
so
I
should
spend
a
little
time
on
this
one
and
try
to
get
it
merged.
If
that
makes
sense
for
all
the
community
and
the
project.
A
B
I
say
issue,
but
it's
more
of
a
limitation,
because
Ruby
did
something
not
really
right
with
where
they
handled
the
releases
and
the
tags.
So
that's
why.
A
Hey,
thank
you
and
then
this
one
I'd
like
to
delay
again
until
Kevin
is
available
because
we've
got
we've
got
this
issue
that
gives
us
some
a
checklist
of
items
that
need
to
be
touched
and
I
think
we
may
want
to
touch
them
one
at
a
time,
probably
starting
with
installing
Linux
and
then
installing
Windows.
And
then
we
talk
about
the
others.
What
order
should
they
be
in
all
right
that
covered
and
I
will
be
out
of
the
office?
This
is
early
warning,
I'll
be
out
of
the
office
July
20th.