►
From YouTube: 2023 06 23 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
Foreign
welcome.
This
is
Jenkins
documentation,
office
hours,
it's
the
23rd
of
June
2023,
Asia
time,
topics
on
my
list:
Google
summary
of
code,
open
poll,
requests
of
interest
and
a
possible
discussion
and
review
of
java
11
to
Java
17
changes
in
the
documentation
that
one
I
call
a
possible
because
I'm
a
little
weary
tonight.
So
we're
going
to
limit
ourselves
to
probably
not
more
than
about
20
20
minutes.
Any
other
topics
you'd
like
to
be
sure
we
put
on
the
agenda.
C
Thanks
things
are
going
a
little
slow
this
week,
but
we
have
created
a
working
example
with
jobs
too.
It
already
has
one
job
you
can.
Let
me
share
a
link.
C
A
A
C
There
is
a
region
script
before
right
there.
You
can
run
it
to
generate
your
own
keys
so
that
for
connecting
and
Jenkins
agent
with
controller
it
generates
new
SSH
Keys
every
time
to
be
secure.
A
A
A
A
Well,
that's
an
interesting
choice
of
upgrade
State.
That's
fun!.
C
Yeah,
that's
we
do
plan
to
remove
afterwards,
it's
because
of
faster
to
make
things
fast
go
faster
right
now:
okay,.
A
A
Collision
yeah
and
that's
no
shock
I
knew
I
had
a
I
knew
I
had
a
colliding
service
on
it.
So
that's
not
a
problem.
I
just
wanted
to
see
if
my
my
tests,
okay,
my
tests
have
passed
far
enough
that
the
bug
I
was
trying
to
duplicate,
can't
be
duplicated
good,
so
I
will
just
go
interrupt
that
okay.
Now,
let's
do
that
compose
up
again.
C
A
C
A
Excellent
okay
I
know
I
have
to
I
have
to
do
some
of
my
usual
experiments.
So
let's
see
what
kind
of
agent
we've
actually
got
there
and
then
updates.
Let's
update
all
the
plugins
to
latest
releases
and
see
if
the
updates
persist
across
a
restart
okay.
So
it's
restarting
I'd
click
the
restart
and
will
it
keep
running.
A
A
C
A
A
Okay,
well
now,
I
am
running
somewhere
other
than
localhost
right.
So
I
connected
my
web
browser
to
a
fully
qualified
domain
name.
Maybe
you
connect
your
web
browser
to
localhost?
Yes,
yes,
okay
and,
and
that
would
do
it,
then,
because
what
Jenkins
does
is
it
uses
the
address
in
the
web
browser
somehow
to
to
populate
that
field?
Nice,
okay,.
C
We'll
we
do
plan
to
use
that
update
wizard
on
when
we
upload
it
in
mainly
so
it
will.
John
Mark
mentioned
that
it
will
solve
that
problem
where.
A
A
C
A
Okay
and
and
okay
and
I,
see
it
here's
the
indicator
all
right,
so
this
agent
that
you've
got
configured
there
is
running
Debian,
Debian,
Debian
operating
system
inside
the
or
the
Debian
utilities
inside
that
inside
that
agent
and
if
I,
look
at
the
the
root
contain
at
the
root
machine,
see
how
do
I
change
it.
Let's
give
it.
Oh,
it's
got
the
same
labels
good.
It's
also
running
Debian.
As
expected,
very
nice.
C
A
C
They
didn't
have
a
job.
You
can
run
a
job
example
job
to
test
if
it's
using.
A
Right
so
if
I
create
hello
as
a
pipeline,
job
and
I
go
click
and
say:
let's
do
this
hello
world
boom
build
now
and
if
you
got
declarative
pipeline
installed
that
should
work.
You
did
very
good.
A
C
So
after
this
we
are
working
on
the
tutorials
that
uses
Docker
the
previous
Docker
commands.
There
are
four
I
think
we
have
open
issues
regarding
them
and
and
right
now
the
mid
midday
evaluation
is
coming
so
on
6
July,
so
this
week,
I
think
I'll
be
working
towards.
A
A
C
A
C
That
sort,
but
we
haven't
decided
yet
fully
but
I
was
thinking.
C
A
C
A
C
If
you,
but
if
you
do
want
to
Delete
the
volume
two
you'll
have
to
use
Docker
compose
down,
slash
less
volume.
A
C
A
A
C
A
Well,
and
that
that
sounds
great
to
me,
I
was
just
curious.
So
if
I'm
not
sure
how
users,
if
users
tend
to
do
one
tutorial
and
then
stop
or
if
they
do,
two
two
or
more
tutorials
and
I,
was
worried.
If
they,
if
we
have
a
single
volume,
is
there
a
risk
that
the
two
tutorials
might
collide
with
each
other
by
using
the
same
volume.
A
A
A
And
so
then
you
said
that
the
next
step
next
Target
is
the
next
sort
of
big
Target
is
using
Docker
inside
somehow.
A
C
A
Exactly
see
that
was
that
was
one
of
the
things
that
I
look
forward
to
you
exploring
to
to
see
what
what
alternatives
are
there
for
easy
execution
of
Docker
operations
in
an
environment
that's
already
running
in
Docker,
and
that
that's
that's
the
place
where
I
well,
this
horror
right
here,
I'm
delighted
it
works,
but
it
is
scary
what
it's
doing
right,
I
mean
it's.
It's
doing.
It's
doing
things
that
this
Docker
and
Docker
stuff
is
doing
things
that
are
have
security
risks.
C
A
C
So
the
next
this
weekend
next
week,
I'll
probably
be
working
to
on
the
midterm
presentation
too.
A
B
A
Yeah,
okay,
I
should
I
should
already
seen
it.
It
does
yeah.
So
so
we
need
the
same.
The
same
technique
here
as
we
need
in
the
tutorials,
because
it's
this
is
also
doing
Docker
and
Docker,
and
it
was
doing
it
specifically
because
we
wanted
people
to
be
able
to
use
the
same
pattern
to
do
this,
as
they
did
tutorials
good,
okay,
great
nice.
B
A
Needed
for
needed
by
four
tutorials
and
the
docker
install
instructions,
good,
very,
very
good
anything
else.
Ashutosh,
no
I!
Think
it's
okay!
How
about
we
take
the
next
topic?
Then
I
made
myself
a
promise
that
I'd
get
done
by
in
about
20
minutes,
we're
a
little
over
Meg
if
you're,
okay,
I'd
like
to
take
the
just
this
one
topic
on
the
open,
pull
requests
of
Interest
we've
got
you
remember.
Jeffrey
Chen
had
submitted
a
pull
request
that
you
would
evaluate.
You
had
reviewed
right
and
some
old
Wiki
stuff
right
exactly.
A
It
was
a
migration
of
two
things:
the
administration,
some
administrating
material
and
a
best
practices
page
and
so
I
started
working
on
it
last
weekend
and
while
working
on
it
found
that
hey
I
couldn't
make
changes
to
it,
so
I
ultimately
ended
up
taking
Jeffrey's
work
but
I
closed.
The
pull
request
so
kept
all
of
his
commits
but
closed
the
pull
request
and
then
split
it
into
two
pull
requests
uh-huh.
A
So
because
the
original
thing
was
targeting
both
administering
Jenkins
and
best
practices.
The
split
into
two
was
one
half
for
administering
Jenkins
and
one
half
for
best
practices
and
the
the
administering
Jenkins
piece
I
felt
like
was
well
enough,
reviewed
after
your
reviews
and
Kevin's
reviews
that
earlier
today,
during
doc's
office
hours,
Europe
I
merged
it
all
right,
and
so
what
we'll
see
is
that
Jeffrey's
work
here
and
the
things
that
I
had
added
to
It
ultimately
did
end
up
in
the
book
right
here.
A
B
A
B
A
A
Well,
but
using
a
telematic
approach,
I
think
is
the
right
approach.
It's
hey.
Let's
talk
about
the
compromises,
because
the
word
best
in
this
case
Miss
might
be
misperceived
as
the
one
true
way,
and
that's
not
what
it's
describing
right.
It's
describing
for
a
particular
set
of
circumstances
here
are
a
set
of
good
practices
that
have
worked
for
some
people
and.
B
A
Yeah,
exactly
and
and
a
software
testing
community
that
I'm
in
loves
to
to
to
berate
the
use
of
the
word
best
in
that
case,
because
it's
a
it's
what
a
superlative,
it's
it's
a
maximum
thing
and
the
usual
answer
is
nonsense.
They're
not
maximal
right,
but
the
cool
thing
about
this
one
is
that
Darren
has
four
or
five
videos
that
are
now
embedded
in
this,
and
so
let's
go
look
at
it
briefly
to
see
how
it
looks
in
the
in
the
in
the
Prototype,
because
I
think
it's
the
right
approach
now.
A
One
of
the
problems
with
this
approach
is
its
well,
it's
imperfect
like
anything,
but
here
if
we
look
at
using
Jenkins
best
practices,
what
you'll
see
is
a
series
of
videos
that
are
almost
back
to
back
with
each
other
GitHub
organization,
folder,
gitlab
group,
uh-huh,
bit
bucket
team
or
project
or
giddy
organization.
Folder
now
I
could
separate
each
of
them
with
a
heading
or
with
some
text,
but
they
are
most
most
of
our
users
will
have
exactly
one
of
these
and
no
more
right
and
so
having
them
choose
now
now.
B
The
other
thing
that
I
haven't
seen
these
videos,
but
is
there
like
do
these?
Do
you
have
two
or
three
points
that
are
like
your
summary
takeaways,
because
the
problem,
one
of
the
things
that
bugs
me
with
the
embedded
videos,
is
it's
a
20
minute
video
and
I've
watched
it
and
I
liked
it,
and
there
were
a
couple
of
things
it's
like
what
exactly
did
they
say
and.
A
A
B
Sit
here
trying
to
jump
around
it's
like
where
was
that
gem?
If
there
are
a
couple
of
gems
that
could
be
out
there
or
the
other
thing
is
summary
commands
that
I
could
copy
and
paste
it's
very
hard
to
copy
and
paste
out
of
a
video
good.
A
B
A
B
It's
a
good
world.
I,
you
go
a
whole
Pine
all
you
want
right.
A
So
what
I
started
with
was
hey
First
Choice.
You
should
use
organization
folders,
they
are
the
most
efficient
way
to
do
it.
It
means
you,
you
create
one
job
and
it
will
create
multi-branch
folders
for
every
repository
and
jobs
for
every
branch
and
massive
automation,
but
there
may
be
cases
where
multi-brand
where
organization
folders
aren't
quite
what
you
need.
Okay,
you
could
then
step
down
one
level
and
do
multi-branch
Pipelines,
and
it's
hey.
If
something
prevents
you
from
using
organization
folders,
then
at
least
use
multi-branch
pipelines,
and
this
is
where
the
needs
more
wisdom.
B
Why
is
multibatch
pipelines
not
a
link
to
the
chap
the
page
about
multi-branch
Pipelines
organization?
Folders
was.
B
B
A
Oh,
oh
I
see
what
you're
saying:
okay
good
all
right,
that's
a
that's
a
good
good
suggestion.
I
should
probably
follow
the
same
pattern.
Let's
see.
Well,
let
me
think
about
that.
Okay,
because
the
what
I
did
was
since
this
closing
sentence
had
the
hyperlink
in
it
here.
I
put
the
closing
sentence
with
the
hyperlink
here
as
well,
but
what.
A
B
A
A
B
A
And
and
now
now
this
is
one
where,
where
it's,
it
might
be
worthwhile
to
consider.
So
this
page,
for
instance,
this
is
actually
a
page
that
Kevin
Martin's
detected
was
not
in
the
in
the
list
on
the
left.
It
was
not
in
the
index
on
the
left,
oh
so
he
moved
it.
He
put
it
there
correctly
very
nice,
but
it
it's
rather
older
descriptions
of
some
things,
and
so,
for
instance,
it
mentions
GitHub
organization
or
a
bit
bucket
team
when
in
fact,
right
now
we
have
five
or
six
organization.