►
From YouTube: The Package Registry is moving to GitLab Core in 13.2!
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
If
you're,
following
along
with
the
package
stage,
you've
probably
heard
about
this
and
you're
probably
excited
about
it
as
well,
but
we
will
be
moving
the
package
registry
from
the
Enterprise
Edition
to
the
core
edition,
which
means
that
the
basic
functionality
of
building
and
publishing
packages
will
be
available
for
all
users
for
free
really
excited
about
this.
So
what
does
that
mean
exactly
if
I
head
over
to
the
documentation?
I
can
see
here's
our
supported
package
manager
types
here.
A
We
support
Coenen
maven,
NPM,
nougat,
PI
P
I
go,
although
this
is
currently
behind
a
feature,
flag
and
composer
packages
as
well.
So
all
of
these
will
move
to
the
core
edition.
I
should
also
say
that
in
the
future,
any
formats
that
we
add
so,
if
I
hop
down
to
suggested
contributions,
these
will
also
be
added
to
the
core
Edition
as
well.
A
All
the
basic
functionality
of
using
git
lab
as
a
private
or
public
package
repository
authenticating,
using
your
git
lab
credentials,
personal
access,
token
or
job
token,
although
I
should
mention
as
an
aside,
not
all
of
the
supported
formats
support
the
job
token,
yet
we'll
be
working
on
nougat
and
I
in
milestones,
13
3,
&,
4,
respectively,
you
can
publish
packages
to
get
lab.
You
can
pull
them
using
the
command
line,
obviously
or
the
CLI
I'm.
Sorry,
the
command
line
or
CI.
You
can
also
search
for
packages
hosted
on
git
lab.
A
So
if
I,
for
instance,
want
to
go
into,
let's
try
maven
and
I
go
to
the
package
registry
UI.
We
have
this
filter
by
name
option
as
well,
so
I
could
type
in
my
project
and
it'll
show
me
both
they're
all
called
that
in
this
case,
but
you're
able
to
search
and
also
a
UI
that
displays
the
meta
details
and
metadata.
So
let's
go
back
to
that.
A
Maybe
an
example,
so,
for
instance,
that
this
package
was
built
using
gitlab
CI,
so
the
benefit
of
that
is
I
could
see
that
which
branch
and
commit
is
responsible
for
the
package.
This
will
help
you
validate
and
troubleshoot
if
something's
gone
wrong.
We
also
include
easy
to
copy
installation
and
setup
commands,
so
you
can
very
easily
just
copy
command
necessary
to
also
to
set
up
your
pom
file.
A
I
could
see
some
basic
metadata
here
and
then
I
could
see
the
activity
of
what's
been
happening,
which
pipeline
is
responsible
and
then,
of
course,
I
can
actually
download
the
jar
and
pom
files.
The
other
nice
thing
is
that
if
you're
contributing
a
new
package
manager
and
if
you're
looking
for
a
suggested
contribution,
I
would
head
over
to
the
documentation,
I'm,
particularly
interested
and
I
know.
The
community
is
particularly
interested
in
Debian,
Ruby,
gems
and
rpm.
A
Okay,
well
really
excited
about
this.
So
if
you
have
any
questions
reach
out
to
me
to
rysiek,
it
lab
whether
something's
not
working
right
for
you
or
you
have
a
different
use
case.
You
want
to
discuss
or
you're
wondering
how
you
can
best
contribute,
of
course,
feel
free
to
reach
out
to
me
tee
rysiek,
it
lab
and
I
will
talk
to
you
in
the
issues.
Thank
you.