►
From YouTube: 2022 06 28 Git Cache Maintenance
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
this
is
google
summer
of
code
jenkins
gate
cash
maintenance.
It
is
the
28th
of
june
2022.
B
A
B
A
B
So
this
week
I
added
that
you
know
getting
all
the
caches
from
the
you
know
on
the
jenkins
controller,
that
logic
has
been
added
and
I
am
able
to
run
the
maintenance
tasks
on
all
the
caches.
Okay,
that's
what
has
been
that's
what
I've
done
and
then
yesterday
I
worked
on.
You
know
we
have
discussed
about
form
validation
like
you
know
where
we
can
store
incorrect
data
also
into
the
file
and
then
validate
them
whenever
we
are
executing
the
maintenance
task.
A
Excellent,
thank
you.
That's
wonderful!
So
so,
let's
are
you?
Okay?
If
we
take
a
look
at
it,
yeah
sure?
Okay,
all
right,
so
this
one
looks
like
oh
okay,
so
you're
intentionally
maintaining
the
ordering
by
using
a
linked
hash
map
and
the
the
idea
there
is.
You
want
to
execute
with
a
particular
order.
B
B
This
is
for
the
form
validation
which,
which
we
have
discussed
you
know
not
to
like
which
allows
saving
of
incorrect
data,
but
it
verifies
when
I'm
running
executing
the
maintenance
stars
so
that
that's
the
logic
for
this
commit
in
this
comment.
A
Very
good,
okay:
now
we
will
oh-
and
this
is,
I
assume,
just
a
diagnostic
thing
to
help
you
as
you're,
but
you
may.
You
may
in
fact
want
to
use
a
system
or
a
logging
system,
because
then
you
can
read
it
and
the
user,
if
they
ever
have
a
question,
could
increase
the
logging
level
and
see
it
telling
us
or
decrease
the
logging
level
to
say:
oh,
it's
not
happening.
A
It
would
each
class
would
have
a
logger,
and
then
you
use
that
class's
logger
that
allows
the
administrator
to
do
very
fine-grained
control
of
which
things
they
want
to
log,
to
see
proof
that
something's
happening.
So
this
one
might
be
a
an
info
level
or
a
let's
see
I
have
to
I'd,
have
to
look
up
the
logger
levels.
A
Yeah,
so
this
one
could
be
a
debug
level,
even
where
you
say:
hey
only
show
this
when
we're
doing
debugging,
debungling
level,
logging,
okay,
but
about
this
the
technique
you're
using
with
small
commits,
looks
very,
very
good.
That's
that's
exactly
the
right
way
to
do
it.
A
B
A
A
Well,
and-
and
you
could
you
could,
for
instance,
you
could
do
this
if
you
were
instead
to
switch
and
use
a
parameterized
test,
then
you
could
make
these
invalid
invalid
syntax
items
each
parameters
and
then
you
do
the
same
syntax.
You
say
I
expect
to
throw
antler
exception
and
all
you
do,
then,
is
in
the
test.
You
call
task
scheduler.getcrontab
list
and
it
will.
It
will
then
use
that.
So
so
that's
this
one
won't
have
the
behavior.
You
want
right
now,
but
it's
pretty
easy.
A
You
just
split
it
out
into
a
separate
file,
task,
scheduler
parameterized
test
and
then
make
the
parameters
your
incorrect
syntax.
That
has
the
nicety
that
then
it's
it's
easy
to
see
what
the
test
is
asserting,
because
all
it's
asserting
is
that
this
exact
statement
will
throw
an
exception.
A
A
B
So
actually,
there
are
two
ways
of
like
how
I
want
the
session
to
be.
First
thing:
is
I
never
like
the
maintenance
stars
are
running
okay,
but
I
never
ran
it
properly.
Like
I
never
run,
I
ran
all
the
maintenance
tasks
like
I
like
you
know,
setting
it
like
for
one
hour
and
then
setting
it
for
like
two
hours
running
every
two
hours.
So
that's
something
which
I
haven't
done,
but
the
maintenance
tasks
are
running.
B
It's
getting
a
lock,
it's
a
it's
using
that
lock
running
running
the
maintenance
task
on
that
cache
and
then
getting
unlocked
so
that
logic
has
been
written,
but
I
haven't
tested
it
completely.
B
Okay
and
the
other
thing
which
I
wanted
in
this
session
was
where,
like
regarding
legacy,
get
maintenance,
okay
for
versions
less
than
2.30.
Okay,
where.
A
B
Write
the
logic
for
it.
Do
I
write
it
in
the
git
login
or
the
get
client
plugin,
because
if
I
wanted
it
to,
if
I
want
to
write
it
in
the
get
login
right,
I
I'm
not
getting
the
get
version,
I'm
not
able
to
use
the
get
version
underlying
git
version
or
cli
version,
so
that
that
that's
something
I
was
not
able
to
proceed.
A
A
B
A
A
Help
files,
okay,
yeah,
so
it
doesn't,
it
doesn't
have
any
way
of
getting
the
okay,
so
the
the
choices
are
are
well.
Do
you
have
a
preference,
because
you
could,
for
instance,
just
create
a
new
api
somewhere
in
the
git
plugin
that
you
can
use
to
determine
what
version
of
command
line
get
your
is
available?
A
B
A
B
A
A
A
And
and
this
you
certainly
could
do
inline
inside
the
git
plugin,
it's
quite
allowed
because
in
your
case
you
I
think
we
we
are
confident
that
we
don't
that
we
always
want
to
use
command
line
git
to
perform
the
maintenance
operations.
Yeah.
B
Yeah
because
I
I
sent
you
the
link
of
a
forum
yesterday
right
where
I
asked
about
jkit
and
they
were
like
they
don't
have
maintenance
tasks
ready
and
that
thing
so
yeah.
A
Right,
yeah
and-
and
I
I
agree
with-
I-
don't
think
we
even
if
they
did
have
it,
it
would
probably
only
be
in
the
j,
get
six
family
and
we're
not
ready
to
adopt
that
yet
so
so,
for
me,
it's!
This
is
too
early
for
us
to
be
forced
onto
jet
six.
So,
even
if
they
had
it,
it
would
probably
not
have
arrived
until
j
get
six
right
now.
I
think
they're
about
to
release
j,
get
6.3.
B
Okay,
so
also,
can
I
call
this
method
directly
like
wherever
I
need
it
to.
You
know,
get
the
version
of
the
get
like
you
know
to
get
the
good
version.
A
I
I
think
you
could
right
so
I
was
assuming
that
the
play
you
would
probably
want
to
to
isolate
the
knowledge
of
get
versions
and
which
things
do
maintenance
inside
of
your
maintenance
task,
the
maintenance
implementation
which,
whichever
one
that
is
inside
that
class.
But
if
you
need
it
in
multiple
places,
you
could
certainly
either
put
it
in
a
in
a
utilities
class
and
use
the
use
the
utilities
class
statically
or
copy
it.
If
you
need
to
okay,
it's
terrible
because
I.
B
A
Well-
and
I
think
I
think
that's
a
that's
a
good
thing-
I
if
we
look
at
this
at
this
code,
it's
doing
exactly
that
right.
So
the
knowledge
of
this
thing
is
it's
doing
logging
to
tell
us
if
it
couldn't
parse
the
git
version
into
a
major
version,
a
minor
version
in
a
patch
version,
and
and
if
you
find
this
kind
of
thing,
helpful
you're
certainly
welcome
to
make
this
an
api.
That's
somehow
available
at
least
package
protected
inside
the
git
plugin.
A
I'm
not
sure
we
want
to
make
it
a
publicly
accessible
api,
because
I
really
would
rather
not
have
get
plug-in.
Consumers
have
any
logic
about
what
version
of
command
line
git
they're
using
it's.
It's
it's
bad
enough
that
that
the
git
plug-in
the
git
client
plug-in
have
to
know
about
command
line,
git
versions,
let's
not
leak
that
information
to
our
callers.
If
we
can
avoid
it.
A
But
if,
if
you
would
like
to
make
this
this
into
a
package
protected
method
somewhere
in
the
git
plug-in,
you
have
my
full
support,
it's
I
know
how
important
it's
been.
I
I'm
embarrassed
to
admit
how
important
it's
been
to
me
to
see
things
like
here.
I'll
show
you,
the
one
that
that
that
has
mattered
to
me
is
when
the
when
the
command,
when
the
version
of
command
line
get,
is
logged
into
the
jenkins
build
log.
That
is
actually
quite
precious
information.
Oh
here,
let's
just
do
ci.jenkins.io
that'll
be
good
enough.
A
Oh,
it's
even
using
jgit,
so
that
doesn't
help
me.
Okay,
let's
use
something
else
like
this
one,
but
what
it
does
is
it
reports
the
the
command
line,
git
version
and
by
reporting
the
command
line,
git
version,
I'm
able
to
diagnose
quite
a
number
of
problems
much
more
easily,
so
you
have
my
full
support
for
logging.
B
A
Excellent
question
very
good
question:
are
you
okay,
if
I
show
a
demo
of
how
logging
works
in
jenkins
and
why
I
think
it's
so
great
yeah
sure
sure?
Okay,
so
so
this
is
my
my
jenkins
controller
and
and
what
I
want
to
show
you
now
sorry,
it's
running
dark
mode
is
dark
mode.
Okay,
yeah!
It's
fancy!
Okay!
So
so
here
is
my
jenkins
controller
and
it
has
some
interesting
jobs
on
it.
A
If
I
go,
if
I
want
to
change
what's
happening,
if
I
want
to
see
what's
happening
with
logging,
I
go
to
manage
jenkins,
and
now,
if
I
scroll
downwards,
there
will
be
a
system
log
thing
here,
so
the
system
log
gives
me
access
to
to
jenkins
log
messages
from
the
web
page.
So
when
I
click
all
jenkins
logs,
it
shows
me.
A
Oh
here
it
was
upgrading
jenkins
last
was
356
we're
running
357
and
it
it
talks
about.
Oh
hey.
I
loaded
an
attached
plug-in
this
thing
and
now
it's
re
connecting
agents.
So
so
the
logging
is
is
already
available
to
me
from
the
web
ui.
So
you
can
see
what's
happening
now.
The
the
more
elegant
thing
here
is
that
maybe
I
need
something
even
more
detailed,
so
I
can
go
to
log
recorders
and
I
can
add
a
new
log
recorder
and
I'm
going
to
call
it
get
scm.
A
A
A
A
That
might
be
good
enough,
so
let's
just
turn
on
the
logger
for
git
scm
and
we're
going
to
go
so
get
scm,
I'm
going
to
say,
create
a
new
log,
a
new.
This
is
creating
a
new
logger
and
it
says
all
right.
What
what
would
I
like
and
I'm
going
to
say?
I
want
the
class
that
I'm
logging
to
be
this
one
so
I'll
now
it
will
help
me
along
the
way-
and
I
like
that
it
helps
me
so
I'm
going
to
say,
hudson
dot,
plugins
dot.
A
What
was
it
again?
It
was
hudson.plugins.get.
A
A
And
it's
performing
some
operations
good.
Now,
let's
see
if
anybody
else
is
running
okay,
this
one's
cued,
so
this
one
has
run
today
good.
So
now,
if
we
go
back
here
and
look
at
log
records,
this
is
something
that
it
logged.
It
says
not
adding
git
tag
action
to
build
nine,
likewise
to
build
24
and
it
performed
a
checkout.
A
A
Is
there
something
that
we
where
we
might
benefit
from
a
log
entry
yeah?
For
instance,
you
might
choose
hey
to
log
something
at
find
that
reports
the
size
of
the
cache
entries.
Something
like
that.
Hey
returned
this
many
cache
entries,
and
you
could
do
that
here
that
kind
of
thing
and
then
you
would
see
it
by
turning
on
the
logging
for
abstract
get
a
cm
source.
A
B
Yeah
yeah
one
more
then
I
I
have
a
doubt
like
now.
What
do
I
have
to
consider
like
to
log
like
what
kind
of
information
should
I
log
into
the
using
the
log
like?
Do
I
have
to
like
log
all
the
procedure?
Whatever
is
happening
or
like?
I
I'm
not
sure.
A
I
think
it's
up
to
you
my
my
my
past
experience
was,
I
seem
to
have
made
the
continual
mistake
of
never
logging
enough.
A
I
I
that
that
may
sound,
really
terrible,
but
but
very
frequently
when
I've,
when
I'm
when
someone
is
reporting
a
problem,
that's
out
in
the
world
and
saying
hey,
I'm
running
jenkins
in
this
in
some
environment
and
of
course
they
never
tell
us
all
the
details
of
their
environment.
They
never
tell
us
nearly
enough.
A
A
So
so,
for
me
at
least,
I
found
that
the
more
I
do,
this,
the
more
often
I'll,
put
simple
little
statements
in
that
tell
me
how
things
are
progressing
so
that
I
can
know
it
and
put
them
at
a
a
relatively
fine-grained
logging
level,
so
that
they're
not
on
by
default,
so
they're
not
costing
anything.
But
if
I
needed
to
ask
someone
hey,
please
turn
up
the
logging
on
this
thing.
They've
already
got
the
code
and
I'm
not
having
to
deploy.
Have
them
deploy
a
new
debug
build
to
get
it.
A
Right
so
so
the
one
of
the
techniques
that
I
found
for
me
most
recently
helpful
was,
I
would
put
the
logging
statements
in
there
and
then
actually
turn
the
logging
on
to
watch
for
myself
that
the
code
was
executing
the
way
I
expected
without
using
a
debugger
to
do
it
and,
and
it
turned
out
it
as
it.
The
result
for
me
was
it's
easier
than
for
me
to
know
hey.
That
logging
is
useful
and
it's
saying
the
right
thing
and
the
code
is
executing
the
right
thing.
Okay,.
B
A
B
A
For
now,
for
for
now,
I
think
yeah
you
should
just
log
it
now.
Ultimately,
we
may
want
in
in
a
later
part
of
the
project,
for
you
to
give
a
location
on
the
ui
where
we
can
show
that
to
users,
because
there
certainly
are
locations
in
jenkins,
where
people
can
see
diagnostic
information
right
that
that
logging
page
is
one
example
of
diagnostics.
B
And
one
more
thing:
can
you
actually
so
when
I
am
using
the
so
little
incremental
build?
Okay,
my
ide
is
not
a
supporting
you
know
one
or
two
dependencies
like
the
gig
dependency,
isn't
being
supported
like
only
the
id,
but
when
I
am
building
the
project
is
running.
Okay,
the
build
is
successful,
but
the
id
throws
a
lot
of
errors
like
I'm
using
intellij
right
now.
It
says,
get
you
know,
dependency
not
found
and
then
all
kind
of
red
files
and
red
lines
everywhere.
It
doesn't.
Let
me
run
the
test.
A
I
manage
professionally
and
so
development
is
my
hobby
and
therefore
I'm
not
a
good
voice
to
tell
you
how
to
configure
intellij,
but
there
are
lots
of
people
who
are
using
intellij
and
they
should
be
able
to
to
answer.
Oh,
you
need
to
do
this
magic
step
or
that
magic
step.
I
thought
there
was
some
configuration
or
some
compilation
thing
that
you
have
to
do
in
order
to
make
it
make
it
find
all
the
things
that
you're
seeking
okay.
B
So
I
I
I
think
I'll
I'll
send
a
mail
and
then
you
know,
I
think
that
could
help
me
out,
because
I
wasn't
able
to
test
anything.
Then
I
had
to
use
the
previous
version
of
it
and
comment
all
these
to
test
the
things
and
then
I
can
uncomment
it
so
yeah
and
I
have
a
doubt
a
regard
like.
If
can
you
open
the
file?
You
know
a
task
executor
file.
You
know
you
bet
so
task
executor.
B
So
here,
if
you
can
scroll
down
so.
B
That
they
get
get
client
method,
the
get
get
client
method
here
it
it
takes
in.
You
know,
get
you
tools,
dot
resolve
get
tool
so,
based
on
this
parameter
that
is
default.
I
get
the
default.
You
know
get
tool
on
the
jenkins
controller,
but
now
here
I
only
want
to
get
you
know
a
cli
get
okay.
So
what
is
the
parameter?
I
need
to
pass
here
only
to
get
a
get
cli
like
see.
I
like
command,
get.
A
Command
yeah,
it's
a
good
question,
I'm
not
sure
if
there,
if
there
is
a
way
from
here
to
to
say,
please
give
me
command
line
git,
because
because
this
thing
good
observation
on
your
part,
this
thing
says:
ask
the
jenkins
controller
for
its
default.
Git
implementation
and
the
default
git
implementation
could
be
configured
to
be
jgid,
yeah
yeah.
We
have.
We
have
ci.jenkins.io,
for
instance,
that
I
believe
is
configured
exactly
that
way
where
it's
intentionally
using
jgit
rather
than
command
line
get.
So
so,
let's
see
what
we
get
okay.
So
how
would
we
well?
A
Oh,
that's
terrifying
because
cli
get
api.
Implementation
is
a
public
class,
it
can
be
used
and
that's
what
it's
doing
here
so
it's
taking
in
this
case.
It's
trusting
that
the
get
client
can
be
cast
in
this
case
safely
to
a
cli,
get
api
implementation,
and
I
assume
there
must
be
something
else
elsewhere
here
that
guarantees
that
that
that
works.
I
have
no
idea.
I
haven't
looked
at
the
code
recently
to
see
how
it
does
that,
but
but
this
thing
is
being
converted
to
a
command
line.
B
A
Okay,
all
right,
so
then
this
so
this
would
at
least
if
you,
if
you
can,
if
the
logic
you
need
to
express
in
your
version
check,
can
be
expressed
as
an
is
it
at
least
this
version.
Then
you,
you
could
probably
use
this
technique
so
long
as
you
can.
You
can
be
assured
and-
and
you
could
certainly
do
a
a
right-
you
could
do
a
let's
put
it
in
here.
B
A
A
There.
We
go
okay.
B
But
in
my
thing
I
will
I
would
like
I
am
constructing
the
get
client
you
know
or
the
get
client
here,
whatever
the
type.
Okay.
So
can
I
directly,
you
know,
convert
it
to
a
see.
I
select
api.
A
A
If
the
controller
is
configured
to
have
j
git
as
its
default
implementation
and
has
no
other
implementation
of
git,
we
can't
run
maintenance
right
because
we
we
we're
blocked
so
so
I
would
think
what
that
means.
Is
you
want
to
ask
for
default
and
if
default
is
not
an
instance
of
cli
get,
then
we
can't
run
maintenance.
B
Okay,
but
then
on,
if
an
administrator
you
know
wants
to
set
jake
as
his
default,
but
you
know
and
still
has
cli
get
on
his
machine.
Then
what
we.
A
B
A
So
what
what
node
agnostic
is
trying
to
say
is
list
list
me
a
git
tool,
that's
available
when
I
don't
know
which
node
I'll
be
on,
but
you
know
which
node
you'll
be
on,
because
you
want
to
execute
on
so
here.
It
says
when
you
know
the
node
you're
going
to
be
on
and
you
do
because
you
want
to
be
running
on
built-in.
A
You
want
to
be
running
on
the
central
controller,
nowhere
else
yeah,
and
so
in
that
case
it's
saying,
hey
you
want
to
use
this
thing
and
as
the
node
value
you
want
to
get
the
default,
the
built-in
node
and
there's
a
there's,
a
method
on
the
jenkins
object.
That
will
tell
you,
give
you
a
node
for
the
built-in
node.
B
Because
I've
seen
in
the
ui
you
can
set
various
kinds
of
you
know,
get
versions
also
see
I
like
get
versions
like
a
2.3
version
at
2.1
version
2.
You
know
1.8
version
so
now,
which
version
do
I
use
internally
to
run.
B
In
this
case,
if
any
administrator
uses
a
default
implementation
as
jgit,
he
can't
they
can't
run
maintenance
tasks
right.
A
That
that's
what
let's
yeah,
that
I
think
I
would
take
that
as
a
safe
assumption
for
now,
because
we
we
really
cannot
do
maintenance
with
jgid
and
if
they're
going
to
choose
to
use
jgit
as
their
default
implementation,
and
we
we,
the
git
plugin
documentation,
tells
them
that
the
canonical
the
the
reference
implementation
for
the
git
plugin
is
command
line.
Git
jgit
has
known
limitations.
They
are
welcome
to
use
it,
but
it
has
known
limitations
if
they
use
it.
They
choose
to
accept
those
limitations
compared
to
command
line.
Git.
B
A
Right,
you're
you're,
not,
I
cannot
the
message.
The
message
really
is:
I
cannot
run
maintenance
with
jacob
and
and
realistically
we
can't.
I
don't.
I
think,
even
though
jgid
implements
garbage
collection,
I'm
not
ready
to
take
the
risk
of
relying
on
their
garbage
collection
implementation,
given
that
they
haven't
done
the
rest
of
the
maintenance
tasks
I'd
much.
Rather,
we
just
use
command
line,
get
for
all
of
it.
B
A
I
would
yes,
I
think
that
makes
sense
just
if
someone,
if
someone
attempts
to
perform
a
maintenance
operation
using
jgit,
just
say
unsupported
and-
and
I
would
do
it
by
logging
rather
than
I
think
it's
better
to
do
it
by
logging
than
by
then
by
throwing
an
exception.
But
if
you
look
in
the
git
client,
plugin
you'll
see
both
both
techniques
used.
A
If
you
attempt
to
do
a
sparse
checkout
with
jgit,
it
will
tell
you
sorry:
jegit,
doesn't
the
j
get
implementation
in
jenkins?
Does
not
support
sparse
checkout
or
here's
a
I
think,
a
more
friendly
way
to
do
it.
So
this
one
throws
an
exception
and
that's
that's
not
very
friendly
to
the
user,
but
it
makes
sure
they
know
you
ask
for
something
that
can't
be
done.
This
one
is,
I
think,
more
friendly
to
the
user.
It
says
you
asked
for
large
file
support,
but
our
jget
implementation
does
not
support
large
file.
Support.
B
B
A
A
A
B
A
A
B
Yes,
okay,
so
I
yeah
there's
nothing
like
I,
I'm
not
getting
anything
like
a
task
listener
from
any
class
which
I
am
using.
So
I
have
nothing
like.
I
don't
have
a
task
listener,
but,
however,
I
have
to
pass
a
task
listener
to
the
get
you
know
cli,
you
know
cli
command
line
get
so
I
for
now.
I
you
know,
pass
your
empty
task
or
null
task.
A
So
so
you've
got
a
task
listener
you've.
So
the
the
get
client
takes
task
listeners
right
and
it
will
log
to
that
task
listener
and
you
might
want
to
pass
in
a
task
listener
that
will
let
you
optionally,
write
the
results
to
the
system
log
so
that
you
can
see
it
because
you
don't
really
have
a
concept
of
a
task
yet
at
least
and
and
so
but
writing
the
information
that
the
get
client
would
be
logging
to
the
system.
Log
may
be
helpful.
A
A
That
was
the
idea,
at
least
that
I
had
you.
You
probably
want
to
check
it
to
be
sure.
Hey
does
it
behave
that
way,
but
I
think
that's
it's
worth
trying
that,
because
having
this
kind
of
message
appear
in
your
system,
log
for
a
maintenance
task
could
be
very
helpful.
It
could
be
quite
quite
a
good
diagnostic
to
have
to
say
oops.
There
was
a
problem
here
somehow
or
other
jet
was.
An
attempt
was
made
to
call
jgit
during
during
a
maintenance
task,
and
then
the
question
is
why
okay.
B
B
Oh
and
then
there's
another
okay.
These
were
the
major
questions
for
this
week.
One
more
thing
I
had
a
doubter
now,
if
I
build
a
project
right,
it's
running
all
the
test
cases
successfully
on
my
computer,
but
on
the
you
know,
on
github,
the
tests
are
failing,
there's
one
test
which
is
failing
in
particular.
A
A
A
A
A
B
A
A
Right
which,
which
means
that
means
you've,
really
got
to
put
debugging
print
statements
and
let
it
run
on
ci
to
see
if
you
can
identify
what's
different
between
your
environment
and
ci.jenkins.io,
because
you're
right
it
should
fail
on
your
computer
as
well.
I
mean,
if
there's
a
if,
there's
a
real
failure.
It
shouldn't
be
somehow
tied
to
ci.jenkins.io,
and
it's
certainly
passing
for
me
on
all
three
all
three
java
versions.
A
A
A
B
And
the
17
one,
the
java
17.
oh
good,
question
very
good.
A
A
B
B
Okay,
so
I
have
to
add
options
all
top
change
statements
and
push.
A
B
B
Oops,
okay,
oh
here
I
wanted
to
use.
Can
you
scroll
a
bit.
B
Okay,
not
the
task
executed.
Oh,
it
was
so
sorry
get
maintenance
scm.
I
guess
I
named
it
like
that
noise
yeah
in
this
one,
so
the
I
added
that
yeah
in
this
only
the
test
is
failing.
Okay,
I
added
the
logic
to
run
this
okay.
Then,
oh,
I
go
down.
Okay.
If
you
go
to
the
next
test.
Okay,
oh
I
want
yeah.
I
commented
this
because
it's
throwing
errors-
oh
it's
like
the
tests
are
failing.
B
So
here
I
wanted
to
test
whether
there
are
no
caches
present
on
the
jenkins
controller
and
you
know
verify
whether
this
thing
get
returns,
no
caches,
but
in
the
previous
method,
the
previous
test,
already
caches
were
being
made.
Okay
like
created
so
now
in
this.
Whenever
I
try
to
run
this,
it
throws
an
error
because
already
there
are
caches
run
present
on
the
no.
A
B
A
A
Public
void
erase.
A
B
Okay.
Okay,
so
I
I
I
look
into
this
I'll.
Add
this
thing
so
that
you
know
these
tests
also
start.
You
know,
you
know
are
finished
so
now
I
have
the
you
know
on
so
now
this
week,
I'll
have
to
be
working
on
legacy,
get
maintenance
okay.
But
for
that
I
would
be
needing
the
versions
of
you
know
the
you
know
and
which
version
I
even
sent
a
mail
to
the
you
know
office
to
the
get
in
the
get
detail
of
for
forms.
B
Okay,
and
then
they
have
given
a
response
which
was
very
complicated.
Okay,
they
were
like
go
to
the
get
cli
use
some
command
to
find,
in
which
version
it
has
been
released
and
all
so
I
I
I
couldn't
follow
with
that.
So.
A
B
A
A
A
A
Then
there's
an
additional
argument:
you
add
to
the
command
line
here,
which,
which
is
the
thing
that
creates
a
tunnel,
and
now
I've
got
to
look
it
up
to
see
what
the
command
line
argument
is
to
create
a
tunnel
and
I'll.
I
would
include
that
in
my
email
to
you,
so
it's
ssh
tunnel,
oops
nope,
define
a
tunnel
with
ssh.
A
A
A
A
A
A
A
A
A
A
A
A
A
B
A
A
A
A
A
B
In
the
guitar
channel,
all
right-
and
finally,
I
think
I'm
taking
a
lot
of
time
of
yours.
So
that's
what
it
is
now
I've
written
the
code
for
the
kit
maintenance.
How
do
we
know
like
it's
it's
properly
working
and
all
like?
Do
we
test
it
like
run
it
on
some
caches?
Whichever
are
present
so
that
you
know
we
can
know
whether
everything
is
going.
B
B
B
A
I'm
delighted
that
you're
asking
questions
for
your
guests.
This
is
wonderful.
Thank
you
for
the
progress
you're,
making.
Let's
keep
going
and
and
we'll
check
in
if
you
need
this.
This
coming
weekend
is
a
holiday
weekend
here
in
the
united
states,
it's
a
public
holiday,
and
so
I
will
I'm
less
likely
to
be
available,
particularly
because
my
grandchildren
will
be
in
town
they'll
be
visiting
here
from
texas,
and
so
so
I,
if
you
need
help
reach
out
to
rishabh
and
see
if
reshop
can
assist,
if
neither
rishob
nor
I
are
available.