►
From YouTube: Improvements to Enable Review App modal
Description
Gina Doyle (Product Designer: Pipeline Insights & Runner) walks through the design proposal to improve the Enable Review App modal today in the Environments page.
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/352528
Docs referenced: https://docs.gitlab.com/ee/ci/review_apps/
A
Hey
everyone.
I
wanted
to
get
your
feedback
on
something
I've
been
working
on
for
review
apps.
So
I
noted
this
when
I
was
performing
the
ux
scorecard
for
review
apps.
A
So
what
I
wanted
to
do
is
focus
on
trying
to
improve
that,
because
we
have
really
great
documentation
that
lives
in
our
docs
site
today
and
provides
a
bunch
of
different
example,
projects
that
you
can
copy,
like
their
configuration
setup
from
it.
So,
just
to
give
you
a
look
into
the
modal
when
I
say
enable
review
app
from
the
environments
page
when
I'm
in
a
project.
A
This
is
where
it
links
to
kubernetes,
which
isn't
isn't
true.
You
don't
have
to
have
kubernetes
set
up,
but
you
would
go
to
this
cluster
whatever,
and
then
you
would
copy
the
snippet
which
doesn't
work
for
all
the
projects.
Like
I
was
saying,
a
lot
of
this
stuff
needs
to
be
changed
and
you
do
end
up
adding
this
thing
into
your
ci
email
file,
but
then
there's
this
optional
step
to
include
visual
reviews,
there's
actually
a
lot
of
additional
features
that
you
can
add
to
review.
Apps
and
visual
reviews
is
only
one
of
them.
A
A
If
you
use
the
dynamic
environments,
it
will
create
a
new
environment
for
each
branch
that
you
open
an
mr
with
and
then
generally
to
configure
a
review.
App
you'll
need
to
set
up
your
infrastructure
to
host
and
deploy
the
review
app.
So
it
doesn't
just
concentrate
on
kubernetes.
It's
generally
you'll
have
to
install
and
configure
a
runner
to
do
deployment.
A
That's
probably
already
happened
if
you're
on
sas
and
you
don't
need
something
special
and
then
you'll
have
to
set
up
a
job
in
ci
yml
like
the
review,
the
review
stage
and
the
job
that
uses
a
variable
to
create
the
dynamic
environments
and
restrict
it
to
run
only
on
branches,
and
then
you
can
also
set
up
a
job
that
manually
stops
the
review
apps.
I
didn't
mention
visual
reviews
and
I
didn't
mention
our
routes
option
that
you
can
attach
to
review
apps
as
well.
I
just
didn't.
A
I
didn't
know
if
that
was
really
that
important
to
to
mention
and
then
what
I
listed
after
that
was
configuration
examples
to
be
able
to
get
your
environment
running,
so
these
were
based
off
of
the
projects
that
I
found
in
our
documentation
and
then
the
ones
that
that
gitlab
has
so.
The
first
example
is
using
a
shell
runner,
which
is
already
given
to
you
by
default.
You
would
configure
your
server
and
then
add
variables
and
to
really
figure
out
how
that's
done.
A
I
link
out
to
those
example
projects
because
they
have
readme
files
of
the
instructions
and
the
review
apps
is
they
show
the
whole
like
configuration
template
in
there,
and
then
you
can
also
use
the
gcp
or
aws
bucket,
which
is
what
we
do
on
gitlab.com
I
linked
up
to
that
which
also
has
a
readme.
A
All
of
these
have
read:
use
a
docker
runner,
configure
your
server
and
add
variables
similar
to
the
shell,
but
a
little
bit
different
and
then
using
a
kubernetes
clusters
to
set
up
this
feature
through
auto
devops.
A
So
if
you
already
have
that
configured,
then
you
can
use
you
can
like
automatically
get
a
dynamic
environment,
and
then
I
link
to
one
of
the
ones
that
we
have
in
the
docs,
which
is
review
apps
openshift,
which
again
has
a
readme
file
with
instructions
of
how
to
do
everything,
and
then
I
was
thinking
this
view
more
example.
Projects
would
actually
just
take
you
to
the
documentation
where
we
include
a
list
of
example
projects.
A
There
might
have
been
like
one
that
I
didn't
mention
here
and
there's
one
youtube
tutorial,
video
about
it
and
then
other
than
that
they
can
just
read
more
about
the
docs
there.
So
I'm
interested
in
hearing
feedback.
I
know
that
this
is
a
lot
of
text,
so
I
had
a
hard
time
formatting
it
and
I
tried
adding
some
like
secondary
text
and
stuff,
so
it
would
make
it
less
overwhelming.