►
From YouTube: 2022 05 24 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
A
A
A
Excellent
well
and
and
we're
delighted,
that's
great
and-
and
I
can
I
can
vouch
for
rashab
as
a
mentor
he
mentored
last
year
and
was
was
exceptional,
so
we're
going
to
have
a
lot
of
fun
together.
I'm
sure
of
it
and
and
we'll
look
forward
to
that.
You
are
each
welcome
to
make
edits
to
this
document
as
we
go
through
it
by
the
way.
A
We
want
to
be
sure
that
you're
comfortable
with
us
as
mentors
comfortable
with
how
we
do
code
review
rashab
reminded
me
last
year
that
we
need
to
be
sure,
you're
comfortable
with
test
driven
development,
because
even
if
I
don't
tell
you
about
it,
I'm
going
to
demand
that
you
practice
it,
and
so
it's
much
more
fair.
If
we
tell
you
about
it
first
before
we
demand
that
you
practice
it
and.
A
A
A
Maybe
it's
a
stub
method
that
does
nothing
and
your
test
asserts
that
it
should
do
something,
and
your
test
therefore
starts
failing
this
right
and
and
the
best
way
to
get
good
at
this
is
to
practice
right.
It's
no
one
expects
that,
and-
and
I
have
to
admit
that
the
jenkins
code
base
is
frequently
not
well
suited
to
this
methodology,
and-
and
I
wish
I
could
say
differently
rishikesh,
but
I
can't
rashab
has
lived
the
experience
of
oh
my.
A
C
I
think
there
are
two
things
to
say
about
test-driven
development.
First
is
that,
while
you
try
to
figure
out
how
to
fail
a
test
or
how
to
write
a
successful
unit
test
case
for
any
type
of
code
that
you're
going
to
write,
you
understand,
or
you
realize
edge
cases
that
you
might
not
have
thought
about.
C
So
I
I
would
say
just
thinking
about
the
code
would
never
give
you
the
edge
cases.
You
have
to
write
the
test.
You
have
to
write
a
test
case
in
order
to
be
able
to
realize
that
there
might
be
issues
that
you
may
miss,
while
you're
just
thinking
about
it
mentally.
So
that
is
the
first
thing.
Second,
is
that
what
I
realized?
C
What
was
why,
when
I
entered
into
the
development
cycle
of
this
particular
plugin,
was
that
your
feature
submission
to
production
that
is
to
release
to
the
audience,
is
not
just
you
designing
the
feature
and
then
ultimately
merging
your
pr?
It's
it's
going
to
be
thinking
about
a
lot
of
tests
which
are
going
to
validate
whatever
scenarios
that
you've
thought
about.
C
You've
discussed
with
us,
essentially
whatever
expectations
that
you
have
and
your
mentors
would
have
and
would
verify
those
have
to
be
codified
a
you
know
in
the
form
of
a
test
case,
so
that
it
is
a
it
is
a
real
proof
of
what
what
are
the
scenarios
that
we
have
thought
about,
and
we
are
sure
that
would
not
create
an
issue
when
we
release
this
particular
piece
of
code.
So
it.
C
Great
and
different
learning
experience
for
me
in
that
sense,
because
I,
in
my
personal
experience
at
that
time,
had
not
worked
extensively
in
this
with
this
methodology.
C
A
A
A
So
it
made
things
particularly
interesting.
Well,
in
your
project,
rishikesh
you're,
going
to
change
behavior
right,
we
are
going
to
be
doing
cash
maintenance
and
that
behavior
change.
They
will
want
that.
It's
almost
invisible
to
them.
They
want
they
don't
want
to
know
that
they
just
want
to
get
value
from
it.
A
We
need
the
the
added
confidence
that
it
is
doing
what
we
expect,
the
other
I
guess
another
benefit
of
tess
is
that
tests
help
us
check
multiple
platforms,
windows,
linux,
bsd,
mac,
os,
etc,
and
multiple
get
command
line,
get
versions,
and
this
one
is
the
you've
already
been
experiencing
this
one
right
in
your
in
your
developing.
Every
documentation
of
your
plan.
It's
like
oh
get
1.8
is
a
very
different
get
than
get
2.35
right.
They
have,
they
have
completely
different
characteristics,
and
yet
both
of
them
are
very
important
in
the
jenkins
installed
base.
A
B
No,
no,
I
I've
got
an
idea.
Okay,
so
I'll
look
into
it
once
again,.
A
Great
all
right,
okay,
so
then,
then
I
think
now
we
will.
We
will
need
you
to
be
confident
sharing
updates
during
office
hours
because
periodically
we
want
you
to
shoot
to
check
in
with
the
office
hours
and
say:
hey
project
is
going
okay
or
oh.
No.
I've
got
this
problem,
I
need
this
help
and
office
hours
is
not
really
the
place
for
for
technical
problems
with
your
specific
project
that
rishabh
and
I
will
do
with
you
in
our
in
our
own
team
meetings.
A
A
B
A
Maybe
this
is
one
that
it
would
be
healthiest
if
I
did
it
and
fushakesh
you
and
rashad
were
reviewers
of
it,
because
that
may
allow
us
to
to
have
another
voice.
You
wrote
the
original
draft
of
the
project
plan
right
fushakesh
and
because
of
that
you
know
it
best,
but
if
I
describe
the
project
details
in
a
pull
request,
that
gives
you
a
chance
to
say
no
mark.
You
misunderstood
something.
The
document
says
this.
A
A
We
can,
although,
given
how
low
volume
the
get
the
get
channel
is
already,
I
would
be
prone
to
just
use
the
get
plug-ins
channel.
Let's
that's
a
good,
that's
a
good
question.
Let
me
see
if
I
can
find
it,
I'm
not
even
sure
it's!
Oh
yes!
Here
it
is
okay,
so
good
question
and
let's
put
it
into
our
notes:
where
do
we
talk
to
each
other,
and
I
think
I
would
suggest
is
the
previously
used
channel
now
rishabh?
C
B
C
A
A
How
would
you
say
it
a
a
more
permanent
channel
and
I'm
not
sure
if
we
need
it,
but
I
would
prefer
on
the
more
permanent
channel
to
be
something
on
community.jenkins.io,
but
I'm
not
sure
yet
what
cases
we
might
need
that
for
maybe
for
hroshikesh's
status
reports.
If
we
want
a
periodic
status
report,
those
would
probably
best
be
done
on
community.
So
on
community.jenkins.io.
A
A
C
I
just
I
wanted
to
ask
mark
at
community.jenkins
today
it's
a
thread
based
communication
platform
right,
you
write
threads
and
you
post
something,
and
then
you
write,
you
have
threads
where
people
are
communicating,
it's
not
a
conversation
based
platform
right
or
am.
I
have.
I
not
explored
that
yet.
A
B
A
B
C
A
C
C
A
But
that
will
happen
that
will
happen
later.
Not
that's
not
a
that's,
not
a
a
systematic.
Do
it
every
time
right,
I
think
you
had
to
do
three
blog
posts.
I
was
just
looking
at
your
blog
posts
actually
and
khrushchev
will
need
to
do
three
blog
posts
to
jenkins.io,
so
he
will
have
the
experience,
but
I
think
we
can
be
more
effective
if
we
use
community.jenkins.io
even
for
draft
blog
posts
say
you
know
those
kinds
of
things:
it's
hey.
I've
got
this
new
thing.
A
A
B
Like
or
related
to,
the
git
maintenance
do
I
have
to
write
that
like
how
did
I
proceed.
A
A
A
A
We
need
to
be
sure
we
discuss
how
we're
going
to
divide
time
over
the
next
10
weeks,
break
breaks
and
vacation,
but
that's
later
in
today's
agenda,
refine
rid
of
the
project
plan
with
deadlines
and
milestones.
I
think
that's
also
later
in
the
deadlines
or
later
in
the
agenda.
A
A
Great
okay,
all
right,
so
I
think
we've
been
through
the
checklist
then
now
the
next
piece
then
I
had
on
the
list
was
the
plan
for
presentations,
and
this
is
this
is
rishabh
can
tell
you
really
about
it?
It's
we've.
We
like
to
have
a
phase
one
presentation
for
the
about
halfway
through
the
project
that
highlights
accomplishments.
C
A
A
A
C
A
So
welcome
to
community
bonding
we've
got
until
june
12th
to
do
preparatory
things
and
then
june
13
coding
phase,
one
starts
coding,
phase
one
ends
and
then
phase
two
starts
july.
25
then
september
5
is
the
final
week
for
submission
of
final
work
and
evaluation
and
rashav,
and
I
submit
final
evaluations
by
september
19th.
A
A
C
A
A
A
Okay,
so
so
the
for
me,
it
would
be.
I
think
it's
easier
for
me
if
I
do
8
30
a.m
and
that
would
need
to
be
monday,
tuesday
or
friday
for
mark,
if
not,
that
so
8
30
a.m,
monday,
tuesday
or
friday.
Let's
see
wait
a
sec.
I've
got
to
check
okay.
What
what
day
of
the
week
is
it
for
you
in
your
time
zone
today.
A
Is
tuesday
for
you,
okay,
and
so
today
is
so.
We
are
on
the
same
day
right
now,
but
when
we
switch
to
8
30
a.m,
we're
offset
by
one
day
so
for
me
yeah,
so
for
me
it
would
be
8
30
a.m,
tuesday,
wednesday
or
friday
is
horrible,
because
that's
yeah,
okay,
wednesday,
tuesday,
wednesday
or
yeah
skip
thursday
thursday,
thursday
evening
your
thursday
morning.
A
Your
time,
I
have
a
personal
appointment
that
I
cannot
break,
and
so
I'm
I'm
unavailable
thursday
morning
your
time,
but
I
could
be
available
friday,
tuesday,
wednesday
or
friday,
and
if
we
had
to,
I
could
be
available
monday
monday.
But
I
sort
of
like
to
leave
your
monday
morning
available
for
personal
time,
because
it's
the
end
of
my
weekend.
C
A
A
A
C
A
C
So
you
do
that
in
one
layer,
one
minute
without
stopping
yeah.
A
C
A
Not
talk
about
that,
let's
talk
about
not
talk
about
the
number
there.
The
number
is
a
bad
thing
to
discuss,
I'm
not
I'm
not
25
anymore.
I
haven't
been
25
for
a
very
long
time,
all
right
so
wednesday,
8
30
ist,
and
I
propose
we
already
do
it
this
week.
So
it
means
we'll
meet
tomorrow
just
to
test
and
we'll
make
sure
that
whatever
topics
we've
got
to
discuss,
we
discuss
them
and
then
each
week
we
meet
now
then
we
need
to
talk
about.
Is
that?
Okay?
For
the
two
of
you.
A
All
right,
okay,
so
then
outages
so
the
time
off,
and
this
is
where
we've
got
an
awkward
one,
I'm
planning
to
be
out
next
week,
but
I
could
attend
the
the
8
30
a.m.
Wednesday,
if
you
don't
mind
that
I'm
dialing
in
from
another
location
and
that
I'll
be
using
my
chromebook,
so
my
sound
may
not
be
great,
etc,
etc.
C
A
C
A
C
A
So
rishabh
host
hosts
the
meeting
next
week,
good
excellent,
okay,
then
then
I
will,
I
will
plan
to
not
attend
and
just
let
the
two
of
you
meet.
If
that's
okay,
great
all
right
the
next
week,
I
think
I
can
meet
because
we're
choosing
to
meet
at
a
time
that
would
work.
A
B
A
Right,
okay,
now
now
I
think
you
can
easily
still
fit
in
the
175
hours
expected
with
this
time
off.
That's
not
a
problem
just
just
be
aware
of
it
that
175
hours
is
roughly
20
hours
a
week
for
the
12
weeks
and
and
that
I
think
well,
if,
if
it's
a
problem
for
you,
please
let
us
know,
but
as
far
as
I
can
tell
it
worked
great
for
rashad,
it
worked
great
last
year
with
our
our
our
participant,
then
so
I
don't
see
any
problem
with
that.
C
These
well,
these
are
the
pull
requests
that
were.
This
was
before
submitting
the
proposal
correct.
B
A
Right
so
so
these
are.
These
are
the
evidence
that
russia
knows
how
to
do
a
poll
request
and
knows
how
to
interact
with
others
in
the
community
and
they
they
are
very
good
evidence
now
there's
there
are
some
complications
on
this
one,
because
frustration
chose
to
do
some
renaming
and
it's
it's
a
little
more
difficult
for
me
to
do
the
code
review
because
of
the
renaming.
A
But
the
reality
is
that's
a
perfectly
fine
choice.
What
he
did
made
the
code
actually
look
much
more
like
java
tests
than
it
did
before.
So
it's
a
nice
improvement.
It
just
means
the
code
review
is
a
little
more
challenging.
I
think
the
answer
here
is
this.
One
is
actually
a
fairly
easy
merge,
a
more
challenging
code
review,
because
I
don't.
I
want
to
be
sure
that
we
didn't
lose
any
test
methods.
A
Right
so,
and,
and
truthfully,
this
is
not
this
one
is
not
the
focus
of
our
project,
so
if
it
never
completed,
that
would
still
be
okay
right.
It's
you,
you
gained
experience
from
doing
it.
The
experience
is
beneficial,
but
if
this
one
I
want
to
complete
just
because
I
very
much
want
it
this
one
I'm
less
worried
about,
and
this
one
I'm
not
worried
about
at
all,
they
they.
Yes,
we
would
like
to
get
that
one
in
but
being
a
breaking.
A
C
So
then
I
I
think
we
don't
need
to
discuss
setting
up
the
local
development
setup
for
working
with
the
git
plug-in,
because
that
rishikesh
would
have
already
done
as
he
was
working
with
the
vrs.
B
A
A
A
A
About
the
problems
encountered,
the
techniques
used,
etc,
because
I'm
worried
about
this
okay,
everything
I've
done,
thinks
about
a
job
and
has
a
workspace
right
and
and
does
has
all
sorts
of
infrastructure
that
the
get
plug-in
where
they
get
plug-in
lives.
But
this
automated
cash
maintenance
really
shouldn't
be
done
with
jobs,
because
we
tell
people
quite
rigorously.
You
must
not
run
jobs
on
the
controller
and
therefore,
we've
got
to
have
some
other
method,
and
my
thought
was
this
is
one
that's
worth
exploring
to
be
sure.
A
We
understand
and-
and
you
may
ultimately
end
up
with
an
architecture
and
class
diagram
that
describes
it
because
you
need
to
know
which
classes
do
you
inherit
from,
but
the
the
key
question
is
not:
what's
the
class
diagram
it's?
How
do
we
do
this
lightweight
process
on
the
jenkins
controller
and
do
it
well.
A
A
So
when
I
say
job
I
mean
something
like
this
thing
right
here,
this
one
master.
This
has
a
series
of
executions
that
are
run
that
I
will
use
the
term
build
to
describe
those
it's
represented
in
this
build
history,
and
this
thing
at
the
top
called
the
branch
master
is
a
job,
and
then
this
job
is
where
I
do
almost
all
work
on
my
jenkins
controllers.
In
one
of
these
jobs-
and
I
have
thousands
of
these
ins
configured.
B
A
B
A
Can't
even
absolutely
I
run
this
particular
job
runs
the
maven
program.
I've
got
other
jobs
like
let's
see
this
one
that
runs
ant.
I've
got
this
one
that
runs
a
shell
script.
A
C
So
mark
I
had
a
question
so
when
you
say
that
this
lightweight
process-
I
what
I
wanted
to
understand
about
that-
is
that
we
is
in
a
jenkins
ecosystem.
Do
we
have
an
extensible?
Do
we
have
a
way
a
hook
or
anything
that
I
can?
I
could
extend
to
and
create
my
own
processes
apart
from
a
job
like
a
guest.
A
A
A
Exactly-
and
that
was
the
thing
I
was
thinking
of-
is
okay:
we've
got
somebody
who
has
created
code
that
we
could
review
to
see
how
they
did
it
and
we
might,
even
after
reviewing
the
code
that
see
how
they
did
it.
We
might
ask
them.
Please
come
tell
us
some
of
the
things
you
learned
by
hard
experience
so
that
we
don't
have
to
learn
the
by
heart
experience.
A
A
We
need
something
that
is
independent
of
any
build,
but
that
we
can
control
that
russia's
code
will
control
and
say
I
want
it
to
run
roughly
weekly
or
roughly
daily
or
roughly
hourly
that
that
kind
of
thing,
but
but
russia's
code
will
then
have
to
have
to
do
things
like
roughly
hourly,
but
don't
overload
the
controller
roughly
roughly
weekly,
but
don't
saturate
on
exactly
midnight
on
sunday
morning.
Something
like
that.
A
That
that
was
done,
yeah-
that
was
my
thinking
here-
was
use
this,
as
as
an
example.
Now
it
does,
it
does
something
wildly
different
than
what
we
need
right.
It
iterates
over
every
job
and
we
don't
need
to
do
that.
We
will
iterate
over
each
cache
and
decide
to
do
some
things.
So
so
it's
it's,
but
but
the
concept
is
it's
scheduling,
work
and
doing
the
work
without
actually
using
a
jenkins
job
to
do
the
work.
C
So
I
I
was
under
the
impression
till
now
that
we
would
use
the
existing
ui
infrastructure
that
we
have
for
a
job,
and
that
is
somehow
where
there
we
would
add
another
option
where
a
user
could
check
the
maintenance
tasks
or
whatever
is
happening,
but
with
this
a
separate
process
that
I
see
listed
here,
I
don't
know.
If
this
is,
can
I
use
the
existing
ui
infrastructure
that
I
have
which
the
user
sees
on
the
jenkins
homepage
or
at
the
settings
level?
Can
I
use
that
or
would
I
have
to
create
separate
views
here?
C
A
Well,
that's,
that's
actually,
a
it's
a
good,
a
good
question,
because
we
may
need
to
bring
it
up
tomorrow
to
get
further
on
it,
because
what
build
what
global
build
discarder
is
doing.
Is
it
uses
the
configuration
inside
the
job
to
define
what
it
should
do,
so
it
does
in
fact
look
at
the
job
pages
configuration
to
decide.
A
B
Around
100
repositories,
very
big
repositories
will
this
you
know
build
whatever
yeah
you
have
stated:
will
that
automatically
decide
which
will
which
cash
it
has
to
take
in
which
it
should
you
know
discard
so
that
it,
you
know,
doesn't
overload
the
system.
A
A
So
we
could.
We
could
cheat
and
use
that
information.
Oh,
it
shows
up
that.
It's
mostly
idle
for
this
one
hour
window
every
day,
or
it's
mostly
idle
for
this
four
hour
window
on
weekends,
those
kinds
of
things
and-
and
my
hope
was
they
might
be
able
to
tell
us
hey.
We
did
it
this
way
or
they
may
say,
mark
you're
crazy.
We
did
no
such
thing,
you
just
set
it
up
to
run
and
let
the
administrator
handle
it.
C
That
would
be,
I
think,
much
more
smarter
way
of
doing
it
rather
than
exposing
a
schedule
for
it,
because
this
in
this
way
we
are
doing
the
operations
very
intelligently
right,
we're
understanding
what
the
existing
state
of
the
system
is
and
then
figuring
out
when
we
should
run
the
maintenance
operations
as
compared
to
an
administrator
would
have
to
then
think
the
same,
and
not
maybe
not.
Everyone
is
thinking
about
this.
A
It
should
be
safe
in
the
sense
that
we
intend
to
do
no,
no
destructive
change
to
that
repository.
It's
it's
cash.
It's
g!
It's
garbage
collection
right!
It's
fetching
without
updating
the
local
references,
it's
those
kinds
of
things
that
are
that
should
be
harmless
and
therefore
they're
not
going
to
see
it
as
negative.