►
From YouTube: 2022 09 14 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
Recording
is
starting
welcome.
This
is
the
14th
of
September
at
2022,
get
cash
maintenance
project,
so
rushikesh
I
have
merged
the
changes
into
the
get
client
plug-in
and
hope
to
release
it
within
the
next
24
hours.
Okay,
congratulations
I'm,
not
as
confident
on
the
changes
in
the
git
plugin,
because
I
want
to
do
some
more
testing.
A
I
want
to
be
sure
that
we
get
the
help
in
ETC,
so
there
are
more
things
to
be
done
there,
but
I
wanted
to
get
the
get
client
plugin
out
there,
because
that
way,
we've
got
a
stable
base
for
it,
and
I've
got
a
way
to
deliver
jgit
5.15.1.
So
thank
you
very
much
and
we'll
continue
the
work
with
the
get
client
or
with
the
git
plugin
in
the
future.
So
thank
you
very
much
so.
B
That's
some
good
news
because
the
code
has
been
merged.
Yeah,
oh
I,
had
it
out
regarding
the
git
plugin.
Now,
how
are
we
going
to?
How
are
you
going
to
test
it
or
how
are
we
going
to
test
it?
Are
you
going
to
run
it
on
your
machine
to
check?
Is
it
executing,
as
expected,
or
yes,
okay,
yeah.
A
A
We've
got
to
be
sure
we
get
documentation
in
and
if
you're
available,
to
help
with
documentation,
great
but
I
think
your
first
priority
has
to
be
update
your
project
page
on
jenkins.io
and,
if
you're,
if
you're,
not
feeling
well
that,
maybe
all
you
do
is
update
that
project
page
so
that
you
can
get
it
it
completed
to
satisfy
the
requirements
of
Google
summer
of
code.
B
A
So
now,
in
terms
of
in
terms
of
I
I'm,
hoping
that
you're
you're
interested
in
continuing,
but
you
certainly
aren't
required
to
continue
to
work
with
with
a
with
me
on
it,
but
one
way
or
the
other.
What
you've
done
is
going
to
be
merged
and
we
will
arrive
at
shipping.
It
I
I'm,
not
sure
when,
yet
because
I've
got
some
travel,
that
I
have
to
do
later
this
month,
that
and
preparing
for
it.
B
Oh,
we
we
can
keep
working
on
this
thing.
If
you
know
activity
we,
you
know,
if
you
put
any
comment
on
that
pull
request
as
well.
I
would,
you
know,
see
an
update
and
do
any
changes
required
from
my
side
as
well.
So
great.
B
Oh
actually
it
for
we
had
College
the
entire
somewhere
like
for.
B
B
So
kind
of
used
to
it
went
over,
but
but
I
can
yeah,
you
know
I'll
keep
contributing.
That
is
from
my
side.
You
know,
try
and
finish
it
and
deliver
it
as
expected
without
any
issues
in
nobody.
Your
safe
state,
excellent.
B
Oh
and
how
this
I
updated
the
get
client
API,
you
know
to
return
a
Boolean
and
that
I
have
updated
as
changes
in
the
git
plugin
as
well.
So
now,
I
know
if
the
get
maintenance
is
being
executed
or
not
before
I
wasn't
sure,
but
now
in
the
late
plugin,
we
can
confirm
that
the
maintenance
has
been
executed
or
not
also
the
caches
size
here
now,
I'm
displaying
it
only
in
terms
of
MB
like
as
we
have
discussed,
okay,
so
that
has
become
easier
to
sort
as
well.
B
Okay,
now
I
I
couldn't
I
I
thought
I'll
work
on
you
know,
skipping
the
caches
for
repository
is
less
than
100
KP,
something
like
that.
But
then
I.
You
know
because
of
this
thing,
I
couldn't
work
on
it
right.
No,
no
problem,
I'll,
try
and
completely
by
this
weekend,
I'm,
not
an
issue.
B
Also,
there
are
I've
updated
the
help
files
like
added
the
text
from
my
side,
but
it
isn't
still
working
in
the
UI
two
three
maintenance
tasks
help
file
up
updated
so
that
also
I'll
finish
and
push
it
by
this
weekend,
so
that
you
know
it
would
be
completed
other
than
that
I
think
yeah
everything
looks
like
goes
going
as
expected.
A
A
B
Oh
I
was
thinking
of
for
adding
so
basically,
first
there's
a
project
abstract.
What
is
the
project?
You're
gonna
talk
about,
and
then
I
was
thinking
about.
You
know
the
deliverables,
what
exactly
was
required
by
me
and
then
one
architecture
diagram
and
then
what
I've
done
is
the
first
phase
and
then
it's
video,
the
YouTube
video
and
then
the
second
phase.
What
I've
worked
on
and
down
you
know
attach
links
to
the
client
plugin,
the
git
plugin.
That's
what
I
was
thinking
I.
A
Like
that
that
link
to
the
link
to
the
pull
requests
and
now
now
that
we've
got
if,
if
we're
lucky
so-
and
this
is
me
saying
if
we're
lucky,
but
if,
if
things
work
out
the
way,
I
hope
you
may
be
able
to
link
to
the
git
client,
plugins
release
note
or
the
changelog
for
3.12.0,
because
it
now
lists
the
automatic
get
cash
maintenance
API
or
it
will,
when
it's
released.
I
can
see
it
as
a
pre-release
and
when
I
release
it
and
if
we
finish
early
today,
I
may
be
able
to
release
it
immediately.
A
A
A
After
it
has
released,
so
it's
it's
broken
link
right
now,
so
don't
don't
be
dismayed
when
when
this
second
thing
is
not
resolvable
right
now,
because
that
I
can
I
or
even
I,
don't
see
it.
What
I
see
is
a
pre-release
of
that
in
my
in
the
queue
showing
the
correct
things,
so
it
it
will
be
at
that
location
once
it
is
released.
A
Like
no
no
I
I,
no
I,
it
should
happen
on
its
own.
That's
a
very
good
question
actually,
because
in
the
Jenkins
project
uses
continuous
delivery
for
many
plugins,
however,
I
am
behind
schedule
and
the
get
client
plugin
doesn't
use
continuous
delivery.
Yet,
okay,
so
so
in
a
in
a
perfect
world,
the
merge
of
your
changes
would
have
automatically
run
the
release
process
and
automatically
published
everything
and
for
a
number
of
plugins
for
several
other
plugins
I
maintained.