►
From YouTube: GitLab Demo System Demo
Description
Jeff Martin, Senior Demo Systems Engineer, provides a demo of the new Demo Systems
A
All
right,
all
of
the
questions
I
see
there
are
great
for
the
QA,
so
I
will
continue
working
with
those
shortly,
but
with
that,
let's
start
with
the
a
Caleb
demo.
This
paper
review
for
some
of
you,
but
the
enhance
the
enhancements
and
what's
coming
in
the
future,
is
going
to
be
here
in
two
or
three
minutes
so
to
stick
with
me
for
a
second.
A
So
if
you
visit
Caleb
demo,
calm
feel
free
to
click
the
team
member
registration
and
create
an
account
once
you
sign
in
you're,
going
to
see
a
whole
bunch
of
things
going
on
here.
What
I
want
to
draw
your
attention
to
first
is
under
staying
where
you're
at
within
the
portal,
so
right
now
you're
on
the
dashboard,
and
you
can
see
any
of
the
resources
that
you
have
access
to.
We
also
have
a
catalog
3.
A
Now,
that's
mostly
a
scaffolding,
there's
not
a
lot
of
content
in
it
yet,
but
I'll
show
you
what
that
looks
like
in
just
a
second
and
then
we
have
the
demo
data
designer,
but
more
than
likely
you're
not
going
to
be
touching
these
right
away.
What
you'll
end
up
doing
is
you
create
an
account?
How
do
we
get
access
to
the
instance?
All
you're
going
to
do
is
go
down
here
and
click
on
the
get
lab
dashboard
and
that's
going
to
take
you
into
the
gate.
Love
instance.
A
If
this
is
your
first
time
visiting
the
site,
it
will
ask
you
to
authenticate,
and
all
you
need
to
do
is
use
the
username
that
you
provided
when
you
register,
as
well
as
the
password
once
you're
inside
it's
going
to
give
you
access
just
to
your
own
group.
So
these
are
projects
that
I
have
created
in
my
own
group,
there
are
other
other
groups
that
are
out
there.
However,
what
we
try
to
do
is
keep
things
relatively
isolated
in
the
gate,
LabCorp
instance.
So
it's
kind
of
your
own
sandbox,
rather
than
a
communal
area.
A
A
If
I
go
to
my
groups
and
click
on
my
group,
name,
I'll
see
a
little
easier
view
of
this,
and
so
what
I've
done
as
an
example,
is
I,
create
a
subfolder
called
project
templates
or
subgroup
and
then
put
all
the
things
that
I
want
to
clone
inside
of
there
and
then
anything
that
I'm
just
running
I
run
at
the
top
level.
I
could
create
sub
directories,
however
I
see
fit.
A
We
have
several
of
our
essays,
some
of
who
are
on
this
call,
who
have
quit
a
few
sub
groups
and
different
things
that
they're
doing
in
here.
You
can
do
whatever
you
need
to.
You
can
go
as
deep
as
you
want.
You
have
full
owner
rights
to
this
group,
so
now
this
group
is,
we
can
go
in
and
create
a
project
the
same
way.
We
would
on
any
gitlab
instance.
We're
not
worried
too
much
about
that.
If
you
do
need
some,
you
know
instruction
or
yours
curious
where
to
get
started.
A
There
are
some
tutorials
here
and
using
project
templates
and
simple
projects.
What
I
want
to
focus
on
today
is
using
the
demo
data
designer,
so
everything
I'm
going
to
show
next
is
written
in
the
step-by-step
tutorial,
as
well
as
there's
a
YouTube
video
that
walks
you
through
it,
and
so
don't
worry
too
much
if
you
miss
a
step
or
try
to
transcribe
notes
on
this
call,
but
it
must
give
you
a
quick
sampling
and
a
taste
of
what
this
is
all
about.
So
what
we
want
to
do
here
is
from
the
get
web
demo
portal.
A
So
this
is
the
get
lab
demo
comm
go
and
click
on
demo
data
designer
and
inside
of
here
these
instructions
are
going
to
walk
you
through
adding
your
environment
and
what
the
environment
really
is.
It's
simply
specifying
what
URL
but
get
Lepus
is.
Do
you
want
to
connect
to,
and
what's
the
personal
access
token
to
talk
to
that
environment
through
the
API?
A
So
all
you
need
to
do
is
add
that
for
the
gait
lab
demo
club,
you
can
also
do
this
for
Caleb
comm
or,
if
you
have
your
own
omnibus
instance,
you're
not
required
to
do
anything
special.
You
can
simply
add
the
URL
in
as
long
as
our
demo
portal
can
reach
it.
You
can
add
demo
data
into
it.
The
second
piece
of
this
is
the
Play
Books,
and
what
a
playbook
really
is
is
basically
specifying
what
are
the
values
that
you
want
to
submit
in?
A
But
you
can
add
all
the
different
labels
that
you
want.
You
can
add
different
milestones,
and
this
is
where
we
talk
about
the
relative
dates.
I'll
leave
this
for
you
to
read
on
your
own,
but
refers
to
that
January
first
relativity,
but
I
was
talking
about
so
whatever
date
that
I
imported
in
it's
going
to
show
up
as
today,
being
the
middle
of
all
this,
and
you
can
see
the
values
done
here,
depending
on
what
that
looks
like,
as
you
create
different
issues,
same
thing
applies
here.
A
That's
a
great
strategy
for
being
able
to
build
this
in
a
modular
approach
right
and
then,
ultimately,
you
can
create
different
issue
boards.
Where
you
can
add
labels,
you
can
add
different
elements
to
this.
So
there's
a
lot
of
value
you
can
do
with
this
and
I
would
entirely
encourage
you
to
watch
the
full
YouTube
video.
It's
about
30
minutes
that
watch
it
through
all
the
steps
and
sees
more
of
the
value.
A
But
ultimately,
what
we
like
to
do
is
expand
this
left
sidebar
to
include
all
the
resources
that
live
API
has
so
this
may
get
50,
60
70
different
items
along.
Obviously
we
will
group
them
or
in
Sui
accordingly,
but
basically
allow
you
to
create
all
the
different
elements
of
a
project
in
a
modular
or
fully
comprehensive
way
beyond
just
what
project
imports
do
we're
also
going
for
the
group
level
which,
as
you
know,
does
not
have
a
lot
of
import/export
functionality
right
now
doing
all
the
epics
doing
sub
projects
with
it
doing
all
the
correlation.
A
You
know.
Real-Time
burndown,
charts
instance
model
configuration,
appearance,
settings
rules
so
on
and
so
forth.
So
the
direction
that
we're
going
over
the
next
three
to
six
months
is
taking
this
as
a
scaffolding
and
a
platform
to
make
demo
data
that
much
richer.
So
the
infrastructure
we've
built
with
the
demo
cloud
is
simply
providing
us
the
infrastructure
needed
to
generate
and
populate
with
demo
data.
That's
what
we're
trying
to
ultimately
do
so
that's
the
connection
with
all
of
this.
So
that's
the
demo
designer,
if
you
look
at
the
catalog
libraries
and
you
browse
through
here.
A
What
were
ultimately
trying
to
do
is
those
links
that
all
get
posted
on
YouTube,
unfiltered
or
throughout
the
handbook
we're
trying
to
centralize
that
we
haven't
taken
this
to
a
level
of
maturity.
Yet
so
right
now
it's
more
the
the
infrastructure
and
the
the
code
and
systems
are
in
place,
but
the
content
is
not
matured
yet
in
terms
of
what's
in
here,
so
it's
not
usable
just
yet,
but
the
concept
would
be
is
if
you
went
in
you're.
Looking
for
a
specific,
you
know
scenario
or
feature
that
a
customer
would
like
to
see.
A
You
can
go
in
and
look
at
that
scenario.
So
I
click
on
issue
tracking
I
can
see.
Is
there
any
content
for
this?
There's
not,
but
if
there
was,
for
example,
I
could
have
the
playbook
that
I
just
created
as
part
of
this
I
need
a
playbook.
This
shows
some
rich
data
for
this
feature.
This
is
where
the
playbook
we
live.
If
there's
slides,
if
there's
videos,
this
is
where
that
would
live.
A
What
we're
going
to
end
up
doing
long
term
is
crowdsourcing
this
so
for
you're,
really
curious
to
get
involved
feel
free
as
an
example
of
what's
possible.
This
is
the
library
that
Darwin
had
helped
create
it's
kind
of
a
prototype,
and
so
you
can
go
in
and
see.
I
want
to
see
what
this
scenario
looks
like
and
embeds,
and
the
YouTube
unfiltered
video,
as
well
as
the
Google,
slides
and
I,
can
simply
go
fullscreen
here
and
see
what
this
looks
like
and
work
my
way
through
that
or
there's
any
markdown
that
goes
with
it.
A
I
can
then
it'll
simply
link
over
to
the
code
that
goes
with
that
or
other
links
right.
So
ultimately
it's
making
it
easy
and
creating
a
library
for
you
to
really
you
stuff,
as
well
as
contribute
additional
versions.
If
you
have
more
content,
you
want
to
add
it
basically
is
a
handbook
contribution
model
as
well.
So
it's
taking
a
step
back.
The
demo
portals
focused
on
the
infrastructure.
A
A
lot
of
the
demo
data
with
the
demo
designer
is
a
scaffolding
of
how
we're
going
to
build
it
and
the
catalog
libraries
allowing
you
to
easily
get
where
you
need
to
go
while
providing
all
the
different
components
of
fully
managed
infrastructure
to
anything,
a
self-service
you
might
need
and
I
just
said,
I
simply
need
get
on
to
pay
for
my
age
of
UX
account.
So
that's
what
we're
trying
to
do
is
go
to
that
level.