►
From YouTube: GitLab 12.9 Kickoff - Package
Description
Review features planned for milestone 12.9, which is scheduled for release on March 22nd, 2020
A
Okay,
the
first
few
items
here
are
all
related
to
optimizing
garbage
collection
for
the
--get
lab
container
registry
for
Google
Cloud
Storage.
We
recently
made
a
similar
optimization
for
s3
and
soar,
saw
orders
of
magnitude
improvement,
we're
hoping
to
see
the
same
types
of
changes
for
those
instances
using
Google
Cloud
Storage.
It's
broken
up
into
several
issues.
Basically,
the
garbage
collector
has
a
couple
of
different
stages.
It
has
the
mark
stage
which
is
responsible
for
identifying
images
and
blobs
that
can
be
deleted.
A
It
has
the
sweep
stage
which
actually
deletes
them
and
then,
of
course
it
because
we
need
to
test
this
and
understand
the
implications
and
know
that
this
will
work
at
scale.
There's
a
bunch
of
benchmarking
and
performance
tests
that
we'll
have
to
conduct
as
well.
This
is
all
part
of
the
epoch
to
improve
the
performance
of
the
algorithm.
You
could
check
out
this
epoch
or
you
could
check
out
the
individual
issues
for
more
details.
A
Okay,
a
couple
more
things
that
are
upcoming,
so
using
NPM
dot
org
as
a
default
remote
repository
for
pulling
the
package
when
it's
not
found
in
the
git
lab
NPM
registry.
So
what
is
this
so
we,
as
we've
launched
several
package
registries
like
the
NPM
registry
or
our
maven
repository.
We
allow
users
to
set
up
private
repositories
on
github,
but
what
happens
when
the
package?
Isn't
there?
A
lot
of
our
users
want
the
ability
to
say
okay.
If
the
package
is
not
hosted
on
github
then
go
out
and
look
in
this
other
remote
repository.
A
This
is
the
first
iteration,
and
what
we'll
be
doing
is
saying
that
you
could
pull
amid
pull
packages
from
NPM
org
when
it's
not
available
in
get
lab,
the
implementation
will
be
fairly
straightforward,
it'll
be
an
instance
level
setting
or
you
can
enable
forwarding
of
pack
request
to
NPM
j/s
org
if
this
works
and
people
like
this
feature
will
roll
this
out
for
other
package
managers
as
well.
So
we're
really
excited
to
get
this
get
this
out.
A
Okay!
What's
next
investigate
adding
pi
PI
pi
PI
support
to
the
package
registry,
so
in
12
in
12
eight
we
recently
just
launched
nougat.
We
found
it
really
helpful
before
implementing
any
new
new
package
registry
to
do
an
investigation
to
do
some
investigation
on
the
technical
side.
So
what
we've
done
here
is
identify.
What
are
the
different
use
cases
that
we
want
to
support?
In
this
case
we
want,
basically
users
can
use
their
get
lab
project
as
a
host
for
a
pi
PI
repository.
A
A
Obviously,
you
can
install
packages
using
pip
install
from
either
using
either
the
pip
client
or
using
get
lab
CI
CD,
and
you
could
upload
packages
using
twine
as
well
as
search
for
packages
using
pip
search,
and
this
will
come
with
a
UI
that
includes
metadata,
like
name
and
version
and
how
it
was
created,
and
this
after
this
in
twelve
ten
and
twelve
eleven
will
actually
work
on
the
implementation
of
an
MVC
for
this.
But
this
is
an
investigation
issue.
A
Okay,
couple
more
here
so
specifying
images
that
should
not
be
deleted
as
part
of
the
container
registry
bulk
delete
API
a
lot
of
talk
about
how
images
are
deleted.
We're
it's
a
big
thing
that
we're
working
on
right
now
is
we're
trying
to
improve
how
you
manage
storage
for
the
container
registry
as
part
of
a
goal
to
help
overall
lower
the
cost
of
storage.
So
we
have
a
bulk
delete,
API
that
allows
you
to
specify
which
tags
you
would
like
to
remove
and
when.
A
But
what
we've
heard
from
multiple
customers
is
the
ideally
want
the
ability
to
say.
Okay,
I
also
probably
have
a
release
image
or
a
master
image
and
I
never
want
to
delete
those,
and
so
they
want
to
add
some
protection
into
the
bulk
delete
API.
So
what
this
proposal
will
do
is
add
in
the
ability
to
protect
using
reg
expert
specify
which
image
names
you
would
like
to
never
delete.
A
Okay,
two
more,
the
next
one
is
a
big
part
of
the
user
interface,
where
you
are
adding
support
for
a
group
level.
Container
registry
browser
could
see.
Basically,
we
have
the
container
registry
UI.
Now
that
allows
you
to
see
images
in
this
case
we
can.
This
will
be
at
the
group
level.
You
can
see
a
list
of
your
doctor
repositories,
you
could
click
into
them
and
see
the
tags
that
are
associated
with
each
one.
You
can
delete
them.
A
You
can
both
multiple
select,
multiple
items
for
deletion
and
you
could
obviously
remove
one
at
a
time
as
well.
So
let
me
get
out
of
this,
so
this
will
be.
This
is
a
popular
feature
that
we
are
adding
support
for
in
12:9,
I'm
really
excited
to
see
this
launched
and
then
finally
being
able
to
utilize
the
git
lab
API
for
creating
revoked
and
revoking
project
and
group
deploy
tokens.
Sorry,
that
was
a
mouthful.
A
Basically,
what
we
want
to
do
is
create
an
API
that
will
allow
you
to
create
lists
and
edit
your
deploy
tokens
that
both
the
group
and
project
level.
So
this
will.
We
already
have
this
feature
for
that.
You
can
create
project
deploy
tokens.
What
we
wanted
to
do
is
create
an
API
that
will
allow
administrators
to
do
this
programmatically,
so
they
don't
have
to
go
into
the
application
at
each
project
level
or
at
each
group
level.
To
do
this,
it's
really
excited
to
see
this
feature
launch
it's
pretty
popular.
It's
been
around
for
a
while.
A
So
I'm
excited
to
get
this
this
new
API
out
and
then
continue
to
build
off
of
this
in
the
future.
Okay,
so
we
talked
about
garbage
collection,
optimization.
We
talked
about
using
NPM
as
a
as
a
remote
repository
when
packages
are
not
hosted
on
github.
We
are
investigating
adding
pipe
I
support
to
the
package
registry.
A
We're
improving
the
container
registry
bulk,
delete,
API,
we're
adding
in
a
new
section
of
the
user
interface,
a
group
level
container
rich
registry
and
we're
talking
about
extending
the
get
lab
API
to
allow
for
creating
listing
and
revoking
project
and
group
deploy
tokens
say:
I
got
it
all
ABS
full
mouthful,
okay!
Well,
let
me
know
if
you
have
any
questions
you
could
always
reach
out
to
me
at
e
rysiek,
get
lab
chime
in
on
the
issues
or
feel
free
to
contribute
something
looking
forward
to
making
this
the
best
release
ever.
Thank
you.
So.