►
From YouTube: 2022 06 24 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).
B
A
A
We
don't
need
to
talk
about
change
log,
an
upgrade
guide
because
that's
been
delivered.
I
guess
maybe
we
should
put
in
a
news
item
here
which
is
2.346.1
release
then
require
java
11.
That's
coming
and
support
java,
17
migration
of
user
stories,
nothing
to
talk
about
there
and
then
open
action
items
for
me
on
upcoming
blog
posts.
C
Yes,
so
from
my
there's
one
ticket,
which
is
open
for
a
ui
improvement,
so
I
wanted
to
discuss
more
on
that
I'll.
I'm
searching
for
it
I'll
provide
the
link
as
well
in
few
minutes.
A
A
I've
still
got
the
action
to
archive
the
documentation,
mailing
list
and
use
community.jenkins.io,
and
I've
got
an
action
item
to
create
three
blog
posts:
cdcon
award
winners,
jenkins,
contributor
summit,
summary
from
cdcon,
and
she
code,
africa,
contributon
results.
A
B
B
C
So
in
this
one
there's
a
rendering
problem
and
I
reported
it,
then
I
tried
to
look
for
a
solution
long
time
back
when
I
reported,
then
I
could
not
find
it.
Then
I
forgot
about
this.
Then
someone
very
kind
enough
person
posted
a
comment
feud.
I
think
last
week
that
hey
this
is
what
you
should
be
doing,
something
like
that
and
I
think
that
would
work.
C
But
then
I
try
to
think
about
like
how
would
I
do
it
because
this
shows
up
on
a
particular
jenkins
version
and
in
my
local
installation
of
jenkins
it
shows
up
the
latest
one.
So
so
what
would
be
the
action
items
from
now
on?
Should
it
be
like?
I
should
use
a
particular
version
of
jenkins,
as
I
have
noted
down
in
the
sticker.
A
Well,
so
all
you
have
to
do
is
report,
which
version
you
were
using
so
by
your
saying,
hey.
I
was
using
jenkins
2.27.3
now,
if
you
want
to
use
an
arbitrary
jenkins
version,
the
easiest
way
to
do
that
is
like
this.
You
say:
docker
run.
A
And
then
jenkins,
slash
jenkins,
colon
and
let's
say
you
want
to
use
2.346.1,
that's
how
you
do
it
now.
This
particular
computer's
already
got
a
docker
image
running
at
that
location.
So
let
me
switch
to
another
computer,
we'll
do
it
here,
so
when
I
do
that
it's
going
to
open
up
port
8080
on
this
computer
running
jenkins
2.346.1.
A
A
A
D
A
Good,
yes,
and
it
crop
shows
the
correct
warning
so
did
now
in
terms
of
this
specific
bug
report.
If
you'd
like
we
could
do
a
quick
check
right
now.
I
think
I
use
exactly
this
configuration
myself
with
the
current
version
of
jenkins.
Do
you
want
me
to
check?
Do
you
want
to
shall
we
do
a
look
to
see
if
the
current
version
looks
the
same?
A
All
right,
so,
let's
look
here
at
jenkins
home
and
we're
going
to
use
this
one.
So
the
plugin
that's
being
used
is
view
jobs,
filter
and
I
actually
have
views
already
defined.
Let's
borrow
this
one.
I've
got
a
view
defined
named
failed
and
this
failed
view
says
here:
let's
go
with
unstable,
it's
easier.
There
we
go
so
this
one.
Now,
if
I
edit
the
view
it
should
show
me
here
is
the
job
statuses
filter
is
and
is.
Was
that
the
thing
you
were
using?
A
C
Oh
okay,
so
I
can
so
you're
saying
I
can
work
on
it
under
look
latest
jenkins
version
as
well.
B
C
A
A
A
A
D
C
C
Thanks
a
lot
so
a
question
on
that,
and
I
don't
expect
the
exact
answer,
but
what's
the
best
way
to
find
the
file
where
I
need
to
do
the
change?
Should
I
search
for
the
text?
Job
statuses,
on
the
whole
code.
C
A
A
C
A
A
A
A
C
A
A
A
A
C
A
Right
well
and
and
the
dismaying
part
for
me,
there
is
I'm.
I
know
it's
been
merged,
it
was
merged
eight
hours
ago.
And
yet,
when
I
look
at
it
now
on
jenkins
at
io,
it
still
has
the
old
scrolling
behavior
and
with
the
old
scrolling
behavior.
It's
it's,
I'm
not
sure
if
it's
a
caching
problem
what's
going
on.
A
A
Configuration,
oh
no,
that's
that's
a
different
example!
That's
his
example
of
somebody
else
using
the
same
technique
just
a
moment
here
we
go
okay,
this
one
so
was
on
securing
jenkins.
So
if
I
navigate
to
securing
jenkins,
let's
see
I
when
I
scroll
up
and
down
it
does
not
stick
and
I'm
not
sure
if
that's
intentional
or
more
accidental,
and
so
I
I
think,
needs
more
discussion
or
something's
wrong
and
I'm
not.
A
That's
what
I'm
seeing
anyway
it
does.
It
does
well-
and
I
haven't
looked
inside
the
javascript
code
from
the
website
to
see
if
it
is,
if
the
changes
are
actually
there
and
they're,
just
they've
somehow
been
changed
in
a
way
that
they
are
no
longer
having
the
effect.
So,
if
I
look
at
what
files
are
changed,
we
should
be
able
to
look.
What
should
we
be
able
to
see?
The
jenkins.css
file
should
should
be
findable
somehow
to
confirm
that
these
changes
were
made.
A
Yeah,
in
fact,
maybe
what
I'll
do
is
I'll
just
make
a
comment
here
and
mention.
C
No
nothing
more!
That's
all.
A
A
All
right,
then,
we
had
another
topic:
was
our
long-standing
pull
requests
the
adopt
a
plug-in
pull
request
and
make
security,
re-document
security,
docs,
rework
and
I
apologize
neither
of
those
have
had
progress.
Meg.
I'm
really
sorry.
A
A
And
we've
announced
full
support
for
java
17.,
so
if
you're
running
either
java,
if
you're
running
java
8,
you
need
to
switch
and
if
you're
not
running
java
17.
Yet
it's
worth
experimenting.
A
Okay,
we've
done
a
past
exercise
trying
to
look
for
outdated
prs
that
we
could
close
recently.
My
focus
has
been
trying
to
get
pr's
emerge
that
are
in
the
queue
we've
got
several
screenshot
updates
that
need
review,
and
it's
just
a
matter
of
reviewing
and
getting
them
in
so
we're
up
to
30
open,
pull
requests
again.
My
goal
is
to
get
back
down
to
25.
A
We
could
we
could
do
it
tonight
if
you'd
like
or
we
could
do
it
today.
I
should
have
to
remember
it's
not
night
everywhere.
We
could
do.