►
From YouTube: 2023 06 02 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
A
2.401.2
release
is
in
four
weeks.
Chris
is
the
release
lead.
A
A
A
All
right,
and
so
we've
got
the
we've
got
the
Docker
Quick
Start
yep
project
and
we've
got
the
alternative
build
process.
No,
let's
call
it
what
it
is:
versioned
documentation
for
the
Jenkins
handbook,
yep
user
handbook
Okay.
So
any
other
topics
you
want
to
add
Google
summer
of
code
and
ashitosh.
This
is
yours.
If
I
remember
correctly,
isn't
it.
C
A
Okay,
great,
and
are
you
comfortable
with
with
the
places
where
we're
currently
using
Docker
in
the
Jenkins
documentation
and
some
of
the
terrible
flaws
of
that
of
that.
A
Okay,
great
super
all
right.
Well
we're
happy
to
have
you
here
and
look
look
forward
to
your
contributions,
so
I
am
curious.
How's!
Your
experience
been
in
you
trying
to
use
Docker
compose
to
make
an
easier
way
to
set
up
Jenkins
and
and
its
agents.
What's
your
experience
been
so
far.
C
For
the
first
Docker
compose
file,
we
decided
to
go
with
a
simpler
file
for
battery
beginner
user
experience,
so
I'm
building
a
first
Docker
file
right
now.
That's
this
on
this
week's
bucket
list
and
I
am
getting
some
errors
and
they
are
getting
fixed,
so
I'm
working
towards
it.
First
file
Docker
compose
file,
will
be
completed
by
end
of
this
week.
I
think.
A
A
C
A
A
C
A
Okay,
well
so,
in
terms
of
documentation,
I
much
prefer
ed25519
keys,
because
there's
there's
so
much
shorter
text.
The
document,
the
the
open,
SSH
people
say:
they're,
also
more
secure,
okay,
okay,
so
so,
and
now
now
the
and
you're
doing
privilege.
True
for
the
same
reason,
I
assume
that
hey,
while
you
were
doing
development
work,
you
you
wanted
to
be
sure
that
permissions.
A
C
And
this
one
is
working
successfully,
that's
what
I
said
all
the
things
to
root
and
privileged
because
of
so
I
didn't
get
in
that
way.
Great
and.
A
A
Absolutely
and
and
experiments
it's
it's
perfect
that
you're
doing
it
this
way.
So
this
is
the
ed25519
private
key,
and
this
is
the
public
key,
and
here
is
your
oh.
This
must
be
your
RSA
private
key,
yes,
okay,
good
all
right!
Well,
so,
and
and
I
can
I.
I
am
no
fan
of
RSA
public
keys
because
of
that
scroll
bar.
So
thank
you
for
using
ed25519.
That's
a
good
choice.
C
A
Very
good,
and
now
this
one
is
using:
oh,
oh,
no
I
see
I'm
looking
at
the
wrong
file.
Now
this
is
your
your
current
one.
That's
that
you're
experimenting
with
we've,
seen
its
user
root,
privilege,
true
and
and
before
we
go
to
production.
I
assume
those
will
be
gone,
but
we
have
to
be
sure
we
understand
how
how
and
what
yes.
C
Bruno
also
created
a
pull
request.
Yes,
yesterday,
I
think
it
was
eight
hours
ago.
C
A
C
A
A
All
right
well
so
this
is
this
is
already
encouraging,
because
it
looks
like
what
one
of
the
problems
that
we
have
in
the
demonstrations
in
the
in
the
the
samples
that
we
create
is
we
end
up
running
things
on
the
Jenkins
controller
and
that's
a
bad,
that's
a
bad
pattern.
So
what
you've
done
here
is
already
reached
past
that
problem,
so
that
we
could
Now
set
the
Jenkins
controller
to
have
zero
executors
and
only
run
things
on
this
agent.
A
A
C
Experiments
are
turning
out.
Fine
I
was
wondering
how
the
process
of
setting
the
documentation
will
go.
That's
why
Bruno
recommended
to
attend
the
meeting,
and
the
plan
was
to
just
see
if
get
familiar
with
the
team,
with
the
first
meeting
and
discuss
about
documentation
later
when
the
docker
files
are
completed.
A
A
Install
process
here
is:
let's
see
how
many
steps
are
in
it
right.
It's
too
many
you've
got
to
you've
got
to
do
steps,
One,
open
up
a
terminal,
create
a
bridge
Network.
What
okay
and
then
you've
got
to
do
run
this
monster
terrible
thing
that
turns
on
that
does:
does
the
docker
in
Docker
and
then
you've
got
to
run
this
create
a
Docker
file
that
brings
in
the
latest
Jenkins
LTS
and
then
you've
got
to
build
it
and
then
you've
got
to
run
it.
A
B
A
So
my
dream
is
that
ashitosh's
work
will
replace
those
five
horrible
steps
with
one
command
Docker
compose
up
and
the
file
name.
I
know
that
that's
a
long
ways
off
for
you
and
I'm
okay
with
it
being
a
long
ways
off,
but
that
was
my
hope,
Chris
or
Meg.
Do
you
have
a
different
opinion
on
how
we
should
how
we
should
hope
for
this.
D
No
I
was
just
mute
and
then
I
couldn't
find
the
microphone
I'm
sitting
here.
Squirreling
like
a
fool
with
my
Mouse
and
then
is
it
going
to
be
a
similar
process
for
Windows.
C
A
A
I
think
so
and
I
think
if,
if
we
are,
if
we
are
as
if
we
are
as
lucky
as
I
hope,
we
will
be
the
Windows
and
Mac
OS.
The
windows,
Linux
and
Mac
OS
will
actually
become
a
single
thing
because
you
don't
really
have
to
be.
The
only
reason
for
the
the
differences
between
these
is
this
exotic
stuff,
with
Docker
and
Docker.
Right
and
I
am
hopeful
that
ashitosh
in
investigating
can
find
ways
to
to
do
that
in
a
way
that
works
with
with
containers
on
Windows
and
containers
on
Mac,
OS
and
Linux.
A
Now
the
Assumption
for
me
is
that
in
each
of
those
three
platforms,
the
container
is
actually
ultimately
running
an
a
Linux
variant
inside
the
container
and
that's
the
default
way
that
Docker
CE
runs
on
Windows
is
it
runs
with
Linux
containers
underneath
so
so
ashitosh?
Does
that
sound
okay
to
you,
or
were
you
assuming
that
you
would
have
to
do
something
somehow,
with
Windows
based
containers
on
Windows.
D
A
Right
well,
and
and
this
the
thing
we
need
here
is-
and
this
is
that's
the
thing
that
ashitosh
is
doing
for
us-
is
creating
a
multi-container
configuration
right.
So
here's
the
agent
container,
here's
the
controller
container
and
I
suspect
for
tutorials.
There
will
have
to
be
somewhere
in
here,
a
Docker
and
Docker
container,
or
something
that
gives
Docker
agents
to
the
controller
as
a
as
though
or
a
cloud
and
I
don't
know
which
of
those
it
is.
But
but
that's
that's
the
the
the
likely
destination
we
dream
of
first
step.
B
I
got
some
questions
about
the
docker
compose
file
prepared
by
ashes.
It's
like
I'm
wondering
if
it's
a
good
idea
to
put
like
like
under
Jenkins.
We
start
no
as
well
and
also
to
add
the
acid
M
size
to
it.
A
Oh
no,
why
would
you
set
it
to
no
that's
interesting
I
thought
that
it
was
typical
that
for
Docker
I
had
to
set
it
to
restart
some
other
setting.
Now
now
I've
got
to
go,
look
and
see
what
it
was,
but
I
I
remember
that
I've
got
a
setting
in
mind.
That
says
something
about
restart
I.
Just
don't
remember
what
the
restart
setting
is.
C
A
B
B
B
A
B
I,
don't
remember
because
I
I
did
I
did
search
for
a
while
back.
Let
me
see
sorry.
B
I
found
out
so
that's
that's
basically
just
I
think
it's
a
Max
size
of
the
depth,
slash
Dev,
slash.
B
Because,
like
we
run
into
some
problems,
if
it
forget
that
parking,
when
we're
doing
the
config
from
Mac
OS.
A
Okay,
so
so
this
so
okay,
so
I'm,
not
sure
I,
I
guess
I
need
to
read
the
instructions.
What
shm
size
is
so
belena
talks
about
it
as.
A
Interesting,
okay,
so
needs
more
research.
Ashitash
you've
got
the
a
good
question,
any
other
questions.
Chris.
A
A
Right
so,
let's
see
the
questions
we
had
were:
oh
I
should
embed
the
embed
the
link
to
ashatosha's
example,
because
that
way
I
could
play
with
it
later.
A
Okay,
and
then
it
was
questions
from
Chris
and
ashutosha.
The
recording
of
this
session
will
be
available
on
community.jenkins.io,
roughly
24
hours
after
we've
done
the
meeting,
so
you'll
be
able
to
refer
back
to
it,
so
it
was.
Should
we
set
shm
underscore
size
needed
it
for
git
lab
plugin
right,
yep
modernization.
So
if
you
get
lab
plugin
project.
A
B
A
A
A
B
Maybe
we,
the
thing
is
I
think
we
should
like
start
talking
with
info
or
Gavin
about
setting
up,
but
how
to
how
to
go
forward
with
hosting
a
first
draft
after
work
to
a
dark
star.
Jack
has
iOS.
A
A
B
I
think
we
are
about
to
have
like
something
to
to
show
for
in
maybe
next
week,
but
so
I'll
report
back
next
week.
Oh
good
yeah
because
like
we're
working
on
like
moving
to
images
manually
because
it
cannot
be
automated
according
to
venting.
B
B
I
think
because
yeah
and
and
I
think
it's
for
and
toy
that,
like
the
way
that
the
images
are
stored,
maybe
a
little
bit
different
because
like
right
now,
it's
it's
more
centralized,
but
maybe
in
the
future
it's
a
little
it's
depending
on
module,
I'm,
not
sure.
Okay,.
A
D
A
So
here
is
the
change
log,
and
here
is
the
upgrade
guide.
Oh
and-
and
there
are
two
mistakes
that
we
detected.
I
should
note
that
that's
good
Mark
made
two
mistakes
in
assembling
the
changelog
that
we
detected.
While
we
were
doing
the
presentation
of
the
what's
new
in
in
2.401.1.
A
It'll
probably
be
me
creating
it,
but
Kevin
may
be
back
in
time
to
do
do
a
revision
of
it.
So
Kevin
returns
returns,
June
12.
he
may
be
able
to
oops.
Let's
put
that
in
the
correct
location.
A
Whoops
Kevin
returns,
June
12th
may
be
able
to
do
the
changelog.
B
D
A
Next,
one
is
a
victory.
This
pull
request
from
Jeffrey
Chen
came
in
two
weeks
ago
or
so,
and
what
Jeffrey
did
was
he
brought
back
a
stalled
pull
request
that
was
originally
proposing
to
take
content
from
the
internationalization
instructions
on
the
Wiki
page,
and
this
is
something
that
was
done
all
the
way
back
in
2019
it
was
started.
We
did
long
series
of
conversations
about
it.
Meg
many
others
have
been
involved
and
we
then
said
hey.
This
is
stalled,
we're
going
to
move
it
to
stalled,
so
it's
not
distracting
us.
A
A
So
here
we've
got
first
pieces
that
International,
localization,
internationalization
and
localization
is
no
longer
work
in
progress.
This
is
good
enough.
It's
production
all
right,
developer
tasks,
translator
tasks,
both
relatively
short
lists
and
entry
for
Chinese,
localization,
still
and
pointer
to
how
to
configure
IntelliJ
to
make
your
job
easier.
Doing
localization
with
links
inside
the
page
to
more
details,
then
right
next
to
it
on
the
page
is
the
crowding
integration
that
Alex
Brandis
has
helped
configure
and
makes
it
much
much
easier
to
translate
plug-in
text
from
one
language
to
another.
A
So,
thanks
to
Jeffrey
now
Jeffrey
has
continued
and
has
made
the
next
step,
which
is
another
pull
request,
and
the
next
pull
request
will
probably
need
the
same
kind
of
work
on
it.
It's
this
conversion
of
administering
Jenkins
and
Jenkins
best
practices,
and
the
challenge
here
is
that
many
of
these
things
are
already
covered
elsewhere
and
we
have
to
find
the
correct
locations
in
the
documentation
to
put
them
and
I'm,
not
sure
that
Jeffrey's
able
to
to
do
that.
A
A
No
need
to
feel
like
it's
obliga
obligated
that
you're
obligated
to
do
it,
but
if
you've
got
capacity
to
do
it,
this
would
be
a
great
one.
Bruno
has
gone
through
and
made
linguistic
changes
and
style
changes
to
to
bring
things
up
to
our
common
way
of
doing
things
and
Jeffrey
has
already
applied
those
changes.
So
what
you're
seeing
should
be
already
first
level.
First
draft
good
enough
to
review
okay.
A
D
D
A
Right
well,
it's
what
what
I
was
thinking
is:
let's
find
the
right
place
to
put
this
kind
of
content
if
it
doesn't
already
exist
and
if,
if
it
you
feel
like
it
belongs
in
managing
or
administering
I'm
fine
with
that
admitting
that
we
know
that
the
dis,
the
distinction
between
those
two
is
flawed
and
imperfect.
Right.
A
A
A
A
A
D
D
C
A
Where
what
we've
got
is,
for
instance,
there
are
some
containers
that
we've
got
some
containers
that
are
done
with
Arch
Linux.
It's
a
low
volume
distribution.
A
We
don't
have
anyone
in
the
maintaining
team,
that's
interested
in
it,
so
it's
not
being
maintained
and
therefore
it's.
It
doesn't
make
any
sense
for
us
to
retain
it,
but
we
need
to
in
some
way
find
a
way
to
announce
to
the
users:
hey
you're,
using
a
container
that
we're
going
to
stop
updating
or
we've
stopped
updating.
A
The
other
kind
is
this:
one
is
already
covered:
Centos
7
controllers,
a
controller
container
or
yeah.
Can
these
are
containers
so
controllers?
And
this
one
is
already
showing
the
end
of
life
warning,
because
it's
using
Centos,
7.,
okay,
but
we've
got
others,
for
instance,
Alma
Linux
8.
A
B
D
D
May
be
a
dumb
question:
it's
off
the
top
of
my
head.
Is
there
going
to
be
any
attempt
to
record
this?
Historically?
No
because
we
do
end
of
life
anyhow.
This
is
just
we're
warning
them
right,
like
some
people,
someone
a
year
from
now,
comes
in
and
wants
to
know
what
happened.
You
know
what
the
path
was
out
of
Cento
S7
or
something
like
that.
A
A
Actually,
good
good
question
so
as
you're
thinking
about
so
we're
we're
pointing
people
to
this
blog
post
for
right
now,
so
that
they
have
a
reference
to
the
dates
and
the
and
the
plan
I've
wondered.
Should
we
have
an
end
of
life
table
in
the
Jenkins
documentation
somewhere
eventually,
but
I
wasn't
sure
that
that
would
be
as
helpful
as
as
the
version
documentation
which
will
give
us
a
place
that
we
can
describe
which
platforms
we
tested
with
a
specific
version
anyway,
right.
A
D
Lag
a
little
bit
and
every
once
in
a
while
somebody
comes
out
of
the
woodwork
who
is
just
you
know,
15
versions
behind
or
something
I
don't
know,
because
the
table
would
also
be
kind
I
don't
know.
Would
it
be
a
pain
to
maintain
or
maybe
not
because
once
it's
dead,
it's
dead?
In
that
stage
you
just
become
keep
adding
stuff
right.
A
At
Jenkins
release
right
so
in
the
version
of
documentation,
should
we
We
note
the
operating
systems.
A
So
in
the
packaging
repository
today,
tests
container
it
can
test
installs
of
all
sorts
of
operating
systems.
Fedora
37,
let's
see
red
hat
eight
Red
Hat,
nine
Debian
10.
A
A
D
A
Good
interesting,
okay,
good
interesting
concept,
mag
I'm
not
entirely
sure
how
to
do
it,
but
we've
got
something
like
it
already
in
well.
Let
me
show
this
page
because
I
was
just
checking
it
today
in
the
Jenkins
documentation
we
have
a
page
called
choosing
the
version,
a
Jenkins
version
to
build
against.
So
this
is
guidance
to
a
developer
of
what
value
they
should
set
for
their
jenkins.version
in
their
Palm
file.
Right.
D
A
It
tells
them
2.375.4
or
2.387.3
now,
five
days
ago,
those
numbers
were
2.361.4
and
2.375.4.
This
documentation
knows
when
we
release
a
new
LTS
and
puts
the
latest
LTS
there,
one
back
there
and
two
back
there
right.
So
something
like
that,
we
could
probably
extract
the
con
the
the
tested
operating
systems
from
the
packaging
repository
as
well.
B
D
D
A
A
A
Okay,
the
main
newsletter
I've
got
to
do
some
writing
for
it,
and
onward
would
go.
B
Okay,
I've
got
a
question
for
Azure
talk.
Show
it's
like.
Have
you
guys
like
forward
a
project,
so
talk
a
quick
start?
Have
you
guys
planned
how
to
draft
a
documentation
needed
for
the
darker
compost?
Examples.
B
A
A
B
You're
saying
it
could
be,
it
could
be,
and
unless
it's
like
I'm
just
wondering
if
they
have
a
process
like
so
so,
I
actually
thought
she
couldn't
stop.
But
drafting.
C
Now
we
right
now,
we
haven't
had
discussed
anything
like
this.
Okay.
A
B
I
don't
mean
to
document
in
the
compose
file.
It's
just
too
documentary
because,
like
we're
not
just
using
the
docker
Converse
model
for
the
example,
so
there's
like
there's
some
background
information
behind
it
too,
and
those
like
actually
may
want
to
collect
as
he
goes
along
and
he
don't.
He
may
not
want
to
wait
until
the
last
minute
to
do
it,
because
then
you
may
have
forgotten
like
most
of
the
details.
That's
what
I'm
asking
now.
A
B
A
C
A
So
the
idea
is
some
form
of
of
running
notes
or
lab
notes
or
don't
forget
this
or
I.
Did
this
because.
A
D
A
Yeah:
okay,
thanks
everybody
recording
will
be
available,
probably
within
24
hours.