►
From YouTube: GitLab Conan Package Repository Demo
Description
This video demos the upcoming Conan package manager support in the GitLab package registry. It covers authenticating with the registry, setting the Conan remote to the GitLab registry, and uploading a package to the registry. Installing and searching for packages from the registry is also covered.
A
Hopefully,
first
of
many
today
we're
gonna,
be
taking
a
look
at
the
upcoming
conan
package
manager
and
package
registry
on
Vietnam
I'm,
going
to
take
everyone
through
just
a
quick
run-through
of
how
to
setup
using
gitlab
as
the
package
registry
for
Conan
and
and
create
some
repositories
installing
and
uploading
a
package
and
some
of
that
basic
functionality.
So
I've
started
out
I've
created
a
project
here.
That
is
a
conan
project.
It's
a
really
really
basic
c++
app.
That
is
a
hello
world
type
app.
This
is
actually
compliments
of
the
conan
documents.
A
They
have
a
hello
world,
app
that
they
shared
on
here
and
their
documentation
is
great
if
you're
just
getting
started
with
coded
or
kind
of
curious
how
things
work
so
to
get
started.
The
first
thing
I'm
going
to
need
to
do
is
I'll
bump
this
size
up.
Everyone
can
see.
Just
let
me
just
give
me
a
holler
if
anything
is
a
little
bit
too
small.
A
B
A
A
Over
here
in
the
terminal,
I'm
just
gonna
run
a
simple
conan
command
come
and
create.
We
want
to
create
it
in
your
current
folder
and
then
conan
uses
this
method
of
you
add
the
attributes
that
you
want
to
add
to
the
package,
and
so
the
first
attribute,
we
add,
is
the
path
to
the
actual
project,
so
you'll
see
that
it's
root
plus
conan
test
local
and
this
matches
our
project
path
up
here.
So
this
is
a
way
for,
since
we're
initially
implementing
an
instance,
level
package
registry
or
repository.
A
A
A
A
A
Yeah,
sorry
about
that
all
right,
so
this
is
just
another
project
that
I
have
set
up
in
the
in
the
same
space,
and
so
over
here
I'm
going
to
kind
of
run
the
same
same
idea:
I'm
gonna
go
come
in
and
create,
and
this
one
has
a
different
file
path.
My
common
project
and
we'll
call
this
one
stable,
because,
hopefully
it
will
work
properly
there
we
go
alright,
and
so
that's
just
doing.
This
still
has
nothing
yet
to
do
with
the
gait
lab
side
of
things.
A
I
won't
go
into
detail
on
how
that
works,
but
if
we
go
to,
if
you
go
to
your
settings,
you'll
be
able
to
create
any
personal
asset
access
tokens
and
so
for
the
scope
of
packaged
registries.
We
just
need
an
API
access
to
them,
so
I've
already
gone
ahead
and
created
that
and
the
way
that
we
use,
that
is
as
a
precursor
for
all
of
our
commands.
A
A
If
we
take
a
look
at
the
conan
file,
this
is
the
main
configuration
file
for
conan
package,
and
so
it's
where
you'll
set
up
your
project
name
and
version,
and
you
can
up
the
version
in
there
as
well
and
that's
all
covered
in
kind
of
documentation,
alright,
so
back
to
the
upload.
So
we've
got
my
conan
package
name
or
they
call
it
recipe
we're
gonna
upload.
All
of
the
files
associated
with
that
package
and.
A
We
need
to
set
the
remote
to
localhost
and
that's
yeah.
So
now
we
end
up
uploading.
It
goes
ahead
and
authenticates
against
localhost
and
then
you
can
see
it
starts
to
upload
the
package
so
to
verify
that
there's
a
few
different
ways.
Certainly
we
can
head
right
over
to
the
UI
and
if
we
load
the
package
page
over
here,
we'll
hopefully
see
what
that's.
Actually
the
old
project
wasn't
yeah.
My.
A
A
A
So
one
other
way
that
we
can
also
check
for
the
packages
using
the
Conant
search
mechanism
and
so
to
do
that,
we're
going
to
use
the
conan
search
command
and
you
can
search
for
packages
by
the
first
portion
of
their
recipe,
which
is
sort
of
just
the
main
sort
of
the
main
name
of
the
package.
So
we
could
search
for
hello
and
I'll,
bring
back
all
packages
named
hello.
We
can
throw
a
wild
card
in
there
and
it'll
find
all
packages
named
in
a
similar
manner.
A
And
there's
a
list
of
all
of
the
packages
that
exist
on
localhost
that
are
available
publicly
or
that
I
have
access
to
that
matched.
That
name,
and
so
you
can
see.
I've
I've
gone
through
a
few
different
iterations
here
and
so
our
stable
one
I
should
own
up
there
as
well
all
right
any
questions
at
all.
So
far
about
the
uploads
and
one
other
thing
to
note
is
while
I'm,
using
my
token
and
configuration
and
remote
in
every
single
command.
A
D
D
A
E
A
E
A
Nick,
alright,
so
now
that
we've
gotten
the
package
uploaded
and
can
see
it
in
there,
so
we
can
kind
of
get
into
how
we
can
install
it.
So
Conan
works
in
a
way
where,
on
any
given
users,
machine
there's
sort
of
a
shared
area
where
all
of
the
packages
are
stored
and
then
any
time
you
refer
to
them,
it'll
just
be
pulling
from
that
shared
area.
A
So
we
need
to
remove
the
package
from
our
local
cache
or
local
store,
I
suppose
so
we're
going
to
do
that
by
saying,
come
in,
remove
and
then
we'll
remove
this
specific
package
and
you'll
notice
I'm,
not
using
my
credentials
because
I
don't
want
to
remove
it
from
the
remote
registry.
I
just
want
to
remove
it
locally.
A
All
right
so
now
that
it's
removed,
we
can
go
to
a
new
project,
so
I'll
just
sort
of
create
a
directory
come
install
test
and
go
into
it
and
from
here
in
order
to
install
packages,
we're
going
to
use
the
Conan
file
in
order
to
it's
kind
of
similar
like
if
you'd
be
working
with
NPM
with
package.json.
It's
just
a
place
where
you'll
list
out
the
different
packages
that
you
need
for
a
given
project
so
we'll
create
that
file
and.
A
A
Cool
so
from
here
we'll
create
a
build
directory
and
CD
into
that
and
from
there
and
now
we
can
run
the
install,
and
so
it
works
in
a
similar
way.
We
have
our
credentials
that
we're
going
to
be
using
and
we
will
do
a
conan
install
and
you
use
two
periods.
This
is
all
kind
of
just
common
nomenclature
where
this
is
what
identifies
that
we
want
to
be
building
into
the
current
directory
and
using
the
conan
file
txt
file
from
the
previous
directory,
and
from
here
we
will
just
set
the
remote
to
localhost.
A
And
everything
set
up
using
that
new
project
name,
but
we
ended
up
using
the
old
one,
so
updating
around
there
all
right.
Try
that
again,
all
right!
So
now
it
looks
like
it
went
ahead
and
downloaded
all
those
files
have
installed
it,
and
you
can
see
that
in
our
build
folder
we
have
all
of
the
various
sort
of
metadata
files
and
then
they'll
be
referring
to
the
package.
A
That's
in
that
shared
area
of
Conan
in
my
local
store
and
so
like
the
last
piece
of
functionality
that
we
might
want
to
deal
with
is
removing
the
package
from
the
remote.
So
if
we
wanted
to
actually
remove
delete
the
package
on
gitlab,
that's
as
easy
as
running
that
remove
that
same
exact
remove
command
as
before,
but
instead
of
just
doing
it
locally.
We
set
the
remote
to
look
closed
here
and.
A
A
C
A
Not
specifically
in
terms
of
how
user
ends
up
using
it,
it's
somewhat
similar
I
think
the
way
that
Conan
itself
works.
There
is
no
necessarily
like,
like
the
way
that
current
self
works.
It
is
certainly
different,
but
from
the
aspect
of
how
a
user
would
use
it
and
how
the
pipeline's
would
probably
access
it.
It's
it
seems
to
be
very
similar
where
you
know.
We
just
need
this
access
token
and
eventually
we'll
be
able
to
use
job
tokens
as
well,
which
I
think
would
allow
us
to
be.
C
C
Don't
know
neski
we
can
skip
over
that,
and
the
other
thing
I
was
thinking
was
like.
As
we
build
up
package
managers
would
be
cool.
You
either
call
out
the
actual
actual
package
file.
While
we've
got
all
of
those
different
things
with
it.
That's
an
icon
or
highlighting
so
I,
don't
know
how
we
would
go
about
doing
that,
but
just
an
idea.
A
Well,
I
think
I,
guess
I'm,
not
100%
sure,
but
I
do
think
that
all
of
the
files
are
needed,
like
I,
suppose
that
there's
probably
away
that
I,
don't
know
how
people
necessarily
use
these
all.
So
there
probably
is
ways
to
to
just
download
that
single
main
package
and
unzip
it
and-
and
he
use
what's
ever
in
it,
but
if
you're
using
Conan,
you
generally
need
all
of
those
files
in
did
you
want
a
breathalyzer
question,
yeah.
B
A
If
we
know
what
file
that
is
that
everyone
wants
to
see
like,
maybe
we
should
just
show
them
that
file
in
the
format
they're
used
to
seeing
so,
for
example,
like
npm,
everyone
uses
package.json
and
that's
where
most
of
the
important
metadata
exists.
So
would
it
be
useful
for
some
users
to
just
be
able
to
view
that
file
rather
than
seeing
you
know,
a
redesigned
list
of
those
different
attributes
and
the
same
kind
of
goes
for
here?
There's
that
conan
file
that
has
all
in
the
various
configuration.
F
So
my
question
is,
since
you
work
with
it,
and
you
have
a
good
feeling
of
it,
how
many
of
those
common
will
we
be
able
to
like
fulfill
in
the
UI
for
the
user?
Probably
we
won't
be
able
to
put
up
what
we
shouldn't
put
the
person's
access
token,
but
the
rest
also
info
that
we
have
in
the
system
to
build
them
for
like
to
make
their
life
as
easy
as
possible.
F
E
A
E
E
Like
my
force
were,
I
was
wondering
if
the
actual
search
was
just
a
generic
database
lookup
and
therefore
could
relatively
easily
be
applied
to
other
package
histories
and
then
eventually
hooked
up
on
the
front
end.
But
yeah.
It
sounds
like
there's
a
bit
more
work
than
I
was
hoping
before
them.
Yeah.
A
Yeah
I'm
not
sure
if
it
was
strictly
required,
but
it
does
seem
that
sounded
like
that.
It
was
one
of
the
sort
of
major
commands
that
users
use.
So
that's
why
we
included
it
in
the
initial
implementation
all
right.
It
looks
like
we're
right
at
time
here
so
there's
any
other
questions
feel
free
to
add
them
to
the
document
and
I'll
and
I'll
try
to
answer
them
there,
but
otherwise.
Thank
you
all
for
coming
and
good
luck
with
your
with
the
rest
of
your
day.