►
From YouTube: 2022 08 18 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
Okay,
it's
on
okay,
welcome.
This
is
the
jenkins
docs
office
hours
european
edition
for
august
17th.
Today,
on
our
agenda.
We
have
some
action
items
if
behind
behind
just
showed
up
so
we'll
be
able
to
check
in
on
the
google
server
of
code,
just
some
updates
about
the
september
lts
release,
which
is
2.361.1.
A
Small
update
on
search
improvements
for
jenkins.io
discuss
the
commercial
short
support
page,
the
blue
ocean
status
statement,
change
log
entries
from
multiple
repositories
and
the
hacktoberfest
documentation
contributions.
A
So
first
things
first
just
to
touch
base
on
the
action
items
and
mark
is
not
here
this
week
he's
on
vacation.
So
we
have
alyssa
here,
helping
us
out
today
with
the
recording.
So
thank
you
very
much
to
melissa
and
all
the
action
items
are
in
the
same
status
as
previously,
where
mark
still
needs
to
complete
the
blog
post
and
such
however,
the
sheet
code
africa,
con
contributon
results,
blog
post
has
so
that
is
a
victory
in
this
case.
A
So
I
just
want
to
check
in.
Would
you
be
willing
to
share
what
you've
got
since
our
last
update
on
the
google
summer
code.
B
B
So
we
know
he'll
talk
about
the
progress,
so
we've
created
the
pull
request
for
the
separation
of
parameters
on
the
page.
So
the
draft
here
is
ready
and
in
that
pr
we
plan
to
not
only
separate,
not
only
include
the
processing
layer,
but
also
include
the
engine
configuration-
maybe
the
readme
for
that,
and
also
some
tests
for
the
processing
layer,
so
that
will
also
be
included
and
other
than
that.
We
are
also
investigating
on
one
of
the
anomalies
that
we
saw
in
the
documentation
of
bit
bucket
server.
B
So
we
were
basically
seeing
some
deprecated
steps
that
in
inside
the
documentation-
and
that
also
led
us
to
seeing
some
pages
that
that
were
actually
not
linked
from
the
main
page.
So
let
me
just
share
my
screen
and
show
it
to
you.
B
B
Okay,
great
so
I'll,
basically
just
search
for
the
issue
that
mark
had
created
in
the
pipelines,
documentation,
repository
and
yeah.
So
it
was
about
the
ignoring
experimental
plugin
releases,
and
for
that
I
saw
that
the
page
that
is
mentioned
by
mark
was
already
fixed,
but
the
old
plugin
link
was
still
leading
us
to
that
ascii
dock,
and
this
indicates
only
one
thing
that
the
cleanup
of
the
ascii
docs
is
in.
That
folder
is
not
yet
done.
B
So
I
wanted
to
maybe
create
an
action
item
for
one
of
the
maintainers
for
this
to
run
a
clean,
ascii
docs
for
this,
so
that
whenever
the
next
build
of
the
pipeline
steps
documentation
happens,
we
can
feed
the
new
ascii
docs
onto
the
folder
so
that
we
get
rid
of
these
old
laying
links
and
in
this
way,
we'll
also
ensure
that
enough.
The
older
document
of
older
documentation
sits
on
our
pages
any
of
our
pages.
B
So,
for
example,
the
one
that
we
saw
was
related
to
a
bit
bucket
server
inside
the
patent
groovy
libraries.
B
And
so
we
also
posted
a
query
on
the
pipeline
authoring
special
interest
script
channel
on
getter,
and
it
was
basically
about
the
snippet
generation
of
this
built
bucket
server
and
inside
that
we
were
not
able
to
get
the
extensions
choice
to
be
filled
by
entering
different
choices.
B
So
I'll,
maybe
open
up
modern
scm,
and
in
this
aside
from
the
standard
scm
that
we
have
everywhere,
we
also
have
bitbucket
servers
sitting
outside
and
in
this
the
the
name
of
this
field
is
trades
and
according
to
christian,
this
should
be
extensions
because
we
tested
it
using
the
snippet
generator
and
it
is
supposed
to
be
renamed
to
extensions.
So
this
was
that
point
that
we,
where
we
thought
that
this
might
be
some
of
the
older
documentation
which
is
not
yet
removed.
B
But
we
have
to
see
basically
that
cleanup
is
required
anyways,
because
the
old
links
which
are
no
longer
linked
from
anywhere
but
those
ascii
talks
are
still
there.
And
basically
I
found
that
link
using
one
of
the
tickets
that
that
was
created
the
original
ticket
behind
the
experimental
plugin
releases.
So
I
picked
that
link
from
there
so
yeah.
Basically,
it
should
be
needed
with
extensions.
That
is
what
we
are
working
on
and
the
sniper
generation
is
also
not
happening
in
the
way
we
expect.
B
So
we've
posted
a
query
on
the
pipeline
optimistic
and,
let's
see
what
happens
to
that,
but
other
than
that
I
have
basically
worked.
I've
also
figured
out
some
criteria
for
setting
up
the
configuration
file
and
that
I
have
updated
in
the
readme
of
this
same
per
request.
So
I've
added
some
tasks
for
this
and
that
basically
contains
that
extra
set
of
information
that
we
want
for
the
parameter
configuration
so
the
maintainer
could
go
through
this
file
so
yeah.
This
was
the
progress
for
the
week
thanks
a
lot.
A
Thank
you
very
much
beyond
now.
I
have
to
admit
since
mark's.
Not
here,
I
don't
know
that
we'll
have
such
lovely
questions
as
he
normally
would
provide,
but
I
can
see
what's
going
on
and
I
I
know
we
all
appreciate
the
work
that
you're
doing
on
getting
this
cleaned
up
and
looking
really
nice
for
with
for
the
jenkins
project.
So
thank
you
again
for
all
your
continuous
work.
A
Next
on
the
agenda,
just
updates
about
the
jenkins
september
lts
release,
which
is
going
to
be
version
2.361.1.
A
Faith
has
asked
for
a
blog
post
about
the
java
11
requirement,
really
just
an
overview
of
jenkins,
historically,
that
they
can
share
in
the
cd
foundation
blog
so
I'll
be
coming
up
with
that.
A
We
have
basel's
post
from
when
job
11
was
required
in
the
weekly
release
as
a
great
piece
to
work
from
and
all
the
information
that
we've
got
since
then
as
well
on
any
releases,
so
lots
of
material
to
work
with
and
I'll
be
working
on
that
once
I'm
able
to
finish
up
the
upgrade
guide
and
change
log
which
are
in
initial
draft
stages
right
now,
but
have
been
submitted
as
a
draft
pr.
The
baseline
for
this
release
is
going
to
be
2.361.
A
That
was
in
the
developer,
mailing
list
thread
and
it
again
it
does
require
java
11..
So
java
8
supports
being
dropped
completely.
We've
been
doing
everything
we
can
to.
Let
people
know
about
this
ahead
of
time,
though
so
we've
done
a
great
job
of
making
sure
that
everyone's
aware
and
then
the
other
thing
that
is
coming
along
with
this
is
java.
17
support
will
be
is
available
with.
B
A
And
people
can
start
previewing
that
and
testing
that
if
they
want
to
the
upgrade
guide
and
change,
log
r
is
here
and
available.
If
anyone
wants
to
take
a
look
share
feedback,
there's
a
lot
that
has
been
added
already,
we've
got
a
lot
of
changes
coming,
so
there's
still
more
to
be
done
there,
but
I'll
be
working
on
that
and
getting
that
taken
care
of
search
improvements
for
jenkins.
A
So
this
is
something
that
mark
has
mentioned
in
weeks
past
that
the
algolia
search
is
out
of
date
for
jenkins,
as
it
stands
right
now,
so
we
need
to
update
from
the
legacy
scraper
to
the
new
version
and
make
sure
that
the
search
results
are
get
are
appearing
as
they
are
expected
to
right.
Now,
if
you
search
for
upgrade,
for
example,
you
won't
find
the
upgrade
guide
so
easily.
A
This
is
something
that
has
to
be
taken
care
of
by
either
mark
or
gavin
mogan,
since
it
requires
specific
credentials,
so
they
will
have
to
take
care
of
that,
or
at
least
work
on
that
and
mark's
already
created
a
an
issue
in
github
for
this.
So
we
do
have
something
to
track
with
any
work
can
be
done
associated
with
that.
A
We
also
have
brought
this
up
in
the
past,
but
just
again
the
commercial
support,
page
proposal
that
was
brought
by
gavin
mogan.
We
have
a
support.
A
vendor
support,
page
right
now,
that
is,
could
be
better
and
gavin's
been
looking
for
feedback
ideas,
any
kind
of
proposals
that
might
help
build
a
better
support
page
for
vendors
direct
communications
links
directly
to
help
what
kind
of
offerings
they
have
and
any
and
various
other
topics
that
would
be
great
to
capture
in
these
situations.
A
A
Yeah
there
has
been
a
proposal
to
ask
the
outreach
group
to
contact
potential
vendors
as
well.
I
think
mark
was
supposed
to
check
in
on
that.
I
have
not
heard
as
far
as
what
the
progress
is
on
that
goes.
A
A
Moving
on
the
blue
ocean
status
statement
that
we've
added
to
the
blue
ocean
documentation
has
been
added
to
more
pages
and
the
plugin
page.
The
docker
hub
page
itself
needs
to
be
updated,
but
that's
a
specific
set
of
credentials
again
and
we're
not
sure
if
we
have
those
to
make
that
update
ourselves.
A
We
might
have
to
check
in
with
some
other
teams,
but
the
idea
is
that
we'll
have
the
status
statement
aligned
in
there
as
well
and
then
there's
a
tutorial
page
for
creating
a
pipeline
that
needs
the
status
added
and
something
I'm
going
to
take
care
of
as
well.
A
A
But
mark
is
going
to
ask
the
jenkins
developer
list
about
something
we
can
do
about,
fixing
that
putting
them
all
combining
them
all
into
one
entry
or
you
know,
that's
still
to
be
discussed
so
again,
any
ideas,
any
feedback.
Any
proposals
would
be
great
to
share,
and
then
the
last
thing
that
I
had
on
my
list
on
our
list
today
was
hacktoberfest,
which
is
coming
up
in
october.
A
We've
got
some
things
that
we
can
work
on
for
hacktoberfest
and
try
to
submit
such
as
the
docs
need
to
be
converted
from
wiki
pages
to
markdown.
There's
still
a
lot
of
older
pages
that
need
this
update.
This
was
actually
the
project
one
of
the
projects
that
we
hosted
mentored
last
year
and
we
were,
and
the
docs
team
was
able
to
help
get
a
good
amount
of
stuff
converted,
which
was
great.
A
There's
gonna
be
there's
some
things
that
we
were
discussing
but
can't
be
included
just
because
they
require
too
much
knowledge
of
jenkins
to
be
really
helpful.
It
would
take
more
time
to
learn
and
understand
what
it
all
means
than
it
would
be
to
do
something
like
inclusive
naming,
so
we're
going
to
keep
working
on
that
something
I'm
going
to
discuss
with
mark
as
we
go
along
and
get
closer
to
see
what
other
docs
options
we
might
have
and
again.
This
is
something
that
we'd
be
happy
to
discuss
here.
If
there's
any
ideas.
A
This
is
just
something
that
it's
new
for
me
and
I'm
really
excited
about
being
a
participant
of,
and
I
would
love
to
just
expand
all
my
skill
sets
and
relationships
within
the
jenkins
community
through
it
so
yeah
any
help
is
welcome.
A
A
A
Okay,
great,
thank
you
so
much
for
letting
me
know,
and
with
that
I
think
we
can
wrap
up
a
little
early
today.
The
video
will
be
available
once
mark
has
a
chance
to
upload
it
again
since
he's
out
this
week.
It
will
probably
be
next
week,
sometime
hopefully
earlier,
but
it'll
be
shared
regardless.