►
From YouTube: GitLab: Package cleanup policies MVC
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
So
I'm
in
my
project
here
and
this
project
has
several
items
in
the
package
registry
and
when
you
publish
a
package
it
often
comes
with
a
series
of
files.
So,
for
example,
if
we
look
at
an
npm
package,
we
could
see
the
zip
file
here.
If
we
go
back
to
the
package
registry-
and
let's
say
we
look
at
a
conan
package,
we
can
see
that
there
are
several
files
included
with
that
as
well.
A
So
if
you
wanted
to
control
how
many
duplicate
of
these
assets,
you
keep,
you
simply
go
to
your
project,
settings
oops
to
packages
and
registries
and
there's
a
new
setting
here
called
manage
storage
used
by
package
assets.
So,
like
I
mentioned
when
you
upload
a
package,
it
uploads
assets,
these
are
just
files
or
binaries,
and
so
what
you
can
do
here
is
say
the
number
of
duplicate
assets
to
keep,
and
then
you
could
choose
a
maximum.
A
So
if
you
select,
let's
say
20,
it
means
that
any
duplicate
asset
we
will
keep
the
20
most
recent
and
delete
all
the
rest
of
them.
So
if
you
uploaded
a
pack,
a
maven
package
with
100
duplicates,
we
would
we
would
only
keep
the
20
most
recent
assets
and
the
package
itself
would
still
be
there.
So
you
just
hit
save,
and
it's
done,
the
cleanup
policy
will
run
within
the
next
24
hours.
This
can
help
you
to
reduce
storage
and
to
also
just
make
the
user
interface
a
little
bit
easier
to
use.