►
From YouTube: 2023 06 16 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
Welcome
it's
the
16th
of
June
2023.
This
is
documentation,
office
hours,
topics
for
today,
Google
summer
of
code,
errors
in
the
2.401.1
changelog,
pull
request
from
Jeffrey,
Chen,
blog
post
review
and
a
draft
PR,
and
we
may
want
a
discussion
or
whoops
a
discussion
and
review
of
Java
7
11
to
Java
17
changes
in
the
documentation,
Justice
that
that
might
be
a
good
group
exercise
for
us.
Any
other
topics
you
want
to
add
to
the
list:
nope.
A
B
Because
we
have,
we
finally
have
a
preview
site
and
I
just
shared
a
little
link
to
the
chat.
So
you
can
see
it's
saying
like
it's
a
Google
as
a
GitHub
Pages
website.
A
B
A
So
so
there
there
are.
This
one,
for
instance,
was
a
highlight
of
oh
there's
a
picture
missing,
but
this
is
looking
great
and
I
love
the
left
hand,
navigation
that
that
feels
really
okay,
now
down
here
in
the
bottom
left,
there
is
the
versioned,
the
version
navigation
experience.
Have
you
been?
Have
you
been
exploring
that
at
all
Chris
to
see
how
it
feels
yeah.
B
A
A
A
A
A
So
when
I
look
nope
nope,
not
that
sorry
when
I
look
at
this
one,
the
handbook
has,
for
instance
across
the
top
here,
the
page
to
page
and
section
to
section
navigation,
yeah
and-
and
this
gives
us
that
same
thing
here
with
if
I
remember
it
said
end
of
page
yeah
so
page
to
page
navigation.
Is
there
and
I've
got
a
tree
view
here
at
the
top.
B
A
A
C
A
A
B
A
C
A
C
A
B
C
B
A
B
Not
much
but
I
just
want
to
say
we
didn't
work
on
a
whole
night
together.
Oh
because,
like
there
were
some
issues
with
the
documentation
for
GitHub
Pages,
because,
like
four
hours
set
up,
we
need
to
do
something
extra.
A
A
A
A
B
A
B
A
B
Everything
because
I
think
I
think
last
time
we
saw
the
images
it
was
a
bit
skewed
due
to
the
compute
I
think
it's
always
a
monitoring
or
computers
by
aventisk
like
local
version.
So
it
was
like
it
looks
a
bit
different
from
the
from
what
we
see
in
reality.
Okay,.
A
A
B
He
got
one
example
working.
That's
the
last
time
I
heard
from
him.
A
Very
good,
all
right,
okay
and
git
lab
plugin
modernization
that
one's
been
on
pause
while
harsh
works
on
exams
right.
C
A
C
And
then
he's
got
a
few
of
them.
Is
there
really
nothing
about
move
copy
or
config.xml
in
these
Docs.
A
C
A
Oh
I
see
yeah
so
well
and
since
that
that's
a
cloud
Beast
thing
so
I'm
not
sure
we
could
certainly
ask
them
if
they'd
be
willing
to
share
it.
Let
us
let
us
put
it
in.
Let
me
see
if
we
can
find
something
with
Google
search,
Jenkins
job
move
or
copy
how
to
clone
a
job.
How
do
I
clone
okay,
so
stack
Overflow?
How
do
I
move
a
job?
A
Okay,
so
so
there's
something
we
could
embed
right,
we've
got.
Darren
is
more
than
happy
to.
Let
us
embed
his,
so
we've
got
how
to
clone
a
Jenkins
job
and
how
to
move
a
Jenkins
job
to
a
folder.
C
A
About
for,
given
that
I'm
going
to
copy
a
link
to
that
here,
let's
just
open
it
up
and
copy
a
link
to
the
video
okay
back
to
your
question
so
copy
slash,
move
video
copy,
Video
available
from
Dan
Pope.
C
This
is
for
line
55
of
administering
dice,
jenkins.adoc,
okay,.
A
A
Oh
yeah,
this
is
okay.
This
is
this
is
just
flat
wrong
right,
while
I
appreciate
that
somebody
in
the
days
of
of
XML
said
this
is
the
only
only
way
to
do
it.
Let's
fix
this
by
embedding
a
video
okay.
So
how
do
we
Yeah?
We
actually
yeah?
We
don't
we
don't.
We
I
think
we
don't.
Well,
let's
get
the
text
there.
We
definitely
don't
want
to
tell
people
to
use
file
system
operations
when
they
could
just
Okay,
so
this
I
think
needs
to
be
split.
A
A
A
A
I
find
jobs
simpler
and
easier,
and
so
I've
caved
in
and
said:
I
don't
want
to
fight
with
trying
to
use
the
word
project.
Yeah.
C
C
A
A
C
Okay,
because,
as
I,
you
know
my
knowledge
sort
of
got
frozen
at
a
certain
point
in
the
wars.
So,
and
you
know
there
were
religious
right.
A
A
A
A
A
And
I'm
fine
with
that,
because
I
think
that's
something
we
need
to
choose
and
I
think
we're
better
suited
than
than
Jeffrey
is
to
decide
that
let's
look
to
see
Okay,
so
we've
got
right
now:
we've
got
copy,
move
and
rename
a
job,
and
we've
got
a
description
of
the
directory
structure
of
the
Jenkins
homepage
or
the
Jenkins
home
folder.
Where,
where
do
you
think
it
makes
sense?
So
let's
go
look
at
the
candidates,
so
we've
got.
C
C
C
A
A
C
A
No
not
really
not
if
I,
remember,
I,
hear,
let's
look
and
see
because
because
rename
move
copy
and
rename
apply
to
jobs
and
there
actually
aren't
any
jobs
on
those
pages.
Okay,.
C
A
C
C
A
Sense,
well
so
so
certainly
there
are.
There
are
things,
for
instance,
if
I
attempt
to
do
let's
Show
an
example,
if
I
attempt
to
take
a
multi-branch
pipeline
job,
so
git,
client,
plugin
folder
has
a
thing
called.
The
GitHub
get
client
branches.
These
Branch,
these
jobs
are
actually
maintained
automatically.
A
C
A
C
A
A
A
C
A
Always
yeah
so
I
I
suspect.
Well,
if
we
okay,
if
we
look
at
tutorials,
we
certainly
have
some
tutorials
that
will
take
us
through
that,
but
I'm
not
sure
we
would
want
to
point
them
to
a
tutorial
for
a
general
description.
So
it
may
mean
that
we
need
a
description
of
creating
a
job
yeah,
because
that
seems
like
a
logical
thing
for
using
Jenkins
right
new
item,
or
maybe
it's
yeah
create
a
job,
creating
a
job.
A
A
C
A
A
Right
right
exactly
at
kmartins,
what
do
you
think.
A
A
C
C
C
C
A
A
C
Paragraph
two
is:
if
you
want
to
create
and
configure
a
pipeline
project
through
a
Jenkins
file
or
through
Blue
Ocean,
or
you
wish
to
find
out
more
about
these
core
Jenkins
that
a
lowercase
j
I,
don't
know
refer
to
the
relevant
topics
within
the
respective
Pipeline
and
blue
ocean
chapters.
A
So
there
there
is,
but
I
still
think
there
is
room
for
a
this
is
this
is
good
I
I
won't
dispute
I
like
that,
but
and
it
gets
them
into
this
into
those
sections,
but
I
think
basic
operations
on
jobs
on
projects
who
correctly
belongs
before
using
credentials.
A
A
But
I
think
I
think
we
owe
it
to
ourselves
to
put
it
in
order
and
I
agree
that
using
credentials
isn't
the
first
thing.
Aborting
a
build
is
actually
useful,
but
probably
needs
to
be
above
using
credentials
and
after
after
creating
one.
So
you
could
Envision
creating
a
job,
creating
a
project
launching
a
project
and
then
aborting
a
project
or
aborting
a
build,
launching
a
build
and
a
boarding
a
build
would
make
make
good
sense.
C
A
C
A
A
C
A
C
B
A
C
A
A
A
A
A
This
one
is
terrifying,
because
what
it
says
is
go
into
the
jobs
directory,
make
a
tar
file
and
then
reload
configuration
from
disk.
Well,
you
didn't
do
anything
that
to
actually
archive
it
or
to
so.
If
archival
means
remove,
this
did
no
remove
right.
If
archive
doesn't
mean
remove,
then
all
this
did
is
a
fractional
backup.
All
this
did
is
a
partial
backup.
A
A
From
disk
this,
this
doesn't
help
doesn't
help
anything
right.
You
don't
need
to
reload
anything
from
disk,
because
the
tar
didn't
delete
anything
right
and
the
problem
with
the
technique
they've
used
here
of
play,
leave
the
tar
file
in
the
jobs
directory.
That's
on
the
hope
that
the
administrator
will
remember
that's
where
their
archives
are
and
I
suspect.
There
are
plugins
that
will
do
archiving
better
than
this
or.
C
A
Exactly
you
want
I
think
I,
let's
not
describe
the
tar
process.