►
From YouTube: 2022 08 12 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
Okay,
welcome
it's
the
12th
of
august
2022.
This
is
google
summer
of
code,
automated
cash
cash
maintenance
for
the
gets
plugin
rishikesh.
What
questions
do
you
have.
B
Oh,
I
had
questions
regarding
you
know.
Storing
the
files
like
we
discussed
it
before,
like
you
know,
like
we
spoke
about
the
metrics
plug-in
okay
on
how
we
would
store
files.
You
know
regarding
the
kit,
maintenance,
caches
yo,
and
how
would
we
then
display
it
back?
I
went
through
the
metrics
plug-in,
but
I
didn't
find
any
way
of
how
they
are
storing
it.
So
would
you
help
me
with
that.
A
And
I'm
not
I'm
not
sure
I
I
can
give
great
help
for
it.
But
let's,
let's
look
together
and
see
what
we
can
find.
I
may
have
to
take
an
action
item
to
go.
Do
some
research
to
see
so
so
the
kinds
of
data
that
you're
trying
to
store
what
you're
trying
to
store
is
a
record
of
when
the
maintenance
was
run,
how
long
it
was
run
or
what
tell
me
more
about
what
information
you're
trying
to
store.
B
Oh,
what
what
maintenance
task
was
run
when
was
it
run?
How
much
time
did
it
take?
Did
it
succeed
or
fail,
and
when
was
it
last
run?
You
know
if
that
was
needed,
so
yeah.
A
Okay,
so
so
what
what
we
need
is,
and
the
idea
is
we,
the
user
will
be
able
to
click
something
from
the
ui
that
tells
that
will
show
them
a
table
of
results
where
hey
the
last
maintenance
tasks
this
this
task
was
performed.
It
was
working
on
this
cache.
It
took
this
long.
It
ran
at
this
time
that
sort
of
thing.
B
Yeah
in
a
table
of
ten
entries-
and
then
you
have
this-
you
know
page
origination.
A
A
All
right,
so
so
what
we're
thinking?
Well
so,
okay,
so
so,
let's
consider
what
are
some
alternatives?
One
might
be
if
we
wanted
to
use
a
presentation
like
what
what
if
we
wanted
to
use
a
presentation
like
the
way
we
present
warnings-
let's,
let's,
let's
grab
one
here
from
that.
So
in
the
in
this
thing,
probably
here,
oh,
I
know
I
can
even
look.
Let's
do
one
better.
A
Let's
look
on
see
a
place
where
you
can
see
it
without
without
having
to
get
access
to
my
machine,
let's
go
to
ci.jenkins.io
and
let's
look
at
the
platform,
labeler
plug-in
or
even
better.
Let's
look
at
the
get
plug-in
and
on
this
one,
what
we
see
are
some.
There
are
some
historical
records
here
right
like
test
results,
code
coverage,
results
and
tabular
results
of
those
things.
A
For
instance,
we
might
want
to
look
at
the
coverage
report
now
this
this
may
be
more
date,
more
a
different
kind
of
data,
because
what
what
I
think
we
you
need
to
see
is
something
that's
sort
of
tabular
like
this.
One
is
where
it
says:
here's
a
table
of
types
of
warnings;
okay,
they
wouldn't
be
warnings
in
our
case,
but
the
type
the
total,
the
new
and
the
distribution
right,
yeah,
okay
and
so
and
then
then
they
may
want
to
click
through
and
see
something
that
tells
them
something
more
and
so
this
this
does.
B
B
A
A
A
A
How
could
we
find
something
that
gives
us
historical
that
we
can
use
as
a
reference
like?
Oh,
oh,
like
build
history
right?
Would
that
that's
probably?
Yes,
that's
that's,
probably
very
similar
to
what
what
we
need
to
do
if
we
look
at
if
I
look
at
ci
on
the
git
plugin,
and
if
we
look
at
build
history,
this
one
right
here,
because
this
this
really
is
showing
the
kind
of
information
you're
describing
right,
it's
something
historical.
B
A
A
A
A
A
B
B
B
A
B
A
A
A
B
A
Job
named
client
pipeline,
and
there
is
one
and
two
right
and
each
of
those
contains
a
change
log.
A
j
unit
result
the
log
file
from
it
and
more.
A
Oh
yes,
this
is
this,
is
this:
is
the
get
forensics
plug-in
storing
its
data?
So
yes,
okay,
so
it
looks
like
these
things
are
storing
things
in
this
build.xml
file.
A
A
But
something
must
be:
writing
those
and
it's
not
a
job
right
and
then
what
others,
for
instance,
monitoring
and
monitoring.
I
think
you'd
already
done
the
looking
to
see,
but
monitoring
has
all
sorts
of
data
that
it's
storing
build
queue
length,
and
these
things
are
even
what
is
an
rrd
file.
I
thought
that
was
some
form
of
real
time
or
some
form
of
time.
Series
database.
A
A
So
a
circuit
here-
let's,
let's
bring
back
that
that
page.
So
what
a
when
a
time
series
database,
what
it's
doing
is
it's
tracking
history
over
time
right.
So
this
graph
shows
from
left
to
right
time
earlier
to
time
later
and
in
doing
that,
we
need
a
way
to
discard
the
oldest
things
and
retain
the
newest
things
and
these
time
series
databases
using
a
round
robin
archive.
A
A
Exactly
that's
that's
the
kind
of
thing
and-
and
I
wonder
maybe
we
want
something
like
that
here-
that
really
we
want
to
use
a
round
robin
thing
because
we
don't
want
to.
We
don't
want
to
accumulate
things
forever,
and
so
maybe
maybe
it
is
something
where,
but
again
that's
leading
us
that's
be
leading
us
back
to
the
monitoring
thing
as
a
way
to
okay.
How
would
we?
How
would
we
store
this?
B
B
Yeah,
surely
do
we
do
that
internally
or
is
this
rdd
rrd
thing
managed
by
us
or
is
that
how
would
that
work.
A
A
A
A
A
A
B
A
B
A
A
A
A
A
B
A
And
I
think
I
think
it
may
be
that
what
I
need
to
do
is
find
someone
who's
expert
in
that
and
ask
for
their
help,
because
I
think
it
makes
sense
that
that
we
should
we
should
use
a
similar
technique
or
at
least
consider
a
similar
technique
to
an
rrd
file
as
a
way
to
store
the
information
about
the
about.
The
cache
cleanup
runs
right
that
that
rd
file
seems
like
a
very
sensible
thing
to
say:
let's
not
keep
more
than
a
certain
number
of
these,
and
let's
rotate
them
automatically.
B
B
A
A
Okay,
no
mention
of
pagination
there.
What
would
is
there
another
word
that
might
be
used
to
describe
pagination.
A
B
A
A
A
A
B
B
If
I
have,
if
I
you
know,
get
to
know
those
at
least
I
can
build
a
basic
ui
and
then
you
know
research
on
how
do
I
store
the
data.
A
A
A
A
A
B
Yeah
again
next
week,
when
would
you
be
back
again.
A
A
Maybe
what
we
should
just
do
is
bring
this
to
the
developer
mailing
list
and
say
hey.
Let's,
let's
ask
the
question
there
look
marx
mark
doesn't
know
how
to
do
this,
help
us
and
and
and
let
people
say:
okay,
hey,
how
do
we
do
it
because
they
may
be
able
to
help
us
better
than
than
me
trying
to
find
a
specific
person
by
asking
the
question
more
generally,.
A
Well
well,
and
just
the
matter
of
of
people,
people
know
me
and
they're
willing
to
tell
me
mark
you've
asked
a
very
dumb
question:
just
do
this
and
be
done
with
it
right
and
and
that's
great,
whereas
for
you
they
may
have
to
be
much
more
gentle
and
say:
oh
well,
who
should
have
you
tried
this
and
tried
that
all
right,
so
davis,
storing
the
okay
here?
So
here
I
am
trying.
Can
you
see
my
screen?
Okay,
yeah,
yeah,
yeah,
okay,
so
storing
the
maintenance
data.
A
B
A
Great
all
right
so
so
here
we
go
we're
gonna,
post
off
we
go
now.
I
I
don't
promise
that
we'll
get
an
immediate
response,
but
if
we
don't
get
a
response,
we
can
certainly
ask
more
questions
or
you
can
reply
to
it
when
people
say
what
did
you
mean
by
this?
What
did
you
mean
by
that?
How
can
I
find
your
code
etc?.
B
B
Those
were
the
only
things
which
you
know
I
have
to
I
wanted
to
discuss.
There
are.
There
are
a
few
more
tests
which
I
have
to
write.
Oh
you
know
there
are
few
failing
tests
again,
one
two
I'll
I'll
fix
them.
That's
not
nothing
from
small,
failing
spot
bug,
issues
and
all
so
I'll
fix
those
and
a
few
parts
of
the
oh
yeah.
There
was
one
thing
regarding
the
hash:
hash
settle.
Okay,
we
are
adding
caches
into
the
hashtag,
but
whenever
we
delete
you
know
repository,
we
didn't
add
any
logic
to
delete.
B
Or
you
know
the
cache
from
the
hash
set.
The
the
caches
would
be
deleted
if
you
restart
the
jenkins,
you
know
software
completely,
because
we
are
using
a
static
hash
set.
Okay
and
the
static
initialization
block.
So
during
that
time
we
would
read
all
the
caches
and
then
assume
if
you
delete
anything,
there's
nothing
which
is
there's
no
way
of
deleting
it
from
the
hashtag.