►
From YouTube: 2022 09 01 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
Release-
and
I
think
we
can
go
along
with
that-
we
have
some
recently
added
blog
posts
about
devops
world
2022
in
the
jenkins
blog,
which
I
want
to
point
out
and
then
a
couple
of
other
topics
from
previous
sessions.
The
search
improvements
on
jenkins.io
and
commercial
support.
Page
that's
been
proposed
by
gavin,
so
just
to
start
us
off
mark.
Would
you
like
to
go?
Give
us
an
update
on
the
action
items.
B
A
Okay,
thank
you
so
much
next
up
jihan.
Would
you
like
to
share?
What's
been
going
on
with
google
summer
of
code
mark
mentioned,
you
were
talking
about
the
docs
generator
and
was
able
to
add
that
so
yeah
just
wanted
to
see
what
you
had
to
share.
C
Yes,
so
I
was
able
to
get
the
request
for
the
pipeline.
Such
documentation
generator
done
and
we
merged
it
a
couple
days
back,
but
it
was
breaking
the
site.
It
will
add
some
errors
and
I
basically
I
fixed
that
by
writing
the
code
to
generate
the
parameters
folder
and
yeah.
C
Even
that
was
much
like
a
half
an
hour
back
and
mark
also
created
a
full
request
to
test
it
on
genki
zotero,
which
I
think
has
failed
again
because
of
that
particular
reason
so
not
able
to
debug
what
the
error
is,
but
it's
not
able
to
find
that
particular
parameter
file
that
is
created
so
we'll
have
to
debug
it
more.
But
I
can
show
you
the
result
on
my
local
machine
like
what
it
looks
like,
and
maybe
we
can
look
into
it
together.
If
that's
fine
sure.
C
Is
it
visible
yep,
so
I'll
just
run
it
locally?
First
and.
D
C
Error,
I
think
this
is
the
build
error
that
is
facing
and
is
saying
or
such
filer
directory.
C
So
I'm
not
sure
whether
this
is
happening
because
we've
created
a
new
new
folder
inside
the
file
structure
of
genquezo
dial.
But
you
can
maybe
test
it
something
else
yep,
so
the
local
site
is
running
and
if
we
go
ahead
and
look
into
multi
branch.
C
Basically,
the
loading
time
for
this,
this
page
required
around
20
seconds
before
it
becomes
stable
for
the
javascript
going
on
and
the
price
browser
will
crash
open.
But
it
requires
only
a
couple
of
seconds
now
to
get
there
and,
for
example,
with
the
configuration
I've
added.
Many
of
these
have
been
abstracted
to
the
new
pages.
C
C
C
This
is
working
fine
on
my
local
machine,
not
sure
what
is
going
wrong
with
the
with
the
side
generation,
but
any
any
thoughts
on
this
one.
B
C
B
C
So
when
we
unzip
it,
it
will
have
a
folder
which
is
known
as
params
in
it
and
after
that.
So
basically
that
particular
folder
will
consist
of
this
file
over
here.
B
B
C
Basically
earlier
when
we
fetch
external
resource,
as
far
as
I
can
recall,
it's,
it
calls
the
okay,
so
it
unzips
it
in
the
steps
directory
itself
and
when
we
do
that,
the
params
folder
comes
within
it
and
if
it's
not
able
to
find
it,
then
I'm
wondering
how
it
is
able
to
name
this
file
correctly
in
the
first
place
so
from
where
is
this
name
coming?
C
If
it's
not
able
to
find
it
in
the
first
place,
because
I
have
not
linked
it,
it's
not
that
the
link
is
coming
out
to
be
like
this,
and
basically
this
is
happening
at
compile
time,
so
it
won't
even
know
if
it
exists
or
not.
If
that
particular
link
exists
or
not
that's
being
linked.
If
that
makes
sense,
I
guess
so,
I'm
not
sure
how
it
knows,
but
if
this,
like
the
name
of
this
particular
ascii
doc
in
the
first
place,
if
it's
not
able
to
locate
it.
C
I'm
not
sure
what
script
is
used
to
unzip.
I
use
the
standard
linux
kinds
of
commands
on
my
machine,
which
basically
gets
the
folder
out
as
well
and
like
I
can
demonstrate
them
by
moving
to.
C
C
B
E
C
The
the
main,
the
folder
that
we
want
is
the
first
hand
itself,
not
sure
what
the
second
third
and
the
fourth
line
are
doing,
what
what
they
are
touching.
Basically.
B
B
It
looks
like
the
the
four
arguments:
are
the
origin,
the
destination,
the
front
matter
and
the
zip
destination
so
origin
that
url
destination,
so
it
copies
it
into
content,
underscore
temp
front
matter,
none
required
and
then
dip,
zip
destination
content,
doc
pipeline
steps.
That
seems
all
quite
reasonable.
C
Do
you
think
that
it
is
appending
the
name
params
over
here?
So
not
sure
this
happened
to
me
once
as
well,
but
basically
giving
so
it's
not
able
to
find
the
end
point
of
this,
maybe
putting
it
like
this.
I
don't
think
it
should
make
a
difference,
though,.
C
B
B
D
I
had
a
look,
a
search
within
github.com
on
this
repo
to
see
if
it
was
called
elsewhere,
but
unfortunately
there
is
just
one
occurrence
in
the
make
file
and
another
one
in
the
dockerfile.
But
that's
all
because
I
was
wondering
if
you
have
the
hero
evie
han.
Maybe
somebody
else
should
have
it
for
other
resources,
but
that's
the
only
place
where
it
is
called
so
false,
positive,
perfect.
B
B
B
B
C
So
what
command
does
it
use
to
unzip
ruby?
The
one
you
mentioned
right
now.
B
That
ask
your
question
again:
vihan,
yes,
ruby,
zip
is
the
thing
that's
performing
the
unzip.
I
assume
it
would
honor
directories.
I
would
be
surprised
if
it
did
not.
Now
is
there
a
way
we
could
check
that?
Actually
there
is,
I
can
probably
go.
B
B
B
C
B
B
C
Even
if
you
use
this
method
and
if
we
don't
do
not
comment
that
out,
we
will
get
the
older
ones,
but
I
think
now,
if
we,
since
the
latest
in
the
repository,
is
updated
now
so
season
points
towards
the
new
documentation.
We
can
try
out
the
fashion
resources,
script
itself.
B
Right
we
could
could
we
could
update
fetch
external
resources
to
pull
from
the
from
the
pull
request
or
from
the
yes
well,
and
it's
in
fact,
it's
already
doing
that,
isn't
it.
C
C
Yes,
basically,
the
external
resources
itself
is
not
working,
so
when
the
ruby
is
fetching
that
and
unzipping
it
locally,
that
is
where
the
problem
is
arriving,
so
we
need
to.
We
need
to
under
investigate
the
uv
part.
B
C
Sure
so
I
can
do
that
and
I
believe
those
changes
would
be
needed
in
jenkins
at
I
o
and
not
bypass
absorp
generator.
So
whenever
we
make
those
changes
first
and
generation
zero,
then
we
can
re-uh
recreate
that
code
request
from
psdg.
B
A
A
Great,
is
it
all
right
that
if
we
move
on
in
the
agenda.
A
Okay,
so
next
thing
that
is
on
our
agenda
today
is
the
jenkins
september
lts,
which
will
be
2.361.1,
along
with
the
release.
A
Faith
has
asked
for
a
blog
post
about
jenkins
for
the
continuous
delivery
foundation
blog
I'm
working
on
that
currently
and
have
been
able
to
get
a
lot
of
feedback
and
suggestions
from
the
jenkins
team
developers
community
at
large.
So
I've
been
able
to
revamp
and
add
a
lot
more
information
there
and
I'll
be
sharing
it
as
a
pull
request.
Once
I've
actually
submitted
the
pull
request,
I
have
to
double
check
on
what
kind
of
formatting
and
file
type
they
use,
since
it
does
seem
to
be
different
from
the
regular
jenkins,
ascii
docs.
A
That
is
also
going
to
include
some
information
that
I've
been
able
to
source
from
basil's
previous
blog
post
about
requiring
java
11
and
with
the
amount
of
content
that's
going
to
be
in
the
changelog
and
upgrade
guide.
There
should
be
more
than
enough
information
to
go
over
and
check
out
with
the
new
lts.
A
A
A
One
other
thing
I
wanted
to
point
out
on
jenkins.io
is
the
fact
that,
with
devops
world
2022
approaching
so
soon,
we
have
some
contributors
in
other
posts
on
the
jenkins
community,
blog
talking
about
their
various
topics
and
ideas
that
they're
going
to
be
bringing
up
at
devops
world.
It's
really
exciting.
This
is
back
to
in
person
for
devops
world,
which
is
a
nice
return
and
with
everything
that
I'm
aware
of
that's
going
to
be
happening.
A
The
search
improvements
for
jenkins.io
is
essentially
the
search
results.
Right
now
are
not
as
good
as
they
could
be.
Some
keywords
don't
show
the
results
you
would
expect,
but
this
is
in
part
due
to
the
fact
that
the
algolia
search
is
older.
Right
now
we're
using
the
legacy
scraper,
it
needs
to
be
updated
to
be
more
modern,
and
this
will
take
some
time
to
develop
and
figure
out
configure.
A
It
looks
to
be
something
that's
specific
to
the
credentials
that
right
now,
mark
and
gavin
mogan
are
the
two
that
have
those
credentials,
so
thankfully
mark's
already
created
a
github
issue
for
tracking,
but
this
will
take
some
time
to
get
going
and
get
this
straightened
out.
A
The
last
topic
that
I
have
on
the
agenda
is
the
commercial
support
page
proposal,
which
was
shared
by
gavin
in
july.
It's
been
a
little
bit
since
there's
been
any
updates
or
discussion
on
it,
so
I
just
want
to
make
sure
that
that's
still
visible.
This
is
something
that
would
greatly
benefit
not
only
jenkins
as
a
whole,
but
the
user
base
and
the
community
at
large.
A
The
idea
of
having
an
updated
support
page
would
lend
itself
to
getting
that
direct
communication,
be
getting
that
easier
support
and
even
expanding
the
options
of
what
support
means
stuff
like
training,
certifications,
other
commercial
opportunities
are
all
possible
and
we
want
to
make
sure
that
this
has
the
best
set
of
information
and
support
that
we
can
provide
for
anyone
that
might
be
looking
to
use
it.
So
if
you
have
any
ideas
or
want
to
get
in
on
the
discussion,
that
link
is
in
the
agenda
and
available
on
the
community.jenkins.io
site.
C
Yes,
so
basically
one
thing
that
I
could
think
to
rectify
the
error
was
in
case.
We
are
not
able
to
see
why
the
unzip
thing
is
not
working.
What
we
can
do
is,
instead
of
keeping
that
params
folder
within
all
ascii..
C
We
create
another
zip
for
it,
maybe
it's
known
as
params.,
and
then
we
unzip
it,
and
since
that
is
a
folder,
it
won't
have
any
issues
that
we
are
facing
now
and
yeah.
It
should
work
so
that
should
be
like
that
should
be
the
green
path,
maybe
and
figuring
out
why
the
folder
is
not
getting
extracted,
is
the
priority
now
so
I'll.
Maybe
work
on
that.
A
Okay,
thank
you
very
much
jihan
and
I
just
wanted
to
say
thank
you
for
all
of
the
continued
work
you're
doing
on
the
documentation
as
a
doc's
person
myself.
I
I
really
appreciate
the
fact
of
trying
to
simplify-
and
you
know
condense
the
bloat
on
these
pages
a
lot.
So
I
love
it.
Keep
it
up.
This
is
amazing,
so
thank
you
so
much
for
the
continued
innovation
and
contributing.
A
Okay,
and
with
that
mark,
I
think
we
can
stop
the
recording.
It
will
be
available
in
24
to
48
hours.
E
Yeah,
so
I
was
just
listening
on
this
pipeline
generation
and
I
guess
this
problem
with
the
subfolder.
It's
really
just
that
we
need
to
create
the
subfolders
recursively.
So
there's
like
one
line
of
ruby
code
missing
because
we're
trying
to
write
into
a
subdirectory
that
wasn't
created
yet
so
that
should
be
a
fairly
easy
fix
for
for
the
drink
inside
so
bihar.
If
you
want
to
submit
it,
I've
posted
it
in
the
chat,
but
the
change
that
needs
to
be
done,
but
yeah.
D
B
E
B
All
right,
yes,
so
benedict,
I
think
I'm
understanding
I
hadn't
looked
at
the
code.
It
says
if
downloading
a
zip
file
extract
it
unzipping
to
and
it
does
a
maker
of
the
zip
destination,
but
then
iterates
exactly,
as
you
said,
over
each
file.
E
B
C
I
take
a
picture
of
it;
it
would
be
great
if
you
can.
Yes,
okay,
thank
you
mark.
Have
you
reverted
the
equal
request
already.
B
I've
I've
submitted
the
pull
request
to
revert
it,
so
the
poll
request
is
being
evaluated
now.
E
For
testing
just
say
that
we
want
to
download
it
not
from
the
last
master
build
but
from
like
fixed
fixed,
so
build
number
800
or
whatever
was
was
the
number
where
the
pull
request
was
applied
and
we
can
test
it
independently.
On
the
build
of
jenkins,
I
scio,
because
we
probably
don't
want
to
block
building
the
website
by
buy.
D
This,
okay,
so
sorry
to
interrupt
spinning.
So
could
you
do
another
pull
request,
maybe
with
your
proposed
fixed
and.
E
Yes,
my
suggestion
is
to
create
a
pull
request
that
would
pull
a
fixed
version
of
the
ascii
dock,
an
old
one,
and
it
would
contain
this
fix
so
that
we
can
verify
that
it
actually
works.
Yes
and
then.
E
Revert
the
part
that
fixes
the
eskidoc
pointed
back
to
the
last
build
of
master,
and
then
we
can
independently
merge
the
ascii
dock
generator
for
request,
because
this
this
will
only
make
the
jenkins
io
part
more
robust.
So
it's
it's
not
necessary
to
merge
behind
changes.
First,
yep.
D
B
If
successful
will
then
be
able
to
fix
the
master
branch
when
we
merge
it
so
I'd
say:
let's
have
you
do
your
your
first
choice
is:
let's
have
have
you
submit
your
pull
request,
let's
see
if
it
fixes
the
master
branch?
If
it
does,
then
I
can
throw
away.
My
proposed
revert
of
vihan's
changes
on
pipeline
steps,
doc
generator
and
we
we've
got
the
solution.
Then.
E
E
B
Great,
so
so
the
way
I'm
interpreting
that
spinach
will
will
will,
if
you're,
okay
with
it,
let's
give
it
say
one
or
two
hours
and
if,
in
the
course
of
the
next
two
hours
you
successfully
submit,
you
submit
a
pull
request,
we'll
watch
for
it
and
merge
it.
If,
after
two
hours,
we
haven't
seen
it
I'm
going
to
assume
that
something
got
in
your
way
and
then
we'll
revert
the
pipeline
step
stock
generator
and
we
can
try
again
on
another
day.