►
From YouTube: 2021 08 09 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
Excellent,
very
good,
all
right,
so
I
had
top
of
the
list,
was
a
question
from
dhiraj
on
a
pull
request
and
then
weekly
change,
log
306
and
with
that
is
the
docker
images,
get
additional
tags.
A
Then
change
log,
automation,
lts
change,
log
upcoming
events-
I
don't
have
anything
actually
on
that,
so
let's
just
call
it
hacktoberfest
and
that's
those
are
the
topics
I
have
anything
else
that
needs
to
go
on
the
agenda
before
we
start
working
through
the
topics.
B
C
Okay,
so
it's
very
basic
doubt
that
I
was
embarrassed
to
even
bring
up
then
I
said:
okay,
let's
do
it
so
in
this
we
are
writing.
I
I
added
a
demo
yaml
configuration
for
this
plugin
called
view
job
filters,
and
it's
for
you
know
anyone
who's,
trying
to
understand
how
to
write
yaml.
So
I've
written
that
and
also
when
we
are
trying
to
write
as
we
know,
we
need
to
also
write
tests
for
the
yaml
configuration.
C
So
since
I
have
not
worked
or
written
any
tests
before,
so
I'm
not
sure
how
to
do
that.
So
here
I
have
written
some
with
the
help
of
referring
some
other
tests
that
were
written
previously
in
the
repository.
C
A
B
A
Right,
okay,
and
so
what
what
tim
is
saying
is
that
your
your
test
is
your
test
is
certainly
necessary
because
we
want
to
be
sure
the
constructor
works
and
what
you're?
What
you're
testing
here
is
you're
testing
that
do
the
constructor
and
then.
A
A
Okay,
so
then,
then,
I'm
going
to
I'm
going
to
just
make
my
best
guess
and
kristin
can
correct
me.
I
suspect
what
this
is.
This
annotation
configured
with
readme
says
that
the
jenkins
that
is
started
as
part
of
this
jenkins
configured
with
readme
rule,
so
what
jay
gives
us
is
access
to
a
what
looks
like
a
jenkins
instance,
and
that
looks
like
a
jenkins
instance
has
been
configured
by
reading
the
contents
of
this,
this
job
filter
of
this
readme
file.
So
it
acts
like
this
was
the
yaml.
A
A
So
but
then
what
tim's
saying
is
okay,
what
this
did
is
this
configured
a
jenkins
instance
that
has
views
that
contain
a
list
and
the
columns
in
the
list
include
status,
weather,
job
name,
etc.
So
all
that
configuration
happened,
but
in
your
test
what
this
thing
does
this
new
build
duration
filter?
Is
it
calls
a
constructor
and
creates
a
new
one
of
these?
It
is
not
looking
at
the
jenkins
that
is
configured
this
j
thing
here
and
it's
not
exploring
it
to
see
that
the
values
were
set
as
expected
here.
A
A
A
A
A
A
A
So
if
I
go
to
jenkins
javadoc,
so
the
javadoc
for
core-
and
I
look
at
jenkins
core
and
now,
if
we
look
for
the-
and
this
is
a
very
popular
word
so
jenkins-
the
jenkins
object,
I'm
just
going
to
have
to
search
for
it
the
hard
way
here
we
go.
This
thing
now
on
this,
so
here
is
the
javadoc
for
the
jenkins
object
and.
A
B
A
Okay,
well
so,
let's
well,
let's,
let's
do
some!
If
you're!
Okay
with
it
are
you?
Okay,
if
we
just
do
some
exploring
together?
Oh
I
would
love
it
okay,
so
so,
first,
let's
list
the
pr's
okay,
so
pr
checkout
and.
A
Just
for
fun
took
tim's
suggestion
and
said
collection
of
okay
going
back
to
javadoc.
Now.
D
C
A
C
D
A
A
A
A
A
A
A
A
A
Which
it
is
java.,
so
the
view
job
filters
plug-in
provides
this
okay,
good,
which
I
guess
you
you
would
have
already
told
me.
Wouldn't
you
because
guess
what
that's
this,
what
it
says
this
plugin
exactly
as
you
documented
it
sorry
I
if
I
would
read
things,
would
go
better
and
then,
but
now
the
challenge
is:
how
do
we
get.
A
A
From
the
top
level
jenkins
right
isn't
that
what
you're?
What
you're
trying
to
do
is
your
challenge
is
you
need
to
you
want
to
assert
that
the
values
you
assign
like
this
amount
of
60
and
the
amount
type
string
of
days
are
correctly,
are
set
to
those
exact
values?
But
in
order
to
do
that,
you
need
to
find
the
build
duration
filter
inside
the
jenkins,
where
it
was
allocated
exactly
yes,.
C
A
A
Let's
see
this
has
diff
yeah.
We
would
look
at
the
views
and
then
on
each
view
I
would
expect
to
be
able
to
find
filters
associated
with
that
view.
D
E
C
I
think
you
should
take
your
time,
then,
because
we
don't
want
to
take
up
much
time
here.
A
Well,
my
apologies
this.
This
is
a.
This
is
a
great
one.
I
think
I
think
I
think
we
can
go
through
and
and
do
some
searching
there
and
and
what
I
may
do
then,
is
in
our
next
session
next
week.
Use
bring
the
summary
of
the
searching.
If
you
don't
mind
waiting
that
long
or
I
I
could,
I
could
send
a
send
a
textual
summary
as
well.
Oh,
hey,
here's
how
you
do
it,
but
the?
How
did
I
find
it
is?
A
C
E
C
A
Oh
no,
I
think
I
think
what
you
did
was
great
and-
and
I
I
mean
I'm
delighted-
you
thought
to
write
tests
and
I'm
really
pleased
that
that
they
have
a
framework
already
in
place
that
will
allow
you
to
write
tests.
For
me,
that's
that's
quite
impressive
right.
It's
this
little
thing
right
here
is
a
dramatic
step.
That's
a
very
nice
step
forward
that
they
made
hey
here's
this
tool
that
makes
it
relatively
straightforward
for
you
to
write
tests.
C
A
A
A
C
Okay
and
second
question
was
that
this
process
of
writing
text
for
jks
repository
using
jenkins
configured
with
the
readme
rule,
and
everything
is
this.
So
what
if
we
write
a
blog
on
this
to
help
anyone
so
does
this?
Is
this
required
or
it's
it's
only
going
to
help
like
two
or
three
people,
so
is
it
worth
the
effort?
That's
what
I'm
trying
to
know.
A
And
I
think
it
I
think
it
is
worth
the
effort
and
it
might
be,
it
might
be
a
and
a
cool
way
to
introduce
the
concept
of
so,
for
instance,
I
believe
we've
got
on
the
on
the
site.
I
think
there
is
an
introduction
to
jenkins
rule
that
you
would
be
doing
everyone
a
favor
if
you
taught
if
you
were
willing
to
blog
more
about
it.
A
A
C
C
A
D
D
A
D
A
All
right
so
diraj
excellent
question:
let's
put
that
as
a
an
action
for
next
week
mark
next
week
summarize
how
to
explore
the
jenkins
instance
from
inside
a
debugger
running
a
test,
and
I
confess
oh
actually,
maybe
this
would
okay.
A
Maybe
what
we
ought
to
do
is
a
dueling
dueling
debuggers
exercise
because
kristin
I'll
bet
you're
an
intellij
user.
Aren't
you.
D
C
A
Okay,
even
better
so
so
what
we
could
do
is
is
we
do
it
as
two
steps
as
okay
mark
show?
Here's
how
I
do
it
with
netbeans,
because
it's
the
debugger
I'm
familiar
with,
and
then
we
asked
kristin.
Okay
kristin.
Can
you
do
the
same
thing
with
visual
studio
code
or
to
do
something
different
because
dhiraj,
I
bet
you
use
vs
code.
Don't
you?
A
D
A
A
A
C
A
A
A
A
D
C
A
A
C
A
Oh,
oh,
that
you
know
I
I
hardly.
I
don't
remember
the
last
time
I
reworded
a
comment.
So
I
reworded
a
comment.
That's
that's
in
the
yaml
file
as
a
comment
just
because,
if
it's
in
the
yaml
file
as
a
comment,
usually
somebody
would
would
want
that
comment
to
be
able
to
take
them
to
to
the
thing
leaving
it,
as
whatever
text
they
did
is
fine
because
it
won't
ever
be
displayed
to
a
reader.
E
A
Okay,
yes,
all
right
now,
we've
got.
We've
got
one
change
coming
tomorrow.
That
really
doesn't
go
in
the
change
log,
but
I'm
going
to
use
it
for
a
blog
post.
Actually
I
wonder
dhiraj
do
you
want
to
be
a
co-author
on
the
blog
post
with
me.
A
So
so
what's
happened
is
we've
got.
We've
got
the
jdk
11
the
transition
from
java
8
to
java
11
oops
java
11
as
the
the
default
jdk
java
on
our
docker
images,
and
what
that's
going
to
do
is
that
means
beginning
with
2.307
next
week,
not
this
week.
But
next
week
the
docker
images
will
run
under
java
11
rather
than
java
8
by
default,
as
in
order
to
retain
compatibility,
retain
the
ability
to
revert.
A
A
A
A
good
question
here
so
mark
and
dhiraj
getter
works
for
you.
That
would
be
great
by
getter
in
the
would
you
actually
would
do
you
prefer
getter,
or
do
you
want
the
jenkins
community
channel
gitter
is
easy.
For
me,
community.jenkins.
A
A
Okay
next
topic,
then,
was
change.
Log
automation-
and
we
had
talked
last
week
that
last
week
or
two
weeks
ago
that
one
of
daniel
beck's
concerns
was
hey.
If
we
have
this
automation
and
no
one
reviews
it,
it
makes
things
much
worse
than
the
change
logs.
We
have
now
and
dhiraj
you
and
I
and
kristen
and
meg
as
well.
I
think
all
agreed:
let's
go
ahead
with
the
automation
and
we'll
regularly
review
those
pull
requests,
pull
requests
so
that.
D
A
A
Okay,
so
I've
still
got
a
review
review
the
pull
request
and
approve,
but
I
think
we
agree.
That's
a
good,
a
good
thing
to
do
and
we'll
we'll
enjoy
it
together.
A
A
A
D
A
D
A
A
A
A
A
A
Okay.
So
what's
what
you're
seeing
on
your
screen
is?
This
is
the
lts
2.302.1
checklist
maintained
by
the
release,
lead
and
the
release
lead.
This
time
is
bazel
pro
so
basil
is
bazel
has
checked
off
the
items
that
are
done,
but
we've
I
haven't,
seen
a
back
porting
announcement
email
and
I
definitely
have
not
seen
the
back
ports.
A
A
A
B
A
A
A
A
A
A
A
C
Which
one
do
you
pick
out
from
the
weekly
to
the
this
one
left,
one.
A
So
is
that
what
you
were
asking?
Dhiraj?
Yes,
yes
yeah!
So
it's
start
with
2.289
the
predecessor,
because
changes
will
be
visible
to
users
for
the
first
time
if
they
arrived
on
2.289
and
were
not
backported
to
289.3.
A
A
C
Just
a
small
question:
what
we
were
doing
is
from
the
predecessor
till
the
current
one.
We
are
fetching
all
the
entries
from
the
weekly
automation,
file
and
pasting
to
the
left,
one
that
you
were
showing
and
then
we
were
trying
to
find
out
that
are
these
entries
were
mentioned
in
the
previous
lts
logs
or
not,
and
if
they
were,
we
are
deleting
them
right.
A
All
right
thanks,
everybody,
I'll
post,
the
recording,
probably
tomorrow
the
next
day,
I'm
a
little
bit
behind
on
getting
all
my
recordings
posted.