►
From YouTube: Speed-run - Configuring Review Apps (website)
Description
This is a demo to show how to configure a review app through the .gitlab-ci.yml file
A
Hello,
my
name
is
Erica
Lewinsky
and
I'm
the
product
manager
for
the
early
stage
good
lab
today,
I
want
to
talk
a
little
bit
about
review
apps
on
how
you
can
configure
them
after
you
already
have
a
working
project,
so
once
we
have
configured
a
basic
staging
and
production
environment
as
part
of
continuous
delivery,
it
would
be
nice
to
review
the
changes
on
an
actual
system
before
going
to
staging.
This
is
called
a
dynamic
environment
or
what
we
call
review
apps
we
get
lab.
A
This
creates
an
environment
prayer
emerge
request.
This
is
valuable
not
only
for
developers
but
also
QA
product
owners,
product
designers,
anyone
that
is
interested
in
seeing
what
the
new
feature
looks
like,
and
you
can
just
simply
send
a
link
and
ask
for
feedback
in
this
demo.
I
will
show
you
how
to
add
a
review
app
after
the
project
is
already
configured
for
this
simple
example:
I'm
using
a
surge,
dot,
sh
and
Gatsby.
That
is
an
easy
way
to
get
a
static
website
up
and
running.
A
So
if
we
look
at
my
project,
you
can
see
that
it's
already
configured
and
it's
deploying
to
staging
and
production
environments.
So
we
can
see
that's
here
in
environments
and
you
can
see
I
have
a
production
of
production
and
the
staging
environment.
Now
the
part
the
pipeline
that
I
have
configured
looks
a
little
bit
like
this.
A
We
can
also
look
at
the
merger
quest
that
I've
done
in
this
project
and
the
last
one
you
can
see
it
was
deployed
to
staging
and
also
the
plights
of
production.
We
can
see
of
the
app
itself.
So
we
can
see
this
is
our
staging
environment,
and
this
is
our
production
environment.
And
now
what
I
want
to
do
is
show
how
you
can
configure
a
review
up
environment
to
check
your
changes
before
it
goes
to
staging,
and
then
it
will
also
change
one
of
the
files
and
see
what
it
looks
like.
A
A
So
we
have
the
stage
configured
and
we
have
the
job
configured,
deploy,
review
and
you'll
notice
that
it
goes
only
on
branches.
It
works
only
on
branches,
which
means
that
whenever
I
deploy
to
master,
this
job
is
not
going
to
be
initiated.
But
when
I
create
a
branch
that's
created
through
the
merger
quest,
it
will
be
called
on,
and
since
this
is
a
dynamic
environment,
we're
gonna
use
some
predefined
Burney
go.
A
So
you
can
see
here
in
the
name
we
have
CI
commit
ref
name
and
in
the
URL
we
have
our
basic
domain
name
and
an
additional
predefined,
CI
environment,
slug
name
and
will
also
notice
for
the
actual
deployment
that
we're
also
using
the
deployment
to
the
domain
name
and
again
CI
environment
slug.
So
this
is
really
important
to
notice.
A
A
A
A
A
We
can
now
see
the
button
that
says
view
app
and
pressing.
It
will
bring
us
to
a
new
environment.
As
you
can
see,
the
name
is
review
pouch
and
it's
our
new
review
at
well.
While
this
is
our
production,
our
pre-production
pages,
if
we
go
back
to
environments,
we'll
see
that
we
now
have
a
new
environment
in
addition
to
the
staging
and
production
that
we
had
before
we
had
our
new
review
patch.
A
A
A
Pages
index
we're
gonna
go
ahead
and
edit
it
with
a
web
ID,
and
you
can
see
that
the
title
of
the
page-
and
this
is
a
new
title,
which
is
what
we
saw
here
and
we'll
change
it
to
this.
The
best
title
ever
just
so
that
we
can
visually
see
the
change
and
we're
gonna
go
ahead
and
commit
which
is
going
to
create
a
new
merge
request
and
therefore
it's
going
to
deploy
it
again
to
the
review
app.
So
change
title
and
let's
copy
here.
A
A
A
A
Okay
and
now
it's
in
production,
so
let's
refresh
and
you
can
see
we
got
all
the
changes
throughout
the
review,
apps
staging
and
production.
So,
as
you
can
tell,
this
is
a
pretty
feature.
It's
very
valuable.
You
can
get
a
lot
of
feedback
before
at
the
point
to
your
know,
sites
staging
and
production
and
I
hope.
You
found
this
helpful.